/ $Header: rdbms/mesg/error.txt /st_rdbms_11.2.0/1 2010/11/07 22:24:04 kquinn Exp $ error.msg / / Copyright (c) 1987, 2000 by the Oracle Corporation. All rights reserved. / / / / File: RDBMS:[UTL]error.msg / Created: 10/17/86 / / -=( COMPLY WITH STANDARDS WHEN CHANGING MESSAGES )=- / / Email SDRESKIN your changes and he will verify compliance with standards. / / -=( COMPLY WITH STANDARDS WHEN CHANGING MESSAGES )=- / / Message Standards / ================= / Author Brian Quigley / Written 07/28/92 / / Purpose / ------- / When a message is generated, you are speaking directly to the user. Often, / the quality of your software is judged by the ease with which a user can fix / problems. Your purpose is to make it as easy as possible to use Oracle / products. / / Note that the "Cause:" and "Action:" sections for a message will also be / seen by the user. Thus, it is important to keep these sections simple, yet / as helpful as possible. / / Whenever possible, include all relevant information within the message. / / Your purpose is to make a message as informative as possible. / / Size Of Message / --------------- / Message text should be limited to a maximum of 76 characters. Messages / containing embedded % directives should not overrun the 76 character limit / unless they signal unusual errors which do not occur as part of user / applications. For example, startup errors and system-dependent errors can / probably may have longer message text. / / / Simple Language / --------------- / Avoid cryptic messages and overly technical language. / / NOT GOOD: index key does not exist root dba %s, dba %s (%s) / BETTER : index key does not exist for row: %s, %s, %s / / / Lowercase vs. Uppercase / ----------------------- / Use uppercase for commands and keywords. / / NOT GOOD: alter cluster statement no longer supported / BETTER : ALTER CLUSTER statement no longer supported / / / Use lowercase in the message wording, including the first letter. / / NOT GOOD: Invalid syntax / BETTER : invalid syntax / / / Commands, Keywords, Parameters Values / ------------------------------------- / Whenever possible, give the command, keyword, and parameter values that the / user used. / / Use uppercase to indicate commands and keywords. / / NOT GOOD: missing IDENTIFIED keyword / BETTER : GRANT CONNECT statement requires the IDENTIFIED keyword / / NOT GOOD: MAXVALUE is less than current value / BETTER : ALTER SEQUENCE MAXVALUE %s is less than current MAXVALUE %s / / / Period / ------ / Do not end a message with a period. / / / Numbers / ------- / Do not enclose numbers with special characters. / / NOT GOOD: number of control files (%s) does not equal %s / BETTER : specified %s control files while other instances have %s / / Spell out the word "number" to ensure the message is understood. / / NOT GOOD: change %s for thread (%s) is in sequence #%s / BETTER : the change number %s for thread %s is in sequence number %s / / / Numbers - User Input / -------------------- / Do not enclose user-input numbers with special characters. / / NOT GOOD: file size (%s) exceeds maximum of %s blocks / BETTER : a file size of %s would exceed the allowed maximum of %s blocks / / / Quotes / ------ / Do not use single or double quotes to highlight a text variable or command. / / NOT GOOD: 'row_locking = always' requires transaction processing / BETTER : ROW_LOCKING = ALWAYS requires transaction processing / / / Single Quotes / ------------- / Never use single quotes. / / / Double Quotes / ------------- / ALWAYS and ONLY use double quotes to identify database objects. / / NOT GOOD: file %s: bad block size "% bytes" expecting "%s" / BETTER : expected block size of %s bytes in file "%s" but found %s / / NOT GOOD: duplicate column %s / BETTER : duplicate column "%s" specified for table "%s", schema "%s" / / / Ellipses / -------- / Never use ellipses. / / NOT GOOD: datatype {%s} for column %s, table %s.%s is not supported / BETTER : datatype %s not support for column "%s" table "%s" schema "%s" / / / Parentheses / ----------- / ALWAYS and ONLY use parentheses for identifying constraint names. / / NOT GOOD: unique constraint %s.%s violated / BETTER : unique constraint (%s.%s) violated / / NOT GOOD: invalid file size (%s) / BETTER : size of %s bytes is invalid for file "%s" / / / Brackets / -------- / ALWAYS and ONLY use brackets for identifying program argument values. / / NOT GOOD: Internal Error: %s,%s,%s,%s,%s,%s,%s / BETTER : internal error, arguments: [%s],[%s],[%s],[%s],[%s],[%s] / / / Grammar / ------ / Use complete sentences whenever possible (but no period at end of / sentence). / / Use not use multiple sentences in a message, i.e. one sentence only. / / Use the active voice. / / Do not use an antagonistic tone. / / Use correct punctuation whenever possible. / / / Recommended Style / --------------------- / Try to make positive recommendations or suggestions as part of the message. / / Explain what is invalid AND what is valid. / / NOT GOOD: invalid file size (%s) / BETTER : file size of %s is invalid / BEST : file size of %s bytes is outside valid range %s to %s bytes / / NOT GOOD: duplicate column %s / GOOD : duplicate column "%s" in %s / BEST : duplicate column "%s" in %s "%s" / ^ ^ / this variable ... ... this variable / indicates the TYPE indicates the NAME / of database object of the object / / / Thus, substituting ... 'colin', 'view' / / in: duplicate column "%s" in %s / gives: duplicate column "colin" in view / / / And, substituting ... 'ugotit', 'primary, foreign or index key' / / in: duplicate column "%s" in %s / gives: duplicate column "ugotit" in primary, foreign or index key / / And, substituting ... 'pedestal', 'table', 'entablature' / / in: duplicate column "%s" in %s "%s" / gives: duplicate column "pedestal" in table "entablature" / / And substituting ... 'wat', 'dee', 'dikins' / / in: illegal constraint (%s.%s) for schema "%s" / gives: illegal constraint (wat.dee) for schema "dikins" / / / Text Variables / -------------- / Do not place text variables at the beginning of messages, as this does not / allow correct alphabetical sorting of the messages. The alphabetical listing / at the back of the Messages Manual is a necessary tool for Customer Support. / / NOT GOOD: %s not found / BETTER : object %s not found / BEST : object %s not found in schema %s / / / Internal Errors & Routine Names / ------------------------------- / Use ORA-00600 messages for internal messages not to be seen by the user. / / Do not use routine names in messages. / / NOT GOOD: ORA-03116, ttcxxx: invalid buffer length / BETTER : ORA-00600, internal error, arguments: [ttcxxx], [], [], [], [] / / / Public vs. Non Public Messages / ------------------------------ / Use ORA-00600 messages for internal messages not to be seen by the user. / / For messages which are for internal use only, indicate this in ERROR.MSG / message listing or at beginning of the range of this type of message in the / file. Debug event codes, CORE messages, are examples. / / Use "// *Document: NO" as follows: / / e.g. / 10049, 00000, "protect library cache memory heaps" / // *Document: NO / // *Cause: / // *Action: Use the OS memory protection (if available) to protect / // library cache memory heaps that are pinned. / / / Programmer's Comments / --------------------- / If you wish to add comments regarding a message that should not be seen by / the public, use "// *Comment: " as follows: / / e.g. / 32769, 00000, "incompatible SQL*Net version" / // *Cause: An attempt was made to use an older version of SQL*Net that / // is incompatible with current version of ORACLE. / // *Action: Use a newer version of SQL*Net. / // *Comment: Can only happen if user tried to use an illegal copy of a / // pre-lease version of SQL*Net. / / / ORACLE vs. Oracle / ----------------- / The word ORACLE in uppercase refers to the ORACLE server. Use the term / "ORACLE server" when referring to the server. / / The word Oracle in lowercase with capitalized first letter refers to the / company. Use "Oracle Corp." when referring to the company. / / /------------------------------------------------------------------------------ / / MODIFIED / kquinn 07/05/10 - 9287616: add event 10253 / kquinn 11/02/10 - Backport kquinn_bug-9287616 from main / wbattist 01/11/10 - bug 9275168 - modify message text for ORA-32701 to / make it clearer / kquinn 02/13/09 - 5687266: ensure ora-1722 is documented / ccaominh 12/12/08 - Bug 7020906: Add event 10481 / tbhukya 12/12/08 - 7627130: Add 39250 err msg to e38001.msg / kquinn 09/03/08 - 7359014: add 12999 error message / ineall 08/28/08 - 7234592: Add 16439 / ashrives 04/18/08 - 6820451 Add 27129->27135 to e24280.msg / swolicki 12/31/07 - reserved range 62010-62029 for DUMA Kernel-Side / mpopeang 11/19/07 - bug5589956: add error 62001 / arogers 10/26/07 - 6413891 Add 27079 to e24280.msg / chliang 04/19/07 - add 30136 / kquinn 04/17/07 - 5523578: add event 25476 / chliang 04/11/07 - add 41400 and 41401 / debanerj 08/09/06 - added 3145 for Vector I/O / jaskwon 05/31/06 - Reserve additional block for resource manager / errors / chliang 03/29/06 - add new error 3140 and 3141 / kshergil 01/23/06 - 4093938: add new error 32029 / kshergil 10/31/05 - 4658627: added error/event 43806 / skiyer 09/20/05 - 4581483: edited error14132 to reflect temp table / usage is wrong / sschodav 08/22/05 - added new error 24854 for bug 4366667 / wclin 09/06/05 - add event 30579 for internal Oracle Text tests / kshergil 06/28/05 - 4364202: add event 10621 / kquinn 06/14/05 - 4421376: Add event 10519 / jgalanes 05/17/05 - Add 44401 - 44409 events for Classic export import / amysoren 04/22/05 - add error 13950 / kquinn 03/24/05 - 4162293: Add event 22824 / chliang 02/03/05 - add error 3135 and 3136 / aramacha 02/11/05 - Fix 4046467 : Add error 25316. / kquinn 10/09/04 - 3830972: Add event 10854 / ssubrama 08/11/04 - bug 3814658 add event 10639 / porangas 08/03/04 - 3774546: Add error 24817 / ssubrama 07/26/04 - bug 3747472 add event 14529 / chliang 06/20/04 - add error 24450 / kshergil 04/23/04 - 3566511: add event 10629 / desinha 02/18/04 - 3128021: add row dep info for 14132 / porangas 01/22/04 - [3385076]: adding an event 10508. / kquinn 01/13/04 - 3296775: Added error 25011 / ssubrama 12/24/03 - add event 10973 for bug 2619509 / akatti 12/01/03 - [2934659]:add OCI event 24910 / kquinn 11/30/03 - 3255701: Add 24952 error / chliang 08/01/03 - bug 2940345: add error 24816 / ssappara 07/02/03 - Bug2909969:Added error 24909 / desinha 01/10/03 - bug 2588217 add event 10506 to disable fix / dtahara 11/06/02 - 2607029: add event 10504 to disable fix / ssubrama 11/07/02 - bug 2656881 event 10970 to backout 2133357 / vakrishn 10/15/02 - added errors 8189-8196 for flashback table project. / sbedarka 09/16/02 - #(2479110) handle pin deadlock error / kquinn 08/13/02 - 2235386: Amended 10027/10028 / akatti 08/23/02 - [2436572]:added error 25409 / cunnitha 05/30/02 - bug 2313473:added error 32583 / sbedarka 05/16/02 - #(2268284) amend 12842 details / sbedarka 05/03/02 - #(2242434) write parse error to alert if 10035 set, / 10035 being reused. / ssubrama 04/09/02 - bug 2200057 add error 6579 / phchang 02/11/02 - #1941831: add error 2314 / ptearle 01/11/02 - 2098120: add event 10502 to disable fix / aramacha 02/13/02 - Fix for 2163927 : added error 28595. / ssubrama 12/15/01 - bug 1814582 add error message 22283 / kquinn 10/04/01 - 1662642: Add event 10624 / phchang 09/10/01 - #1914633: correct max size in error 22973 / gviswana 05/29/01 - Add event 10513 to disable wrap source compression / jarnett 05/08/01 - add event 10501 for periodic heap check. / ptearle 03/03/01 - 1577003: add event 10138 / allee 01/26/01 - bug 971108, new error message 30770, 32576 / dgprice 01/12/01 - bug 1394096 new error message 1062 / cunnitha 01/10/01 - #1364334:add error 1690 / ptearle 12/27/00 - 1344111: add event 10137 / snutakki 12/04/00 - replace event 13300 with 10337 to avoid conflicts / snutakki 11/30/00 - #1183055: Add new event 13300 / sbedarka 11/15/00 - #(822764) behaviour controlled via event 10945 / ptearle 11/16/00 - 1089848: add event 10136 / kquinn 07/19/00 - 532570: Add 10371 event / etucker 06/01/00 - add messages for datetime messages / sbedarka 05/23/00 - #(966634) add new error 30626 / sparrokk 02/17/00 - Add message 30563 / wnorcott 01/18/00 - Add ORA- msgs 31401-31599 for CDC / prao 01/16/00 - 987371: change trigger debug event from 10250 to 10309 / kquinn 01/14/00 - 1065010: Add event 10129, document 10122 / kquinn 01/18/00 - 762114: Add event 10191 / phchang 11/10/99 - Added (missing) message 27157 / tguenssl 09/30/99 - 887509: add message 27092 / kquinn 11/18/98 - 710922: Add error 1948 / kquinn 01/07/99 - Add message 28604 / kquinn 11/24/98 - 769412: Event 10119 used for QKA only / sbedarka 05/08/99 - #(743019) controlled by event 10154 / sbedarka 12/03/98 - Changed 10152 to 10153 owing to conflict / sbedarka 11/19/98 - 737725: Add event 10152 / kquinn 07/21/98 - 692355: Add event 10151 / kquinn 03/18/98 - add message 7345 / phchang 01/20/98 - Add message 25196 / eyho 08/25/97 - add DLM debug trace event / jdraaije 12/19/96 - name change from callout to external proc.(again) / pravelin 12/12/96 - Repair damage from merge error in version 312 / swerthei 12/09/96 - add 19659 / cxcheng 12/05/96 - add message 22308 / cchu 11/27/96 - Fix merge problem / wchang 11/22/96 - add repapi error codes and messages / mluong 11/21/96 - fix compilation error / bmichon 11/21/96 - Adding Error 29400, data cartridge error / fputzolu 11/20/96 - allow pkey update within same partition (14402) / pravelin 11/20/96 - Add 2 messages for heterogeneous (HO) connection err / sdange 11/20/96 - add more error messages. / sgollapu 11/19/96 - Add 24344 / moshen 11/19/96 - add event 10403 / lchidamb 11/18/96 - add display type error messages / jnewman 11/16/96 - Re-editing messages 02300-02350 / jnewman 11/15/96 - Edit cause and action for 22800-22810 / slari 11/15/96 - change wording of OER(2031) / jnewman 11/14/96 - Editing error messages 02300 -02350 / jdraaije 11/13/96 - reapply name change from callouts to external proc's / rtaranto 11/10/96 - Add trace event 10278 (used for testing) / bhirano 11/10/96 - modify 4031 error message / rjenkins 11/08/96 - 10149: year 2000 check constraint event / amganesh 11/08/96 - correct action message / jwijaya 11/08/96 - more revision of object errors / vkrishna 11/07/96 - modify object error messages / skrishna 11/07/96 - add 21301 error / rgmani 11/07/96 - Add HO error message #28556 / jbellemo 11/07/96 - DistSecDoms: add errors / dchatter 11/07/96 - add back 24351,24352 which somehow disappeared / dchatter 11/07/96 - fix error msgs for OCI to conform to standards / swerthei 11/07/96 - change explanation for message 19584 / ramkrish 11/06/96 - Reserve 29400-29499 for Oracle8 Cartridges / ramkrish 11/06/96 - 21560: chg Cause, Action; 22285: chg Mesg / jsriniva 11/05/96 - iot: add alter table messages / slari 11/05/96 - add OER(24343) / aroy 11/04/96 - add error to catch NULL LOBS / rherwadk 11/04/96 - add error message #96 / bwadding 11/04/96 - Add event 12837 / opeschan 11/04/96 - add ORA-6505 / tanguyen 11/04/96 - add 22869, remove {2344,22862} / pshah 11/03/96 - Removing error #23600 / skrishna 11/03/96 - add error 21525 / skrishna 11/03/96 - add 22065 error / jwlee 11/02/96 - duplex archive log destinations / rmurthy 11/02/96 - add error 22992 for remote lobs / sjain 11/01/96 - Add new messages / vkrishna 11/01/96 - fixup 22812 and 22915 / celsbern 11/01/96 - Updated #24271 / tanguyen 11/01/96 - change text of 22867 / vkrishna 11/01/96 - fixup 22812 and 22915 / celsbern 10/31/96 - Fixed text for 23419 / sgollapu 10/31/96 - Add error for invalid stmt hndl / rherwadk 10/31/96 - fix for error message #68 / jnewman 10/31/96 - Change purpose of range 8500-8599 / pshah 10/31/96 - Making #25228 and #25229 more informative / pshah 10/31/96 - Adding errors #6525 and #6526 back / jwlee 10/31/96 - remove duplicate rbr posting error / jwijaya 10/30/96 - review and revise object errors / jwlee 10/31/96 - remove duplicate rbr posting error / asriniva 10/30/96 - OSSTK messages / ranantha 10/30/96 - Change comment for event 10938 / ranantha 10/29/96 - Add event 10938 for PL/SQL trace. / azhao 10/29/96 - re-add lob errors 22990 and 22991 / swerthei 10/25/96 - add 19657 / wuling 10/28/96 - add 29300-29321, fix 21000 / arhee 10/28/96 - add event for IPC tracing / jwlee 10/25/96 - error 10199 / tpystyne 10/25/96 - change 27001 and add 27020 / aroy 10/25/96 - Add error no 24336 / bhimatsi 10/24/96 - 22868-9 : lobs and drop tablespace errors / mluong 10/24/96 - fix compilation error / mluong 10/24/96 - get fix from bhirano / vkrishna 10/24/96 - modify 22807, nested table errors / twang 10/23/96 - new error for pdml global deadlock / mcoyle 10/23/96 - Add 12835 for OPS_ADMIN_GROUP / tcheng 10/22/96 - add 25008 / jnewman 10/22/96 - cosmetic changes start 280 10/22 / slari 10/21/96 - add OER(24337) / sgollapu 10/21/96 - Add Readonly Error for SvcCtx / mluong 10/21/96 - fix merge problem. / mluong 10/21/96 - fix compile error / jnewman 10/21/96 - cosmetic changes to errors 10/21 / skrishna 10/21/96 - add 21602 / slari 10/21/96 - add OER(24337) / jsriniva 10/19/96 - iot: alter error messages / bhirano 10/18/96 - add new ksm errors for large pool init.ora parameter / lchidamb 10/18/96 - add date, display type related errors / bwadding 10/18/96 - add events for kxib / hasun 10/17/96 - Add 12038 for snapshots / mluong 10/17/96 - fix compile error / jdraaije 10/16/96 - callouts have been renamed to external procedures / rhari 10/16/96 - More external procedure error messages / hasun 10/16/96 - Add error 12037 for snapshots / ramkrish 10/16/96 - Reserve 22280-22299 for LOB/FILE; Free 24280-24299 / rpark 10/14/96 - fix error 1794 to say 32 instead of 16 max num of co / aroy 10/12/96 - add error messages for npilfrd/wr / wuling 10/11/96 - reserve 29300-29399 for dbms_pitr, change 21001 / tcheng 10/10/96 - change message 22979 / slari 10/09/96 - add OER(24336) / slari 10/09/96 - add OER(24336) / slari 10/09/96 - add OER(24336) / tsaulys 10/09/96 - add 1061 / sgollapu 10/08/96 - Remove "in " occurrences in err msgs / pshah 10/07/96 - Add event #10931 / rwessman 10/07/96 - added messages for the Oracle Security Service / pshah 10/07/96 - Add event #10931 / fge 10/03/96 - update message 25112 / ldoo 10/03/96 - Add 23419 / tanguyen 10/03/96 - incomplete and mutually referring types (err 22867) / jnewman 10/03/96 - cosmetic change to cause/action / ato 10/02/96 - relocate AQ export check errors / ademers 10/02/96 - add 23384-88, 26531 / ramkrish 10/02/96 - Fix mrgerr during add_ro_bfile(09/19) xref v184/v185 / rherwadk 10/02/96 - enhance error message ORA-4017 / rjenkins 10/01/96 - 2k char 4k varchar2 / ldoo 10/01/96 - Add 23418 / jsriniva 09/30/96 - iot: add alter-related error msgs / ldoo 09/26/96 - Add 26563 / arhee 09/26/96 - bug 403081 / swerthei 09/25/96 - add 19657, 19658 / rmurthy 09/25/96 - errors for Alter Lob / kosinski 09/24/96 - Merge Win32 changes into base development / tlee 09/24/96 - update mesg 1211 and 1592 / fge 09/24/96 - add 25122 for partitioned bitmap index / fge 09/20/96 - 25111: change message text / rgmani 09/20/96 - Add new HO error messages #28524 to #28530 / varora 09/20/96 - add no map/order method error / jcohen 09/18/96 - update 25113: GLOBAL not allowed for bitmap index / jcohen 09/18/96 - update 25113: GLOBAL not allowed for bitmap index / ldoo 09/18/96 - Change mesg of 23326 and obsolete 23311 / ramkrish 09/18/96 - reserve 22285-99 for KOLF - Generic BFILE manager / celsbern 09/18/96 - add messages for DBMS_HO package / adowning 09/17/96 - v8 import of snapshots / schandra 09/16/96 - 2075: concurrent attempts to heuristically end trans / masubram 09/13/96 - Add 12036 for updatable snapshot log not empty / jarnett 09/12/96 - bug 336488 merge: errors 160-163 / dchatter 09/12/96 - delete merge symbols / hasun 09/11/96 - Modify 12004 to be more specific / esoyleme 09/11/96 - update 25425 and 25408 / adowning 09/10/96 - snapshot log validation messages / jboonleu 09/10/96 - add koh error code / jnath 09/10/96 - bug 346936: repcat error 23356 / wbridge 09/09/96 - tablespace point in time recovery / aroy 09/09/96 - add messages for NCHAR support / jstamos 09/09/96 - fix 23346 for bug 398867 / rmurthy 09/09/96 - modify message for error 22894 / tcheng 09/06/96 - reuse 25007 / asgoel 09/06/96 - Added errors for and validating replication code / tlee 09/04/96 - update conversion mesgs / khnguyen 09/04/96 - add msg 12704 for character set mismatch / whuang 09/03/96 - adding the event for array index insertion / nmichael 08/30/96 - More error messages for bulk SQL / rhari 08/30/96 - Add error #6524 for unsupported callout options / tcheng 08/28/96 - fix mesg 25007 / surman 08/28/96 - Merge 367403 to 8.0.2: Fix 1002 mesg / jsriniva 08/28/96 - allow last index column in include clause for iots / sthakur 08/28/96 - add missing descriptor message / anori 08/27/96 - remove OIDGENERATORS error message / edarnell 08/27/96 - add collections messages / ato 08/27/96 - add AQ error for datatype mismatach / pshah 08/26/96 - Adding error messages for AQ admin interface (create / tcheng 08/26/96 - add 25007 / rmurthy 08/23/96 - add error 22893-94 for scoped REFs / jklein 08/23/96 - bug 284399 - error codes without leading zeroes / jklein 08/23/96 - bug 332114 - 10200, 10203 events switched / jklein 08/23/96 - bug 342658 - improve cause for error 701 / tpystyne 08/23/96 - add 238 / ssamu 08/22/96 - add exchange error msg / jsriniva 08/22/96 - add 'column name expected' error msg for iots / swerthei 08/22/96 - add 19656 / dchatter 08/22/96 - remove merge comments / rbodamer 08/21/96 - Add HO error messages / nmichael 08/21/96 - New error messages for dbms_sql / ldoo 08/21/96 - Add 23393 and 23394 / ato 08/21/96 - add more dbms_aqadm error messages / akruglik 08/20/96 - add msg 14118 / asurpur 08/19/96 - Adding new message for expiration of external accoun / aroy 08/19/96 - oci nchar support messages / heri 08/19/96 - Add 10148 : use old random generator / tcheng 08/18/96 - add 25006 / dchatter 08/16/96 - add error message - handle already initialized / tcheng 08/16/96 - 22906: disallow DML on THE expression / rxgovind 08/15/96 - add error 22930 / sgollapu 08/14/96 - Add 24327 / tanguyen 08/13/96 - add 22862-3 / rjenkins 08/13/96 - add error for changing constraint / swerthei 08/12/96 - remove 19591 / ssamu 08/12/96 - get rid of 14502, 14077, use 2149 / jwijaya 08/11/96 - add objects option not installed / jwijaya 08/11/96 - add objects option not installed / swerthei 08/08/96 - add 19653 / vkrishna 08/07/96 - add Nested Table related messages / akruglik 08/07/96 - add msg 14117 / smuralid 08/06/96 - add 22802, 22803 / rherwadk 08/06/96 - fix message text for error# 2096 / swerthei 08/05/96 - add 19649, 19650, 19651, 19652 / jarnett 08/02/96 - bug 371279 - limit maximum call depth / rxgovind 08/02/96 - add error 22928 / tcheng 08/01/96 - add OBJECT keyword to WITH OID clause / schandra 07/30/96 - change 2020 error message / aborr 07/30/96 - kccmus gets error if created control mounted / tanguyen 07/29/96 - enhance 2344 to include create type / bnainani 07/29/96 - Change cause for 02226, add 10515, 23600 / rmurthy 07/28/96 - add errors 22886 - 22892 for REFs / ato 07/26/96 - add 24277 / rhari 07/25/96 - Error 6523 for max callout arguments / fge 07/24/96 - merge bitmap from 7.3.3 to 8 beta1 / varora 07/24/96 - add 22885 error message / atsukerm 07/23/96 - add new DBMS_SPACE messages. / swerthei 07/23/96 - change text for 19625 / adowning 07/19/96 - add 23392 / vkrishna 07/19/96 - add 22909 / akruglik 07/19/96 - error 14074 will be used only for ADD PARTITION / asgoel 07/17/96 - Adding two error numbers for debugging and tracing r / mcoyle 07/16/96 - Add 12832 for GV$ hard affinity / gpongrac 07/16/96 - add 295 / tcheng 07/16/96 - add 22977,22978,22979 / kmuthukk 07/15/96 - add v7 compat event for pl/sql fixed-char binds / vkrishna 07/12/96 - add error for null nested table instabce / tcheng 07/12/96 - add 22975, 22976 / tcheng 07/12/96 - fix 22970 / adowning 07/10/96 - 23389: obsolete switch_snapshot_master / tlahiri 07/09/96 - add 00377: too many relog ops during a direct load / mchien 07/09/96 - fix error msg / anori 07/07/96 - add alter table restriction messages for ADT columns / swerthei 07/01/96 - add 19638 / slari 06/28/96 - OCI error for exec if iter = 0 and non-select / swerthei 06/27/96 - add 19560 / tanguyen 06/26/96 - reuse 2344 for replacing type with OID clause / smuralid 06/26/96 - add 2348-2350 / tanguyen 06/25/96 - remove 2344 / akruglik 06/25/96 - add mesages complaining about length of partition bo / fputzolu 06/25/96 - add event 10124 to force creation of segmented array / ksriniva 06/24/96 - add error messages for sls.c / rwessman 06/24/96 - Updated Oracle Security Service errors. / jdraaije 06/20/96 - add callout agent connection errors / slari 06/20/96 - add oci error messages / ssamu 06/20/96 - add message for object in PTI / jboonleu 06/20/96 - update messages for KOC / dchatter 06/19/96 - 24325: a converted svc cannot beused in V8 calls / arhee 06/19/96 - change IPC error messages / varora 06/19/96 - add method errors / sthakur 06/18/96 - clean up kod and koka error messages / asurpur 06/18/96 - change password expired message / sdas 06/18/96 - iot: add iot direct-load error message / schandra 06/17/96 - Convert XA to use new OCI / tarora 06/17/96 - eliminated some unnecessary skgfr msgs, changed / 27053 / aroy 06/14/96 - add error 24801 / jsriniva 06/13/96 - add iot overflow in tablespace but not iot top index / akruglik 06/12/96 - fix for bugs 373151 and 373181 / rwrivera 06/11/96 - update IPC messages / rherwadk 06/10/96 - OER 111: don't allow mts_servers > mts_max_servers / gngai 06/06/96 - Added 8178 for SET TRANSACTION / swerthei 06/03/96 - 294 - invalid archive format specifier / schandra 06/02/96 - session migration password / ramkrish 06/02/96 - dbms_lob: rephrase mesg with format char changes / skrishna 06/02/96 - add 22166 and 22167 / rxgovind 06/02/96 - add errors for trusted 3gl cbks / tpystyne 06/01/96 - add events 10326 and 10327 / tcheng 05/31/96 - add 22974, 2345 / jwlee 05/30/96 - minimum support of Lamport SCNs / tcheng 05/30/96 - add 25005 / tanguyen 05/30/96 - add 2346 / cxcheng 05/29/96 - cleanup before beta 1 - remove 19400-19449 / rwessman 05/29/96 - Need to add number space for Oracle Security Service / tarora 05/29/96 - change 27014 / swerthei 05/28/96 - remove 19577, 19578, change 19571, 19588 / twang 05/25/96 - error messages for lock manager process termination / hasun 05/24/96 - Add snapshot error message 12030 / ldoo 05/23/96 - New repl security model / akruglik 05/23/96 - add message 14110 / akruglik 05/23/96 - define event 14087; add message 14108 / tarora 05/23/96 - improve/add SKGFQ msgs / skotsovo 05/23/96 - add more lob errors / akruglik 05/22/96 - rephrase msg 14041 / cxcheng 05/21/96 - change error message 22314 to be more general / swerthei 05/21/96 - add 19637 / tarora 05/21/96 - add message for skgfq / akruglik 05/21/96 - partition bound syntax changes: / reuse T_HIGH and T_VALUE messages for / T_LESS and T_THAN / akruglik 05/21/96 - mark messages mentioning TABLE$OR$INDEX$PART$NUM not / to be documented / bhimatsi 05/21/96 - add errors for LOB clause parsing / esoyleme 05/21/96 - Fill in failover errors / ldoo 05/20/96 - Add 26500 again / jgautam 05/17/96 - PDML: Add messages for PDML restrictions / jgautam 05/17/96 - PDML: Add messages for PDML restrictions / hasun 05/16/96 - Add snapshot error message for LOB filter columns / swerthei 05/16/96 - remove 19603 / bhimatsi 05/15/96 - add lob segment space errors / rjenkins 05/15/96 - deferred unique constraints / dchatter 05/14/96 - adding/modifying OCI 8 messages / ddas 05/13/96 - enhance cost info for rowsources / jwijaya 05/09/96 - fix the message of 22165 / tanguyen 05/08/96 - remove USAGE from 2305, add 2344 / nmacnaug 05/08/96 - update gc error messages / abrumm 05/07/96 - error codes for index maint options / ramkrish 05/07/96 - Update dbms_lob errors in new range / jcohen 05/07/96 - QKA Disable Bitmap And-EQuals / hasun 05/06/96 - replmerge / skrishna 05/06/96 - add 22164 and 22165 / ssamu 05/02/96 - split 2266 into drop & truncate messages / tarora 05/02/96 - add msgs for skgfrofl / ssamu 05/02/96 - split 2266 into drop & truncate messages / tcheng 05/01/96 - add 25004 / cxcheng 05/01/96 - add error message 22319 / cxcheng 04/29/96 - add message 22321 / cxcheng 04/26/96 - add message 19491 for delete / tanguyen 04/23/96 - fix 2343 - add "in other schemas" / schandra 04/21/96 - loosely-coupled branches / swerthei 04/20/96 - change text for 19576 / nlewis 04/18/96 - DistSecDoms: add msgs 28020-28024 / wbridge 04/18/96 - keep tablespace info in controlfile / akruglik 04/18/96 - redefine 14084 since it is no longer meaningful / skrishna 04/17/96 - add error messages for collection (KOLC) / jwlee 04/16/96 - add events for testing tablespace-relative DBAs / atsukerm 04/12/96 - new error messages for DBMS_SPACE. / abrumm 04/11/96 - OER(2365) Direct Load State --> Index Unusable / tarora 04/11/96 - add to some kcc msgs / tarora 04/10/96 - add 27073 / rwrivera 04/09/96 - getting IPC error messages / tanguyen 04/09/96 - add 2342-2343 / wuling 04/09/96 - add message 19706, 19707 / pravelin 04/04/96 - add Heterogeneous Option (HO) error messages / aborr 04/04/96 - error if use snapshot routines with backup cfile / swerthei 04/02/96 - change text for 19586 / asurpur 04/02/96 - Dictionary Protection Implementation / aborr 03/29/96 - eliminate #01214: maxloghistory limit exceeded / jmuller 03/29/96 - Fix bug 343966: flag uses of types before their / " 03/29/96 declarations; but allow this to be turned off for / " 03/29/96 backward compatibility / chong 03/26/96 - DBMS_LOB moved from 23385-23399 to 24280-24299 / ldoo 03/25/96 - Reserve a range for replication PL/SQL packages / swerthei 03/25/96 - add message for recovery catalog record mismatch / rbodamer 03/18/96 - Create Error range for Heterogeneous Option / rbodamer 03/18/96 - Correct Error range for Heterogeneous Option / swerthei 03/14/96 - add message 19708, remove 19620 / ldoo 03/13/96 - Reserve 26500 - 26999 for Replication / ldoo 03/12/96 - Add 26500 / ldoo 03/12/96 - Reserve a range for replication / ato 03/11/96 - allocate sub-range for oltp features / swerthei 03/11/96 - more SMR messages / aborr 03/08/96 - dup name check on snapshot controlfile name / asurpur 03/08/96 - Reserving error range for security related errors / tanguyen 03/08/96 - fix 2305 to disallow {ALTER, DELETE} / aborr 03/07/96 - bug257523: warn if resetlogs will fail after inc rcv / rxgovind 03/06/96 - add error 22929 / cxcheng 03/06/96 - add message for ortbeg() / slari 03/05/96 - add kpu error 243xxx / tarora 03/02/96 - add message for SKGFR / swerthei 03/01/96 - change message 19625 / bhimatsi 02/29/96 - Minimum Extent clause for tablespace (25120-21) / aborr 02/23/96 - KCC fixed table inconsistent due to concurrent updat / tanguyen 02/23/96 - add 2305 for granting priv on type / swerthei 02/20/96 - add retryable-error semantics / swerthei 02/20/96 - add errors for SwitchToCopy / tarora 02/19/96 - add slnrm msgs / aborr 02/16/96 - correct controlfile resize error message (224) / emendez 02/15/96 - merging all branches / tpystyne 02/14/96 - add event 10325 / tarora 02/14/96 - removed 213, 1586. corrected func name in skgfr msgs / ltan 02/08/96 - PDML:add 1687,25119 for tablespace LOGGING attribute / aborr 02/06/96 - reword some controlfile-related messages / swerthei 02/02/96 - Restore messages for SMR / tarora 01/31/96 - rename so->sksa. added ksfq msgs / swerthei 01/31/96 - more SMR messages, for milestone 4 / aborr 01/31/96 - add error messages for V8 controlfile / swerthei 01/29/96 - enhance SMR messages / tanguyen 01/30/96 - add 2304 for OID clause in CREATE TYPE / ramkrish 01/25/96 - reserve 23385-23399 for dbms_lob (& file) package / swerthei 01/22/96 - more SMR messages / wuling 01/15/96 - add messages for krbi (19700-19705) / swerthei 01/15/96 - change SMR string length messages / smuralid 01/15/96 - add ORA-2341 => "non-queryable types in sql" / jweisz 01/05/96 - change second MODIFiED to MOD HISTORY / tarora 01/03/96 - added message for skgfr (27060) / usundara 01/02/96 - (rtaranto) merge from /main/712: Update message 4062 / aho 12/28/95 - deferred unique constraints - index trace / tarora 12/27/95 - added more information for some OSD errors / gswart 12/26/95 - New snapshot too old error message / nmacnaug 12/20/95 - correct parameter name / sthakur 12/20/95 - add KOKA errors / ldoo 12/19/95 - Add trace events for internal triggers / jwijaya 12/19/95 - add ranges for object SQL / abrumm 12/15/95 - add direct load error msg / tcheng 12/13/95 - add mesg for constraints on row-type table / nmacnaug 12/12/95 - kcl parsing error / tarora 12/01/95 - added message for ksfq / tarora 11/30/95 - add messages for skgfq, skgfr osds, shrink / OSD error range (27000-27299) / tanguyen 11/28/95 - reassign message numbers and fix msgs for TYPE DDL / tanguyen 11/28/95 - fix merge problem / tanguyen 11/28/95 - reassign message numbers and fix messages for / TYPE DDL / cxcheng 11/28/95 - fix merge problems / qtran 11/22/95 - recover modification history / jhyde 11/21/95 - add events 10711-10716 / atsukerm 11/21/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm / tcheng 11/17/95 - add error mesg for extent view / rherwadk 11/17/95 - add error messages for skgm / bhirano 11/17/95 - add init.ora parameter errors / swerthei 11/16/95 - reserve 27000-27499 for V8 Unix OSDs / aho 11/16/95 - iot : parse errors / swerthei 11/15/95 - change text for 1507 and add more explanation / lwillis 11/14/95 - 10118 CBO enable hash costing / lwillis 11/09/95 - 10117 parallel cost model / lthieme 11/07/95 - add message text for simulated error ORA-07347 / swerthei 11/02/95 - reserve 19500-19998 for SMR / msimon 11/02/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm / jweisz 11/01/95 - Add pls error msgs 6515,16,17 for rhari / akruglik 10/31/95 - add messages for index partition maintenance operati / wbridge 10/30/95 - flush buffer cache on redo corruption / qtran 10/30/95 - reserve trace events range for bitmap row sources / akruglik 10/30/95 - rephrase mesg 14070 to indicate that options are / allowed for partitioned indices OR with REBUILD / ssamu 10/27/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm / rjenkins 10/27/95 - deferred constraints / hjakobss 10/27/95 - events 10107-10116 / rtaranto 10/26/95 - Update message 4062 / abrumm 10/24/95 - add generic Rejected message / jklein 10/20/95 - bitmap dml / achaudhr 10/19/95 - improve diction of some error msgs / ssamu 10/18/95 - new error message for split/move partition / ssamu 10/17/95 - new analyze messages / fputzolu 10/17/95 - PTI: add error 14403 for partition locking / arhee 10/17/95 - add event 10374 / bhimatsi 10/16/95 - bug 313376, 1557 should take argument / achaudhr 10/16/95 - UJV: new errors for updatable join views / rmirchan 10/15/95 - 12827 parallel min percent message / lfeng 10/14/95 - Add Spatial Data Option messages / aho 10/11/95 - alter index allocate extent / jcohen 10/10/95 - bitmap index checkin / abrumm 10/08/95 - direct path loader partition support / jbellemo 10/05/95 - add event 10145 / wbridge 10/04/95 - do not automatically use a file name from the log / rhari 10/02/95 - add event 10928 / cxcheng 09/29/95 - modify collection type messages / akruglik 09/28/95 - add a message to be issued if a user tries to trunca / msimon 09/26/95 - Add in preliminary version of kdl subsystem / pshah 09/25/95 - add error message #00124 for MTS / smuralid 09/22/95 - add ORA-2335 through ORA-2337 / smuralid 09/21/95 - change ORA-953 (was "invalid index name") / slari 09/21/95 - b301008, add OER(24307) for osetpi / jtellez 09/21/95 - Add multi instance index create event 10709 / gngai 09/21/95 - Added cause and action to several msg / smuralid 09/20/95 - add ORA-2327 through ORA-2334 / jboonleu 09/20/95 - update error message file with ORI errors / hbergh 09/18/95 - bug 274084: error when system rollback seg specifie / tanguyen 09/15/95 - add 21602: dropping type with dependency / boki 09/13/95 - fix error messages 23430 - 23434 / scorcora 09/12/95 - Bug #197210, OER(100) to 123, 100 for ansi not found / pshah 09/12/95 - add error range for Advanced Queueing (25200-25699) / hasun 09/12/95 - Modify message #23375 / hasun 09/08/95 - Modify Cause and Action of 23309 / akruglik 09/07/95 - messages for CREATE INDEX processing / lwillis 09/01/95 - Add 10076 enable cp join costing / jbellemo 08/31/95 - merge changes from branch 1.564.720.43 / gdoherty 08/31/95 - mergetrans fix_pti_merge_bugs / schandra 08/30/95 - modify error message for ORA-03296 / akruglik 08/29/95 - add msg 14071 / akruglik 08/29/95 - add msg 14070 / lthieme 08/23/95 - resolve standby database inspection issues / aborr 08/23/95 - bug 298769: stop kcvirv loop when kcvucp gets IO er / ssamu 08/22/95 - add new analyze errors / ksriniva 08/17/95 - add UNIX message 7444 for oradbx / ssamu 08/14/95 - change text for message / dsdaniel 08/11/95 - merge PTI with Objects / dsdaniel 08/11/95 - reserve range 14000 to 14999 for PTI / ksriniva 08/04/95 - add errors for invalid heap dumps / schatter 08/03/95 - add event 10375 / hasun 08/03/95 - Modify replication error 23381 / jbellemo 08/02/95 - fix up Cause phrasing / mramache 08/01/95 - clarify error 4097 / jbellemo 08/01/95 - TRUSTSP: add 12436 and replace 991, 12432 / (support for psdswc, PL/SQL switches). Add events / 10925, 10926, 10927 for pl/sql switches to control / behavior-change bugfixes 237911, 190119 and 235190. / akruglik 08/01/95 - merge changes from ak_BIG_PTI 1.0 NDE view / ssamu 07/28/95 - add new message / akruglik 07/27/95 - define msgs 13011-13013, 13016 / hjakobss 07/26/95 - event 10106 / ssamu 07/24/95 - new messages for analyze / ssamu 07/24/95 - add messages for partitioned table analyze / emendez 07/23/95 - cheking RCS rev to stabilize 7-7 / hjakobss 07/20/95 - event 10105 / skaluska 07/18/95 - PTI: add error message for no such partition / mramache 07/18/95 - modify meaning of error 4097 / boki 07/13/95 - fix message for 23377 / bhimatsi 07/11/95 - merge changes from branch 1.564.720.42 / jleo 07/07/95 - add event 10104 to dump statistics for hash join / arhee 07/05/95 - new events for ksim testing / rhari 07/03/95 - Reserve 13000 - 13199 for Oracle7 MultiDimension / tcheng 06/30/95 - merge with k7030101 / boki 06/28/95 - modify for offline instantiation / ajasuja 06/28/95 - change message 6575 / akruglik 06/26/95 - merge changes to support CREATE/DROP/ALTER partition / amozes 06/22/95 - add event for table queue statistics / akruglik 06/21/95 - remove definitions of messages used for reporting in / tcheng 06/16/95 - merge o8 changes; add to SCCS / usundara 05/31/95 - [merge changes from revision 1.564.720.44] / reserve event space 10925 through 10974 for PL/SQL / hasun 05/30/95 - Add error for invalid connection qualifier / jbellemo 05/12/95 - #221259: remove 1415 / add event 10069 / aho 05/12/95 - even more errors for recreate index / hjakobss 05/11/95 - event 10103 / fputzolu 05/10/95 - PTI: reserve range 13400-13500, add 13400,1,2, chang / lthieme 05/09/95 - fix #278985 do not allow mnt with no lock mgr. / rxgovind 05/05/95 - change error 6514 / nmichael 05/04/95 - Event 10277 - New event for sharing cursors / svenkate 05/03/95 - events for direct read / slari 05/03/95 - change ORA-02391 / boki 05/03/95 - bug 279979 -- add new error msg / akruglik 05/03/95 - ALTER TABLE errors / thayes 05/02/95 - Add event to allow PERSISTENT DLM ops / lthieme 05/02/95 - fix #151892 check control file size on open / kosinski 05/02/95 - Merge from 0.1 BIG snapshot / aho 05/02/95 - more errors for recreate index / dchatter 05/01/95 - reword message 3127 and add new message 3131 / rxgovind 04/17/95 - add error 6514 / jwlee 04/17/95 - rewrite 1241 slightly / thayes 04/14/95 - Add releasable lock DLM error / hbergh 04/14/95 - add new cause/action to 1545 / jwlee 04/10/95 - add external cache error 1241 / gdoherty 04/10/95 - set transaction isolation level / lthieme 04/06/95 - fix inconsistant spelling errors / lthieme 04/06/95 - fix consistant spelling errors / cozbutun 04/04/95 - add 6580 / nmichael 04/02/95 - merge changes from branch 1.564.720.39 / dchatter 03/28/95 - new messages for piecewise / bhimatsi 03/27/95 - merge changes from branch 1.564.720.35 / jtellez 03/22/95 - 962 - New errors for skxf / jklein 03/22/95 - remove error 2474 / hasun 03/20/95 - Fix checkin errors / slari 03/16/95 - add thread safety changes / drady 03/10/95 - Oracle TRACE changes / aho 03/10/95 - fix ci - merge screwup / hjakobss 03/09/95 - event 10102 / rlim 03/08/95 - rewrite error 4043 / dchatter 03/06/95 - merge changes from branch 1.564.720.36 / lchidamb 03/05/95 - add error code 24303 / nmichael 03/04/95 - Bug 265643 - Error for binds in trigger when clause / gngai 03/03/95 - Added errors esfor ALTER SYSTEM DUMP UNDO / wbridge 03/01/95 - external cache / rlim 02/28/95 - rewrite error 4043 / jklein 02/27/95 - event for skip corrupted index / mramache 02/22/95 - stored triggers / jcohen 02/16/95 - events 10804 and 10805 for ksxb and rso / atsukerm 02/16/95 - Sort Segment implementation / ksriniva 02/14/95 - document range for generic debugger / jklein 02/14/95 - unlimited extents / jwlee 02/13/95 - merge changes from branch 1.564.720.33 / dchatter 02/13/95 - add new messages for upilog / hjakobss 02/10/95 - events 10092 and 10093 / arhee 02/09/95 - merge changes from branch 1.564.720.10 / pgreenwa 02/07/95 - add debugging event for ksi.c / lthieme 02/07/95 - merge changes from branch 1.564.720.34 / wbridge 02/06/95 - standby database errors / lthieme 02/06/95 - issue 2495 error only for read-only tablespaces / jwlee 02/06/95 - error codes for resilvering testing OSDs / boki 02/06/95 - add error codes for table comparison feature in 7.3 / rhari 02/05/95 - merge changes from branch 1.564.720.32 / error messages for utl_pg / jwlee 02/03/95 - Add error codes for resizable data files / rhari 02/02/95 - merge changes from branch 1.479.710.81 / lthieme 02/02/95 - merge changes from branch 1.564.720.31 / lthieme 02/02/95 - fix #260249, hold ts$ and file$ enques on resize / hjakobss 02/01/95 - events 10089 and 10091 / lchidamb 01/31/95 - reserve range for UPI/OCI calls: 24300 - 24499 / tanguyen 01/30/95 - add 2304 for OID clause in CREATE TYPE / hasun 01/25/95 - Modify and add errors for Rep3 - Object Groups / wbridge 01/23/95 - do not allow log switch in backup controlfile / usundara 01/19/95 - bugfix 255455 - merge from rev 1.564.720.28 / fix plsql error handling - new errors 6540 - 6549 / hjakobss 01/17/95 - event 10088 / atsukerm 01/10/95 - DEALLOCATE UNUSED space feature / adowning 01/10/95 - fix typos / wbridge 01/04/95 - add support for resilvering of OS mirrors / hjakobss 01/03/95 - event 10086 / dsdaniel 12/23/94 - merge changes from branch 1.564.720.6&8&16&18&24 / jstamos 12/21/94 - add repcat errors (1.564.720.7&20) / bquigley 12/21/94 - ora-1034 add cause/action / lchidamb 12/14/94 - merge changes from branch 1.564.720.5 / ksriniva 12/14/94 - merge changes from branch 1.564.720.22 / msimon 12/13/94 - merge changes from branch 1.564.720.23 / msimon 12/12/94 - merge changes from branch 1.479.710.82 / msimon 12/12/94 - Fixes for bug 249693 - Add event 10320 / ksriniva 12/12/94 - add ORA-17, ORA-7445, and 10077 / dsdaniel 12/12/94 - merge changes from branch 1.479.710.76&77&78&80 / thayes 12/08/94 - Fix name of parameter in msg 406 / boki 12/01/94 - adding new error numbers for schema offline instant / boki 12/01/94 - adding new error numbers and msgs for schema offlin / aho 12/01/94 - rci trace event 10610, 2095 / jstamos 11/30/94 - merge changes from branch 1.479.710.79 / jstamos 11/30/94 - add periods and capitalization: 23306 - 23320 / jbellemo 11/30/94 - merge changes from branch 1.564.720.19 / hasun 11/29/94 - Change cause/action statements for (2094,23364) / ksriniva 11/23/94 - change 10090 to 10095 / jbellemo 11/23/94 - remove 1966 / jbellemo 11/22/94 - fix up 12495, again / hasun 11/22/94 - Add messages for Replication factoring (23364,2094) / dsdaniel 11/18/94 - execution of deferred RPC disabled / dsdaniel 11/17/94 - merge changes from branch 1.479.710.74 / jstamos 11/16/94 - merge changes from branch 1.479.710.75 / jstamos 11/16/94 - add 23353 for repcat / dsdaniel 11/15/94 - 23352 - deferred rpc error message / thayes 11/14/94 - Change reference to compatible parameter / ksriniva 11/14/94 - add error codes for generic oradbx / jbellemo 11/14/94 - remove 1948 / dchatter 11/14/94 - merge changes from branch 1.564.720.9 / dchatter 11/14/94 - merge changes from branch 1.564.720.14 / rhari 11/13/94 - merge changes from branch 1.564.720.11 / jstamos 11/11/94 - merge changes from branch 1.479.710.72 / rtaranto 11/10/94 - merge changes from branch 1.564.720.15 / rtaranto 11/10/94 - merge changes from branch 1.479.710.73 / rtaranto 11/10/94 - Update Cause and Action comments for event 04097 / dchatter 11/09/94 - merge changes from branch 1.479.710.70 / rtaranto 11/02/94 - merge changes from branch 1.564.720.12 / jbellemo 11/02/94 - merge changes from branch 1.564.720.13 / jbellemo 11/02/94 - merge changes from branch 1.479.710.64 / rtaranto 10/31/94 - merge changes from branch 1.479.710.71 / dsdaniel 10/27/94 - new replication messages / rhari 10/25/94 - merge changes from branch 1.479.710.63 / arhee 10/20/94 - merge changes from branch 1.479.710.69 / rtaranto 10/19/94 - Add event 04097 / hjakobss 10/16/94 - event 10078 / dchatter 10/14/94 - messages of 3125, 3126, 3127 backported from 7.2 / dchatter 10/14/94 - change 3124 to an internal error and add 3128 / jstamos 10/13/94 - merge changes from branch 1.479.710.58 / dsdaniel 10/13/94 - add 1085 / adowning 10/13/94 - merge changes from branch 1.479.710.65 / lchidamb 10/12/94 - add 1084: invalid parameter to oci call. / hjakobss 10/10/94 - event 10077 / rjenkins 10/06/94 - obsoleting 2255 / msimon 10/05/94 - merge changes from branch 1.564.720.1 (bug 209788) / lchidamb 10/05/94 - changed error #3112 / hjakobss 10/05/94 - event 10076 / rjenkins 10/04/94 - merge changes from branch 1.564.720.2 / arhee 10/04/94 - add event 10377 / rjenkins 10/03/94 - merge changes from branch 1.479.710.60 / jstamos 09/30/94 - reserve error numbers already in use / for refresh groups, snapshots, and job queues / jbellemo 09/30/94 - fix up 12495 / rhari 09/29/94 - some more messgaes for UTL_RAW and UTL_PG / (now complete 08401 - 08499) / jbellemo 09/28/94 - add 12495 / hjakobss 09/28/94 - event 10076 / adowning 09/28/94 - add replication PL/SQL errors / rhari 09/27/94 - UTL_RAW & UTL_PG (8401 -- 8443) / msimon 09/27/94 - Sequence numbers rewrite (bug 239487) / msimon 09/26/94 - merge changes from branch 1.479.710.59 (bug 209788) / jbellemo 09/23/94 - add event 10090 / agupta 09/15/94 - 231813 - add message for creating segment / rjenkins 09/09/94 - removing 2255 / msimon 09/07/94 - Changes for bug 209788 / jstamos 09/02/94 - externalize 23306 - 23320 for replication / ksriniva 08/31/94 - add WMON termination error message / atsukerm 08/31/94 - merge changes from branch 1.479.710.57 / abrumm 08/22/94 - Change 1854 due to max Julian date increase by CORE / atsukerm 08/18/94 - new space management events / hjakobss 08/15/94 - event 10075 / cozbutun 08/15/94 - change a few comments / gpongrac 08/10/94 - merge changes from branch 1.479.710.55 / bhirano 08/10/94 - merge changes from branch 1.479.710.56 / dleary 08/05/94 - add 1781-1784 for UNRECOVERABLE / bhirano 08/05/94 - add (unix-specific) core file size events / gpongrac 08/01/94 - revise message for 292 and 293 / dsdaniel 07/28/94 - 1085 preceding error in deferred rpc / lthieme 07/27/94 - resolve inspection issues for resizeable datafiles / alingelb 07/25/94 - fix 1163 / dsdaniel 07/21/94 - merge changes from branch 1.479.710.53 / dsdaniel 07/21/94 - deferred rpc export error 23327 / svenkate 07/19/94 - changes to err msg 1163 / dsdaniel 07/11/94 - merge changes from branch 1.479.710.51 / dsdaniel 07/11/94 - error number conflict with 7.2 / dsdaniel 07/11/94 - dbms_sys_error upgrade / wbridge 07/08/94 - bug 150326: typo in error 66 / ksriniva 07/08/94 - add trace event for kst / gpongrac 07/08/94 - parallel recovery factoring / gpongrac 07/08/94 - merge changes from branch 1.479.710.50 / svenkate 07/07/94 - bug 210900 : changes to err msg 1163 / ksriniva 07/07/94 - merge changes from branch 1.479.710.49 / dchatter 07/07/94 - added error msg for Ref Cursor and Non-blocking OCI / ksriniva 07/06/94 - add events for latch recovery / hrizvi 07/06/94 - add 1657, 10510, 10511, 10512, fix 1545, 1625 / atsukerm 07/06/94 - DBMS_SPACE errors revisited / pgreenwa 07/05/94 - trace event: write timing stats on OPS reco scan / wbridge 06/29/94 - #198847: report 1031 rather than 251 / cbarclay 06/29/94 - add 6504 - Result Sets type mismatch / rjenkins 06/27/94 - 193637: reorg constraint creation / wbridge 06/24/94 - bug 182267 - fix some causes / pritto 06/22/94 - bug 221252 - add TABLESPACE to cause for 1771 / ajasuja 06/21/94 - dbms_pipe error messages / nmichael 06/20/94 - Hash expressions for clusters / wbridge 06/16/94 - specify file number for forced checksum error / jloaiza 06/16/94 - add disable dml locks / jloaiza 06/16/94 - add compatibility for disable table lock / aho 06/15/94 - SYS isn't allowed to create indexes with nfb (2001) / jloaiza 06/14/94 - add disable dml_locks / lthieme 06/03/94 - Resizeable Datafiles Feature / jklein 05/24/94 - fix spelling error for message 6556 / ksriniva 05/16/94 - merge changes from branch 1.479.710.47 / ksudarsh 05/06/94 - relocate error msg / wbridge 04/25/94 - checksum error events / ksudarsh 04/21/94 - parallel query option check / ksriniva 04/19/94 - enhance ORA-4031 and ORA-443 / wmaimone 04/08/94 - merge changes from branch 1.479.710.45 / rlim 04/07/94 - merge changes from branch 1.479.710.44 / dsdaniel 04/07/94 - merge changes from branch 1.479.710.34 / abhide 04/07/94 - merge changes from branch 1.479.710.36 / (merge SQL*NET error codes) / jtellez 04/06/94 - add io tracing event 10705 / ltung 04/05/94 - merge changes from branch 1.479.710.41 / wbridge 04/04/94 - allow end hot backup after crash / ajasuja 04/04/94 - merge changes from branch 1.479.710.32 / wmaimone 03/31/94 - cause/action for 1010 / thayes 03/22/94 - merge changes from branch 1.479.710.38 / rlim 03/21/94 - #206483 - reuse 1037 for maximum cursor memory / exceeded / ltung 03/21/94 - add 12800, 12826 for parallel query execution / dpawson 03/21/94 - merge changes from branch 1.479.710.42 / pgreenwa 03/14/94 - merge changes from branch 1.479.710.39 / ltung 03/10/94 - events 10378, 10379 / dpawson 03/10/94 - Merge in nCube error msgs / Merge in correct Unix messages instead of obsolete / Unix trusted messages / pgreenwa 03/08/94 - add trace event for ksq / hrizvi 03/08/94 - add smon events 10510, 10511 / dpawson 03/04/94 - merge changes from branch 1.479.710.29 / thayes 03/03/94 - Error for simulating block recovery / ltung 03/02/94 - merge changes from branch 1.479.710.37 / dpawson 03/02/94 - Reserve numbers for resizable data files / aho 03/02/94 - add max key length to oer(1450) (bg 198813) / ltung 03/01/94 - parallel clause syntax errors / hjakobss 02/28/94 - merge changes from branch 1.479.710.20 / jwijaya 02/23/94 - merge changes from branch 1.479.710.35 / dpawson 02/08/94 - Reserve a range for DRS6000 / jwijaya 02/03/94 - remove 2300-2350 old odb messages / dsdaniel 02/02/94 - kkxp.c code change / ksriniva 01/27/94 - sigh... really fix ORA-30 message for bquigley / ksriniva 01/27/94 - merge changes from branch 1.479.710.33 / ajasuja 01/26/94 - remove OER-4040 / ksriniva 01/25/94 - merge changes from branch 1.479.710.30 / dsdaniel 01/21/94 - merge changes from branch 1.479.710.31 / wbridge 01/20/94 - add ALTER DATABASE CLEAR LOGFILE command / jbellemo 01/20/94 - merge changes from branch 1.479.710.26 / dsdaniel 01/20/94 - reassign dbms_sys_error range / rjenkins 01/19/94 - merge changes from branch 1.479.710.19 / ksriniva 01/19/94 - fix Cause part of ORA-30 / dpawson 01/19/94 - reserve osd message range / dsdaniel 01/18/94 - merge changes from branch 1.479.710.9&21 / jbellemo 01/17/94 - add event 10063 / ksriniva 01/11/94 - merge changes from branches 1.479.710.{11,15} / ltung 01/10/94 - 10380 - 10382, 12818 - 12820 / jbellemo 01/07/94 - add event 10062 / cozbutun 01/06/94 - merge changes from branch 1.479.710.24 / cozbutun 01/05/94 - modify 4091 to say trigger or function / hrizvi 01/03/94 - bug 189557 - fix explanation of 1599 / dleary 01/03/94 - make event 10383 level a bitfield / gpongrac 12/30/93 - change comments for 12812 and 12813 / dsdaniel 12/27/93 - obsolete ICD error / sjain 12/21/93 - merge changes from branch 1.479.710.17 / jbellemo 12/21/93 - merge changes from branch 1.479.710.18 / jbellemo 12/21/93 - merge changes from branch 1.479.710.14 / hjakobss 12/21/93 - trace event 10060 / dpawson 12/21/93 - merge changes from branch 1.479.710.7 / rjenkins 12/20/93 - creating job queue / jbellemo 12/17/93 - #191402: remove 1930 / sjain 12/16/93 - add new error message for ora-6400 / dleary 12/16/93 - add event 10383 / ksriniva 12/10/93 - add trace event for latch operations / jbellemo 12/08/93 - #190089: add new message 1742 for unterminated comm / jwijaya 12/07/93 - add error ranges for OI/KO/KG / wbridge 11/23/93 - log block checksum / pritto 11/10/93 - merge changes from branch 1.479.710.12 / hkodaval 11/05/93 - merge changes from branch 1.479.710.4 / pritto 11/04/93 - merge in SQL*Net 2.1.2 error messages / pritto 11/02/93 - add 122 / ltung 11/02/93 - fix parallel query messages / ksriniva 11/02/93 - merge changes from branch 1.417.312.18 / dsdaniel 10/30/93 - dbms_sys_error error range / rjenkins 10/28/93 - adding an error message / ksriniva 10/22/93 - fix action part for ora-4031 / dleary 10/20/93 - event 10384 / dleary 10/18/93 - event 10385 / hkodaval 10/14/93 - bug 174446: add new error about read-only tablespac / aho 10/13/93 - merge changes from branch 1.479.710.3 / aho 10/13/93 - add 10606 - debug trace kkri (93.10.13) / aho 10/13/93 - add 10605 - debug trace kkri / aho 10/05/93 - forgot comment character / aho 10/05/93 - add event to test parallel create index (10605) / change 1404 (bug 181123) / ksudarsh 10/01/93 - restore deleted messages / jklein 09/29/93 - reserve ksepec events for scafs / mmoore 09/22/93 - add error range for pga/appc gateway / pritto 08/23/93 - re-insert Trusted Oracle messages / ksudarsh 08/10/93 - parallel query option / cozbutun 08/09/93 - add 6575 / aho 08/05/93 - add create index fastpath event / pritto 07/29/93 - merge in sql*net 2.1 error messages / wbridge 07/27/93 - disallow rolling upgrade between point releases / agupta 07/22/93 - add errors for cluster extent overflow / jcohen 07/20/93 - reserve events 10370-10386 for parallel SQL / hasun 01/25/95 - Modify and add errors for Rep3 - Object Groups / wbridge 01/23/95 - do not allow log switch in backup controlfile / usundara 01/19/95 - bugfix 255455 - merge from rev 1.564.720.28 / fix plsql error handling - new errors 6540 - 6549 / hjakobss 01/17/95 - event 10088 / atsukerm 01/10/95 - DEALLOCATE UNUSED space feature / adowning 01/10/95 - fix typos / wbridge 01/04/95 - add support for resilvering of OS mirrors / hjakobss 01/03/95 - event 10086 / dsdaniel 12/23/94 - merge changes from branch 1.564.720.6&8&16&18&24 / jstamos 12/21/94 - add repcat errors (1.564.720.7&20) / bquigley 12/21/94 - ora-1034 add cause/action / lchidamb 12/14/94 - merge changes from branch 1.564.720.5 / ksriniva 12/14/94 - merge changes from branch 1.564.720.22 / msimon 12/13/94 - merge changes from branch 1.564.720.23 / msimon 12/12/94 - merge changes from branch 1.479.710.82 / msimon 12/12/94 - Fixes for bug 249693 - Add event 10320 / ksriniva 12/12/94 - add ORA-17, ORA-7445, and 10077 / dsdaniel 12/12/94 - merge changes from branch 1.479.710.76&77&78&80 / thayes 12/08/94 - Fix name of parameter in msg 406 / boki 12/01/94 - adding new error numbers for schema offline instant / boki 12/01/94 - adding new error numbers and msgs for schema offlin / aho 12/01/94 - rci trace event 10610, 2095 / jstamos 11/30/94 - merge changes from branch 1.479.710.79 / jstamos 11/30/94 - add periods and capitalization: 23306 - 23320 / jbellemo 11/30/94 - merge changes from branch 1.564.720.19 / hasun 11/29/94 - Change cause/action statements for (2094,23364) / ksriniva 11/23/94 - change 10090 to 10095 / jbellemo 11/23/94 - remove 1966 / jbellemo 11/22/94 - fix up 12495, again / hasun 11/22/94 - Add messages for Replication factoring (23364,2094) / dsdaniel 11/18/94 - execution of deferred RPC disabled / dsdaniel 11/17/94 - merge changes from branch 1.479.710.74 / jstamos 11/16/94 - merge changes from branch 1.479.710.75 / jstamos 11/16/94 - add 23353 for repcat / dsdaniel 11/15/94 - 23352 - deferred rpc error message / thayes 11/14/94 - Change reference to compatible parameter / ksriniva 11/14/94 - add error codes for generic oradbx / jbellemo 11/14/94 - remove 1948 / dchatter 11/14/94 - merge changes from branch 1.564.720.9 / dchatter 11/14/94 - merge changes from branch 1.564.720.14 / rhari 11/13/94 - merge changes from branch 1.564.720.11 / jstamos 11/11/94 - merge changes from branch 1.479.710.72 / rtaranto 11/10/94 - merge changes from branch 1.564.720.15 / rtaranto 11/10/94 - merge changes from branch 1.479.710.73 / rtaranto 11/10/94 - Update Cause and Action comments for event 04097 / dchatter 11/09/94 - merge changes from branch 1.479.710.70 / rtaranto 11/02/94 - merge changes from branch 1.564.720.12 / jbellemo 11/02/94 - merge changes from branch 1.564.720.13 / jbellemo 11/02/94 - merge changes from branch 1.479.710.64 / rtaranto 10/31/94 - merge changes from branch 1.479.710.71 / dsdaniel 10/27/94 - new replication messages / rhari 10/25/94 - merge changes from branch 1.479.710.63 / arhee 10/20/94 - merge changes from branch 1.479.710.69 / rtaranto 10/19/94 - Add event 04097 / hjakobss 10/16/94 - event 10078 / dchatter 10/14/94 - messages of 3125, 3126, 3127 backported from 7.2 / dchatter 10/14/94 - change 3124 to an internal error and add 3128 / jstamos 10/13/94 - merge changes from branch 1.479.710.58 / dsdaniel 10/13/94 - add 1085 / adowning 10/13/94 - merge changes from branch 1.479.710.65 / lchidamb 10/12/94 - add 1084: invalid parameter to oci call. / hjakobss 10/10/94 - event 10077 / rjenkins 10/06/94 - obsoleting 2255 / msimon 10/05/94 - merge changes from branch 1.564.720.1 (bug 209788) / lchidamb 10/05/94 - changed error #3112 / hjakobss 10/05/94 - event 10076 / rjenkins 10/04/94 - merge changes from branch 1.564.720.2 / arhee 10/04/94 - add event 10377 / rjenkins 10/03/94 - merge changes from branch 1.479.710.60 / jstamos 09/30/94 - reserve error numbers already in use / for refresh groups, snapshots, and job queues / jbellemo 09/30/94 - fix up 12495 / rhari 09/29/94 - some more messgaes for UTL_RAW and UTL_PG / (now complete 08401 - 08499) / jbellemo 09/28/94 - add 12495 / hjakobss 09/28/94 - event 10076 / adowning 09/28/94 - add replication PL/SQL errors / rhari 09/27/94 - UTL_RAW & UTL_PG (8401 -- 8443) / msimon 09/27/94 - Sequence numbers rewrite (bug 239487) / msimon 09/26/94 - merge changes from branch 1.479.710.59 (bug 209788) / jbellemo 09/23/94 - add event 10090 / agupta 09/15/94 - 231813 - add message for creating segment / rjenkins 09/09/94 - removing 2255 / msimon 09/07/94 - Changes for bug 209788 / jstamos 09/02/94 - externalize 23306 - 23320 for replication / ksriniva 08/31/94 - add WMON termination error message / atsukerm 08/31/94 - merge changes from branch 1.479.710.57 / abrumm 08/22/94 - Change 1854 due to max Julian date increase by CORE / atsukerm 08/18/94 - new space management events / hjakobss 08/15/94 - event 10075 / cozbutun 08/15/94 - change a few comments / gpongrac 08/10/94 - merge changes from branch 1.479.710.55 / bhirano 08/10/94 - merge changes from branch 1.479.710.56 / dleary 08/05/94 - add 1781-1784 for UNRECOVERABLE / bhirano 08/05/94 - add (unix-specific) core file size events / gpongrac 08/01/94 - revise message for 292 and 293 / dsdaniel 07/28/94 - 1085 preceding error in deferred rpc / lthieme 07/27/94 - resolve inspection issues for resizeable datafiles / alingelb 07/25/94 - fix 1163 / dsdaniel 07/21/94 - merge changes from branch 1.479.710.53 / dsdaniel 07/21/94 - deferred rpc export error 23327 / svenkate 07/19/94 - changes to err msg 1163 / dsdaniel 07/11/94 - merge changes from branch 1.479.710.51 / dsdaniel 07/11/94 - error number conflict with 7.2 / dsdaniel 07/11/94 - dbms_sys_error upgrade / wbridge 07/08/94 - bug 150326: typo in error 66 / ksriniva 07/08/94 - add trace event for kst / gpongrac 07/08/94 - parallel recovery factoring / gpongrac 07/08/94 - merge changes from branch 1.479.710.50 / svenkate 07/07/94 - bug 210900 : changes to err msg 1163 / ksriniva 07/07/94 - merge changes from branch 1.479.710.49 / dchatter 07/07/94 - added error msg for Ref Cursor and Non-blocking OCI / ksriniva 07/06/94 - add events for latch recovery / hrizvi 07/06/94 - add 1657, 10510, 10511, 10512, fix 1545, 1625 / atsukerm 07/06/94 - DBMS_SPACE errors revisited / pgreenwa 07/05/94 - trace event: write timing stats on OPS reco scan / wbridge 06/29/94 - #198847: report 1031 rather than 251 / cbarclay 06/29/94 - add 6504 - Result Sets type mismatch / rjenkins 06/27/94 - 193637: reorg constraint creation / wbridge 06/24/94 - bug 182267 - fix some causes / pritto 06/22/94 - bug 221252 - add TABLESPACE to cause for 1771 / ajasuja 06/21/94 - dbms_pipe error messages / nmichael 06/20/94 - Hash expressions for clusters / wbridge 06/16/94 - specify file number for forced checksum error / jloaiza 06/16/94 - add disable dml locks / jloaiza 06/16/94 - add compatibility for disable table lock / aho 06/15/94 - SYS isn't allowed to create indexes with nfb (2001) / jloaiza 06/14/94 - add disable dml_locks / lthieme 06/03/94 - Resizeable Datafiles Feature / jklein 05/24/94 - fix spelling error for message 6556 / ksriniva 05/16/94 - merge changes from branch 1.479.710.47 / ksudarsh 05/06/94 - relocate error msg / wbridge 04/25/94 - checksum error events / ksudarsh 04/21/94 - parallel query option check / ksriniva 04/19/94 - enhance ORA-4031 and ORA-443 / wmaimone 04/08/94 - merge changes from branch 1.479.710.45 / rlim 04/07/94 - merge changes from branch 1.479.710.44 / dsdaniel 04/07/94 - merge changes from branch 1.479.710.34 / abhide 04/07/94 - merge changes from branch 1.479.710.36 / (merge SQL*NET error codes) / jtellez 04/06/94 - add io tracing event 10705 / ltung 04/05/94 - merge changes from branch 1.479.710.41 / wbridge 04/04/94 - allow end hot backup after crash / ajasuja 04/04/94 - merge changes from branch 1.479.710.32 / wmaimone 03/31/94 - cause/action for 1010 / thayes 03/22/94 - merge changes from branch 1.479.710.38 / rlim 03/21/94 - #206483 - reuse 1037 for maximum cursor memory / exceeded / ltung 03/21/94 - add 12800, 12826 for parallel query execution / dpawson 03/21/94 - merge changes from branch 1.479.710.42 / pgreenwa 03/14/94 - merge changes from branch 1.479.710.39 / ltung 03/10/94 - events 10378, 10379 / dpawson 03/10/94 - Merge in nCube error msgs / Merge in correct Unix messages instead of obsolete / Unix trusted messages / pgreenwa 03/08/94 - add trace event for ksq / hrizvi 03/08/94 - add smon events 10510, 10511 / dpawson 03/04/94 - merge changes from branch 1.479.710.29 / thayes 03/03/94 - Error for simulating block recovery / ltung 03/02/94 - merge changes from branch 1.479.710.37 / dpawson 03/02/94 - Reserve numbers for resizable data files / aho 03/02/94 - add max key length to oer(1450) (bg 198813) / ltung 03/01/94 - parallel clause syntax errors / hjakobss 02/28/94 - merge changes from branch 1.479.710.20 / jwijaya 02/23/94 - merge changes from branch 1.479.710.35 / dpawson 02/08/94 - Reserve a range for DRS6000 / jwijaya 02/03/94 - remove 2300-2350 old odb messages / dsdaniel 02/02/94 - kkxp.c code change / ksriniva 01/27/94 - sigh... really fix ORA-30 message for bquigley / ksriniva 01/27/94 - merge changes from branch 1.479.710.33 / ajasuja 01/26/94 - remove OER-4040 / ksriniva 01/25/94 - merge changes from branch 1.479.710.30 / dsdaniel 01/21/94 - merge changes from branch 1.479.710.31 / wbridge 01/20/94 - add ALTER DATABASE CLEAR LOGFILE command / jbellemo 01/20/94 - merge changes from branch 1.479.710.26 / dsdaniel 01/20/94 - reassign dbms_sys_error range / rjenkins 01/19/94 - merge changes from branch 1.479.710.19 / ksriniva 01/19/94 - fix Cause part of ORA-30 / dpawson 01/19/94 - reserve osd message range / dsdaniel 01/18/94 - merge changes from branch 1.479.710.9&21 / jbellemo 01/17/94 - add event 10063 / ksriniva 01/11/94 - merge changes from branches 1.479.710.{11,15} / ltung 01/10/94 - 10380 - 10382, 12818 - 12820 / jbellemo 01/07/94 - add event 10062 / cozbutun 01/06/94 - merge changes from branch 1.479.710.24 / cozbutun 01/05/94 - modify 4091 to say trigger or function / hrizvi 01/03/94 - bug 189557 - fix explanation of 1599 / dleary 01/03/94 - make event 10383 level a bitfield / gpongrac 12/30/93 - change comments for 12812 and 12813 / dsdaniel 12/27/93 - obsolete ICD error / sjain 12/21/93 - merge changes from branch 1.479.710.17 / jbellemo 12/21/93 - merge changes from branch 1.479.710.18 / jbellemo 12/21/93 - merge changes from branch 1.479.710.14 / hjakobss 12/21/93 - trace event 10060 / dpawson 12/21/93 - merge changes from branch 1.479.710.7 / rjenkins 12/20/93 - creating job queue / jbellemo 12/17/93 - #191402: remove 1930 / sjain 12/16/93 - add new error message for ora-6400 / dleary 12/16/93 - add event 10383 / ksriniva 12/10/93 - add trace event for latch operations / jbellemo 12/08/93 - #190089: add new message 1742 for unterminated comm / jwijaya 12/07/93 - add error ranges for OI/KO/KG / wbridge 11/23/93 - log block checksum / pritto 11/10/93 - merge changes from branch 1.479.710.12 / hkodaval 11/05/93 - merge changes from branch 1.479.710.4 / pritto 11/04/93 - merge in SQL*Net 2.1.2 error messages / pritto 11/02/93 - add 122 / ltung 11/02/93 - fix parallel query messages / ksriniva 11/02/93 - merge changes from branch 1.417.312.18 / dsdaniel 10/30/93 - dbms_sys_error error range / rjenkins 10/28/93 - adding an error message / ksriniva 10/22/93 - fix action part for ora-4031 / dleary 10/20/93 - event 10384 / dleary 10/18/93 - event 10385 / hkodaval 10/14/93 - bug 174446: add new error about read-only tablespac / aho 10/13/93 - merge changes from branch 1.479.710.3 / aho 10/13/93 - add 10606 - debug trace kkri (93.10.13) / aho 10/13/93 - add 10605 - debug trace kkri / aho 10/05/93 - forgot comment character / aho 10/05/93 - add event to test parallel create index (10605) / change 1404 (bug 181123) / ksudarsh 10/01/93 - restore deleted messages / jklein 09/29/93 - reserve ksepec events for scafs / mmoore 09/22/93 - add error range for pga/appc gateway / pritto 08/23/93 - re-insert Trusted Oracle messages / ksudarsh 08/10/93 - parallel query option / cozbutun 08/09/93 - add 6575 / aho 08/05/93 - add create index fastpath event / pritto 07/29/93 - merge in sql*net 2.1 error messages / wbridge 07/27/93 - disallow rolling upgrade between point releases / agupta 07/22/93 - add errors for cluster extent overflow / jcohen 07/20/93 - reserve events 10370-10386 for parallel SQL / pritto 07/16/93 - #(170429) add 121, mts_servers w/o mts_dispatchers / hrizvi 07/08/93 - fix wording 1593 / mmoore 07/07/93 - #(141926) trigger description too long / glumpkin 07/07/93 - change 2256 / dpawson 07/06/93 - reserve errors for icl unix / tsaulys 07/02/93 - #(155239) add 7641 for smscre() / tsaulys 07/02/93 - #(149634) add 7880 for sdopnf() / dpawson 07/01/93 - merge changes from branch 1.417.312.17 / agupta 06/29/93 - add event to prevent forward coalesce / sjain 06/21/93 - add new messages for streaming / jwijaya 06/14/93 - add error / dpawson 06/11/93 - Changed message 445 to take seconds as an argument / ajasuja 06/10/93 - connect internal messages / achaudhr 06/10/93 - errors for updatable joins / cozbutun 05/28/93 - add errors for pls_in_sql purity stuff / hjakobss 05/27/93 - name changes in 6562, add 6566, 6567 / hjakobss 05/27/93 - fix line feed error in 6562 / ajasuja 05/26/93 - merge changes from branch 1.417.312.16 / aho 05/18/93 - add event 10604 - trace parallel index creation / ajasuja 05/14/93 - expand message 12434 / glumpkin 05/10/93 - Merge change for ora-2243 / thayes 05/06/93 - Fix 2249 error message and cause/action / gpongrac 05/06/93 - add block rcovery debugging event / rlim 04/27/93 - change FIPS Flagging error message 97 / glumpkin 04/20/93 - Update description for 12008 / jbellemo 04/16/93 - add 1989 for invalid os roles / tsaulys 04/12/93 - merge, change 7544 for #140423 to 7721 / pritto 04/12/93 - merge changes from branch 1.417.312.12 / tsaulys 04/09/93 - #(157272) change 7538,7539,7540 / tsaulys 04/09/93 - #(157272) add 7544,7556,7557,7558,7559,7861,7862 / rlim 04/08/93 - add flagger msg 97 / ltung 04/07/93 - add 10387-89, 12815 (cache partitions > 1) / hkodaval 04/07/93 - Bug 26632: give obj and tablespace names for error / add 1650, 1651, 1652, 1653, 1654 and remove 1547 / rlim 04/06/93 - add msg 960 & 962 / ghallmar 04/06/93 - change text for 2064 / mmoore 04/01/93 - #(156181) fix processing of large 'when' clauses / gpongrac 04/01/93 - add new log open error (365) / hkodaval 03/29/93 - Bug 123364: remove recursion and hence error 1596 / wbridge 03/24/93 - read-only tablespaces / dsdaniel 03/24/93 - commitscn function for repliation / pritto 03/17/93 - #(153641) remove 110 & add 960, 962 for rlim / ltung 03/15/93 - merge from dve$fox (parallel query msgs) / dpawson 03/15/93 - #(140423) Add msg 7544 - not enough OSD resource / bquigley 03/15/93 - ora-01022,01058 / tsaulys 03/09/93 - #(145081) add 7541, 7543 / hkodaval 02/26/93 - Bug 140750 - add event 10061 to disable SMON from / cleaning temp segments and coalescing extents / jwijaya 02/22/93 - merge changes from branch 1.417.312.7 / jwijaya 02/22/93 - merge changes from branch 1.417.312.6 / jwijaya 02/17/93 - renumber 4069 and fix 4068 / jwijaya 02/17/93 - renumber 4069 / pritto 02/08/93 - #(149456) add 119, mts_listener_address syntax error / dleary 02/08/93 - merge changes from branch 1.286.12.1 / jbellemo 02/02/93 - merge changes from branch 1.417.312.5 / jbellemo 01/22/93 - (#147335): add message 12444 / achaudhr 01/21/93 - add event 10058 / rkooi 01/20/93 - add 4069 / jwijaya 01/18/93 - merge changes from branch 1.417.312.3 / pritto 01/16/93 - merge changes from branch 1.417.312.1 / jwijaya 01/14/93 - bug 145876, add 4046 / jklein 01/13/93 - merge changes from branch 1.417.312.2 / jklein 01/13/93 - bug 146226 - add event to disable histograms / pritto 01/11/93 - #(144049) remove 481, 482 / mmoore 01/11/93 - change message for 8176 / wbridge 01/07/93 - event to suppress file name for regression tests / glumpkin 12/16/92 - #(141079) add sqlnet error messages / glumpkin 12/16/92 - #141079 - add sqlnet error messages / mmoore 12/11/92 - disable set_role in stored procs / agupta 12/11/92 - add 10292 - debug drop tablespace / wbridge 12/08/92 - snapshot refresh all error / wbridge 12/03/92 - fix error handling for refresh all / ltan 12/03/92 - modify 1545 cause and action / wbridge 11/30/92 - background process to refresh snapshots / pritto 11/30/92 - merge in SQL*Net 2.0.12 errors / epeeler 11/30/92 - modify enable constraint message / sjain 11/25/92 - Add 1044 / rkooi 11/25/92 - fix 6563 error message / jloaiza 11/25/92 - fix error 57 / ajasuja 11/25/92 - new error 12354 / rkooi 11/24/92 - A couple of changes for Brian / jcleland 11/24/92 - fix error 12354 / jcleland 11/24/92 - -madd error 12354 / ghallmar 11/20/92 - add event 10281 to affect process creation timeout / bquigley 11/20/92 - Put back %s at beginning of ora-4063,20000 / jloaiza 11/19/92 - second parameter to 4031 / bquigley 11/19/92 - msgs starting with %s changed / ajasuja 11/19/92 - error 12445 for analyze table / maporter 11/18/92 - #139480 - remove 10700 event / bquigley 11/18/92 - Trusted messages / bquigley 11/17/92 - ora-603 / jwijaya 11/14/92 - comment on event 10205 / rkooi 11/13/92 - add 655x for psdres / bquigley 11/13/92 - update ORA-2436 / ghallmar 11/12/92 - add events for 2PC tracing / ajasuja 11/11/92 - merge forward from 7.0.11 / thayes 11/10/92 - Add parameter range checking errors / jcleland 11/10/92 - revise error messages 12351,12353 / jcleland 11/10/92 - add error message 12353 / bquigley 11/10/92 - update 2021 / cozbutun 11/09/92 - modify 2019 / ajasuja 11/09/92 - add MLS error 12447 / rkooi 11/06/92 - add 6513 for pl/sql / bquigley 11/05/92 - fix up merge diffs / jwijaya 11/04/92 - add 6561, 6562 / gpongrac 11/03/92 - add event 10291 for testing tbsadf / wbridge 11/02/92 - #(135186) robust lock mode inquiry / jbellemo 11/02/92 - add 12461 / bquigley 11/02/92 - add 2028 / rlim 10/30/92 - add 1040 / glumpkin 10/30/92 - Merge unix error messages / pritto 10/29/92 - add event 10258 for shared server selection / maporter 10/29/92 - Add 7531 vms error message for ssfccf $display / bquigley 10/28/92 - make 2038,2039 clearer / bquigley 10/27/92 - Add 1414 / pritto 10/26/92 - #(135834) add 116 / bquigley 10/25/92 - add 1413 / bquigley 10/25/92 - 1484, 1486 clearer / aho 10/23/92 - add event to test truncate index undo (10603) / rkooi 10/22/92 - reduce length (for LMS) of error 21000 / tsaulys 10/21/92 - Add error message 7709 for bug 33056 / rlim 10/21/92 - add 1039 / ccongdon 10/21/92 - Add errors 7515, 7519, 7537, 7542, 7527, and 7533 / for bug 117453. / pritto 10/20/92 - #(130911) move 7575,7576 to 1987,1988 / #(135660) add 7606 / jwijaya 10/19/92 - add 1083 / bquigley 10/17/92 - ora-1409 / wbridge 10/16/92 - require log_files to match in all instances / lwillis 10/14/92 - Add 1986 - optimizer_goal / mmoore 10/13/92 - #(131686) change messages 2074,4092,0034 / maporter 10/13/92 - Fill in archival errors that were never entered / maporter 10/12/92 - #132670 - report archiving osd errors (add 290) / jklein 10/12/92 - new analyze parse options / ghallmar 10/10/92 - add ora-476: RECO died / thayes 10/08/92 - Add error #1639 / glumpkin 10/08/92 - fix typo in 02436 / wmaimone 10/01/92 - duplicate 12449 / mmoore 10/01/92 - remove trigger restrictions, remove error 4086 / jwijaya 09/28/92 - 4055 is obsolete / verbrug 09/23/92 - Remove 12704 / thayes 09/23/92 - Fix error messages for log members / rlim 09/21/92 - add 1413 and 1463 / rkooi 09/19/92 - change error 6559 to standards / pritto 09/18/92 - update message 110 / wmaimone 09/16/92 - add 12400,12401,12448,12449 / achaudhr 09/14/92 - 126559: rewording 1719 / rkooi 09/08/92 - backout 1.334 changes - postpone until 7.0.12 / pritto 09/08/92 - #(127459) update message 114 / glumpkin 09/07/92 - Add new snapshot error message: 12010 / ghallmar 09/05/92 - reuse 2043: must end current transaction before ... / bquigley 09/04/92 - Alter any msg beginning %s so the %s appears later / bquigley 09/04/92 - Alter any msg beginning %s so the %s appears later / mmoore 08/31/92 - #(122494) add column name to error 4086 / rkooi 08/26/92 - add 6503 for pl/sql / pritto 08/26/92 - clarify and extend cause/action on OER(23) / jklein 08/20/92 - parallel data load / jbellemo 08/17/92 - fix label translation errors: 12450-12460,7610-7620 / jwijaya 08/13/92 - add 4069 / gpongrac 08/10/92 - change Cause: for error 1610 / dleary 08/06/92 - reserve events for parallel query / jwijaya 08/05/92 - add a new error / pritto 07/30/92 - add dispatcher error messages / bquigley 07/29/92 - Add Message Standards Documentation. / hrizvi 07/28/92 - fix extreneous / before 2078 / wmaimone 07/24/92 - MLS tech writing review / bquigley 07/24/92 - Update ORA-00568 & 00057 / hrizvi 07/21/92 - add 2093 / thayes 07/20/92 - Add pec error number for MLS / jwijaya 07/20/92 - remove database link owner from name / jklein 07/16/92 - remove message 983 - obsolete / hrizvi 07/16/92 - add 19, 35, 1985 / wbridge 07/15/92 - add compatibility checking calls / hrizvi 07/15/92 - add 1636, 1637 / gpongrac 07/15/92 - use error 373 for online log incompat problem / ltan 07/14/92 - add error 8176 / pritto 07/10/92 - #(105280),#(105279) add more sz errors / thayes 07/01/92 - Change message for invalid thread number / rlim 06/30/92 - changing text of error 2444 / sjain 06/26/92 - Add message for # 568 / rkooi 06/25/92 - get rid of arg to 6557 / vraghuna 06/23/92 - add 7850 for fixed= option / pritto 06/17/92 - add XA error messages / hrizvi 06/16/92 - add 8103 / ghallmar 06/14/92 - change wording of error 2047 / wbridge 06/10/92 - improve error simulation / mmoore 06/10/92 - add error message for create or replace trigger / glumpkin 06/09/92 - Add event 10053 -- optimizer stats / mmoore 06/08/92 - #(111777) add error for lacking create session priv / epeeler 06/08/92 - modify error message 1451 / jbellemo 06/05/92 - rollout 12458: obsolete / hrizvi 06/05/92 - add 2091, 2092 / thayes 06/04/92 - Add errors for KCK module / hrizvi 06/04/92 - add 1635 / agupta 06/03/92 - remove 1635,1636 / jbellemo 06/02/92 - new MLS errors: 12457,12459 / sjain 06/01/92 - Add/changge error messages / thayes 05/29/92 - Add error for 0 file size / maporter 05/29/92 - Add 475, 1380-1389 / jklein 05/29/92 - add kdn event / jcleland 05/29/92 - add message for 12336 / rkooi 05/27/92 - remove extra '/' lines to ease finding error ranges / reserve 3300-3499 for Meiko. / delete history prior to 01/01/92. / wbridge 05/21/92 - reword 285 / agupta 05/21/92 - 60972 - dtsdrv - don't drop if users temp or defaul / pritto 05/19/92 - #(109437) add error msg for long mts_service / jloaiza 05/12/92 - add discrete transaction error / ajasuja 05/12/92 - new message 12407 / smartin 05/05/92 - Fix kcl 160? error messages / jklein 04/29/92 - fix bug 106913 - make message 4014 TRANSLATABLE / mmoore 04/28/92 - #(9647) fix granting on a view to check dependents / rkooi 04/26/92 - add errors for dbms_pipe icds / rkooi 04/26/92 - add arg for 6557 / wmaimone 04/24/92 - merge changes from branch 1.270.300.4 / cheigham 04/23/92 - add loader out-of-memory message / hrizvi 04/22/92 - fix wording of 1593, bug no. 99222, add 1556 / mmoore 04/16/92 - add message for disallowing features in mts / mmoore 04/13/92 - add error 4093 / wmaimone 04/06/92 - add 12458 / pritto 03/26/92 - merge in SQL*Net version 2.0.9.3 messages / jwijaya 03/25/92 - fix 6500 / agupta 03/25/92 - alter table allocate extent (freelist group) errs / jwijaya 03/18/92 - clean up pl/sql error messages / wbridge 03/13/92 - fix create controlfile / maporter 03/11/92 - Reserve NCUBE error range / jklein 03/05/92 - cann't allocate extent on hash clusters / rkooi 02/21/92 - change 00257 per mktg / mmoore 02/19/92 - remove error 4093 / ajasuja 02/18/92 - add errors 12487, 12429, 12441, 12442 / wbridge 02/17/92 - add error 1221 / ltan 02/17/92 - change ora-1597 for system rollback segment / jwijaya 02/13/92 - doesn't -> does not / jloaiza 02/13/92 - add oltp transaction failed error / mroberts 02/12/92 - remove quotes from 4043, 4052, 4053, 406x / wmaimone 02/07/92 - add MAC dictionary reference errors / jwijaya 02/07/92 - add an error / pritto 02/06/92 - merge in SQL*Net v2.0.8 errors, add 113 / mmoore 02/06/92 - change standard_extension / bmahbod 02/04/92 - add 1634 for bug 87775 / rkooi 01/31/92 - better 'cause' section for error 1002 / smcadams 01/29/92 - add 1219, 1220, 34 / rkooi 01/29/92 - improve error 1011 / ltan 01/29/92 - modify cause and action of ora-1594 / rlim 01/24/92 - 6.2->7.0 merge / rlim 01/22/92 - add 2022 - local view too complex for remote / epeeler 01/22/92 - add 2445 - exceptions table missing / mroberts 01/21/92 - add 3124 (async operation interrupted) / jwijaya 01/16/92 - add 4029 / jklein 01/16/92 - fix error 2170 / wbridge 01/13/92 - add event 10300 to avoid undo compatibility check / maporter 01/12/92 - merge changes from branch 1.191.51.3 / wbridge 01/10/92 - reword 1040 / rlim 01/10/92 - reword 1 and include violated index name / wmaimone 01/08/92 - add 12438, change syshi/low to dbhi/lo / wbridge 01/08/92 - reword 1171 / thayes 01/07/92 - add error for renaming current log file / jcleland 01/03/92 - add errors for label translation / ghallmar 01/02/92 - add 2079: no new branches after tx commit / maporter 12/23/91 - add message for osnsoi failure. / maporter 12/21/91 - Add err 50 for bug 48037, 79392 / Hayes 07/29/91 - add error 10288 / Heigham 07/19/91 - add errors 2372-3 / Tan 07/18/91 - change message of event 10041 / Tan 04/17/91 - change message of error 1456 / Jain 04/12/91 - Change the text of 1488 / / Copyright (c) Oracle Corporation 1999, 2001. All rights reserved. / / NAME / e0.msg / DESCRIPTION / Error messages for Oracle / NOTES / Language : American / Character set : US7ASCII / / List of ORACLE errors / / This file is converted to header/message files using lmsgen.c. / / The first col is the ORACLE error number. / The second column is reserved and must (for now) be x00000. / The remainder of the line is the error text (max 76 characters). / / Adding an error: / Check out this file, add the error, and check it back in. / Error numbers should always be ordered. / The second column should always be x00000. / Pseudo-error debugging events: / Error codes 10000 .. 10999 are reserved for debug event codes / that are not really errors. / / MODIFIED / vzsridha 02/06/11 - add ora-499: raised when XDMG fails to initialize / repeatedly / sanselva 01/26/11 - proj33056: ORA-851 for RMON termination / vgokhale 01/12/11 - Add OER-387 / mmpandey 05/20/10 - 9714832: modify ADRCI Note, per new requirement / mmpandey 05/13/10 - 9713537: modify ORA-00600 Cause/Action message / vpantele 02/26/10 - ORA-244 and 245 / vzsridha 04/25/09 - add exit error for XDMG process / jjlee 03/03/09 - add ORA-241 / clhsu 02/23/09 - add a new process 496 / adalee 01/08/09 - add ORA-495 / kgiyer 11/15/08 - Bug-7503836: Shorten text for ORA-336 / kgiyer 05/20/08 - Bug-6746478: add OER 242 and 243 / vpantele 09/05/08 - fix ORA-752 / rlong 08/07/08 - / jgiloni 08/04/08 - Add 135-139 / jjlee 07/15/08 - comment change / jiashi 06/05/08 - update ORA-235 / mcoulter 03/27/08 - / clhsu 03/07/08 - bug6513336: change ora-494 to conform language rules / shsong 02/13/08 - enhance OER 336 message / pbagal 12/06/07 - add inst. type to 99 / mcoulter 11/21/07 - BUG 6603046 - need to handle more error paremeters / (9) / slahoran 10/22/07 - bug/6327593 : add ORA-44 / yuli 09/04/07 - RECOVER UNTIL CONSISTENT / kesriniv 08/03/07 - add ORA-66 for ksp-invalid-sid msg / bbaddepu 08/01/07 - add 848-850 / vpantele 04/25/07 - add OER 239, 240 and 494 / kesriniv 05/08/07 - add ORA-00098 and ORA-00099 / bbaddepu 04/26/07 - enhance 840 and 839 messages / banaras 02/07/07 - lock_sga and memory_target are not compatible / bbaddepu 01/19/07 - enhance 845 msg / siroych 12/27/06 - add 846 / kumamage 08/01/06 - add soft internal error / rvingral 07/24/06 - add OER(493) / tyurek 06/13/06 - define 00491 for RMS0 / yohu 06/01/06 - add OER(492) / bbaddepu 05/23/06 - add 843, 845 / siroych 05/19/06 - add OER 844 / bbaddepu 04/30/06 - add 839, 840/1/2 / siroych 04/11/06 - add OER 837, 838 / vpantele 02/15/06 - Add error 752 for lost write detection / jiashi 03/27/06 - remove OER(343), modify OER(346) / avaliani 03/29/06 - incorporate erros_us feedback / ramekuma 02/23/06 - ddl_waitlock: update definition of ORA 54 / ltominna 01/25/06 - remote op fail error OER(43) / avaliani 11/21/05 - reserve OER(39) / bbaddepu 07/13/05 - add diag events notes / seeda 06/30/05 - 4226133: ORA-64 doesn't report caller description / mjstewar 06/24/05 - add OER(751) / yuli 06/23/05 - add 725 / jiashi 02/25/05 - modify OER(63), obsolete OER(66) / hmankude 02/03/05 - Bug 4160349: new msg for ckpt death / jiashi 12/16/04 - modify messages for 216, 217, 219 / kumamage 12/14/04 - add message for 453 / avaliani 11/30/04 - add OER(569) / pokumar 09/08/04 - add event 833 / pokumar 07/15/04 - add message 832 / wojeil 07/27/04 - bug-3449667:add error message for enabling / USE_INDIRECT_DATA_BUFFERS on non-VLM platforms / pokumar 06/23/04 - add event 831 for stress testing / sridsubr 04/18/04 - Add service name error msg 42 / tbosman 02/11/04 - numa / tbosman 10/02/03 - / tbosman 09/20/03 - attach failed / tbosman 08/20/03 - add PSP error / eyho 05/24/04 - remove OER 99 / jiashi 05/16/04 - update OER 302 / rlong 11/06/03 - OSM->ASM / tsepez 11/04/03 - RBAL/ORB* termination messages / pokumar 10/28/03 - add 830 / pokumar 10/08/03 - add event 829 for stress testing / rasivara 09/25/03 - correct typo in ORA-288 message / cluu 08/29/03 - add err msg 105,109,110,111,112,117,118,133,134 / kpatel 08/18/03 - add error 828 / pokumar 07/29/03 - add error message 827 / asundqui 07/14/03 - add Resource Manager abort_sql/kill_session messages / pokumar 05/30/03 - change text of 824 / pokumar 05/01/03 - add sga-tuning error messages / pokumar 04/18/03 - enhance ora-371 to include size recommendation / tlahiri 03/18/03 - Add sga_target too large message / vsrihari 02/27/03 - reuse 397 for instance recovery abort / tlahiri 01/23/03 - Add error for MMAN process start failure / pritto 12/05/02 - Fix typo in 486 / lilin 01/06/03 - change messages with thread no. to include instance / pritto 12/05/02 - Fix typo in 486 / kumamage 12/14/02 - add error 450 / bbaddepu 11/19/02 - modify err msg 218. / tlahiri 12/10/02 - Add error messages for SGA tuning / jiashi 09/24/02 - add error message 740, 741 / banand 03/15/02 - recovery thru resetlogs : change 342 / cluu 10/07/02 - remove unused messages: 117,124,118 / cluu 10/06/02 - remove unused messages: 105,111,112,120,121 / swerthei 04/26/02 - block change tracking; add 487 for CTWR / yuli 10/03/02 - add 750 / yuli 09/20/02 - obsolete alter database convert / kumamage 09/04/02 - add internal error message / pritto 07/01/02 - Only one umbilicus per db instance / jarnett 05/10/02 - bug 2314669 - make DX overflow a user error. / jwlee 05/08/02 - add error 479. / pritto 10/22/01 - Rename PSM to OSM. / pritto 10/15/01 - Add OSM Background message / wojeil 02/11/02 - adding 385. / yuli 01/16/02 - tablespace rename project / yuli 02/08/02 - 10i irreversible compatibility project / msusaira 12/07/01 - add error messages for H.A.R.D project / vkarra 11/20/01 - add error message for auto segment space management / smuthuli 10/18/01 - add 478 / pritto 10/02/01 - Update detached process number range. / sdizdar 02/23/01 - added 0217 / mwjohnso 07/26/01 - modify ora-298 text / mjaeger 07/05/01 - bug 479696: 00295: alter db datafile/tempfile / bsinha 07/20/01 - fix distributed autonomous txn / ilam 06/18/01 - Add 485 error for DIAG / bsinha 06/13/01 - autonomous-distributed interop / cluu 04/27/01 - add listener error messages / eyho 03/06/01 - RAC name changes / qcao 02/14/01 - fix bug 407350 / anithrak 03/05/01 - Enhance ORA-379 message to add block size / vjoshi 12/13/00 - change error message / robermar 11/22/00 - Detect Multiple strand redo / heneman 10/21/00 - Rename MTS. / jarnett 08/17/00 - bug 1217450 - disallow autonomous in distributed / vsrihari 07/19/00 - add 299 for block media recovery / smukkama 07/20/00 - change 374 - db_block_size must be multiple of 512 / vsrihari 06/12/00 - add 399 for change vector corruption / vsrihari 06/06/00 - fix ORA-396 message argument / vsrihari 05/24/00 - add 398 for instance recovery abort / tlahiri 05/08/00 - Add dynamic cache error messages / smukkama 03/04/00 - Add 380,381,382 - multiple block size project / apadmana 01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW / eyho 02/14/00 - add 484 error for LMS / vsrihari 02/02/00 - add msg 397 for two-pass recovery / jarnett 07/02/99 - bug 853211 - allow local transaction disable on V8 / pogilvie 06/15/99 - testing error 607 / gcandea 02/11/99 - Add 127 and 128 for ALTER SYSTEM SHUTDOWN / robermar 10/22/98 - Error message 396 for two-pass recovery / drehfiel 09/10/98 - updating to follow message standards / skray 08/28/98 - edit message text for 38 / skray 08/14/98 - add 37, 38 / drehfiel 08/13/98 - editing action for message ORA-00001 / agreenbl 05/28/98 - Fix text for 00093, 00094 / mcoyle 04/03/98 - Add ops-aware oradebug mesgs / mcoyle 03/02/98 - Add errors for ops-aware oradebug / emagrath 02/26/98 - Add new archive log/state parameter support / mwjohnso 02/17/98 - Add 298 & 299 / heneman 12/03/97 - Add 2 MTS refuse error codes / bchang 09/26/97 - 000439: first character should be lower case / tlahiri 09/23/97 - add 379 / swerthei 08/13/97 - add 296, 297 /------------------------------------------------------------------------------- 00000, 00000, "normal, successful completion" // *Cause: Normal exit. // *Action: None. 00001, 00000, "unique constraint (%s.%s) violated" // *Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. // For Trusted Oracle configured in DBMS MAC mode, you may see // this message if a duplicate entry exists at a different level. // *Action: Either remove the unique restriction or do not insert the key. /0002 reserved for v2 compatibility (null column) /0003 reserved for v2 compatibility (column value truncated) /0004 reserved for v2 compatibility (end-of-fetch) /0009 reserved for v2 compatibility / / 10 - 49 user session and session switching errors / 00017, 00000, "session requested to set trace event" // *Cause: The current session was requested to set a trace event by another // session. // *Action: This is used internally; no action is required. 00018, 00000, "maximum number of sessions exceeded" // *Cause: All session state objects are in use. // *Action: Increase the value of the SESSIONS initialization parameter. 00019, 00000, "maximum number of session licenses exceeded" // *Cause: All licenses are in use. // *Action: Increase the value of the LICENSE MAX SESSIONS initialization // parameter. 00020, 00000, "maximum number of processes (%s) exceeded" // *Cause: All process state objects are in use. // *Action: Increase the value of the PROCESSES initialization parameter. 00021, 00000, "session attached to some other process; cannot switch session" // *Cause: The user session is currently used by others. // *Action: Do not switch to a session attached to some other process. 00022, 00000, "invalid session ID; access denied" // *Cause: Either the session specified does not exist or the caller // does not have the privilege to access it. // *Action: Specify a valid session ID that you have privilege to access, // that is either you own it or you have the CHANGE_USER privilege. 00023, 00000, "session references process private memory; cannot detach session" // *Cause: An attempt was made to detach the current session when it contains // references to process private memory. // *Action: A session may contain references to process memory (PGA) if it has // an open network connection, a very large context area, or operating // system privileges. To allow the detach, it may be necessary to // close the session's database links and/or cursors. Detaching a // session with operating system privileges is always disallowed. 00024, 00000, "logins from more than one process not allowed in single-process mode" // *Cause: Trying to login more than once from different processes for // ORACLE started in single-process mode. // *Action: Logoff from the other process. 00025, 00000, "failed to allocate %s" // *Cause: Out of memory. // *Action: Restart with larger sga heap. 00026, 00000, "missing or invalid session ID" // *Cause: Missing or invalid session ID string for ALTER SYSTEM KILL SESSION. // *Action: Retry with a valid session ID. 00027, 00000, "cannot kill current session" // *Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current // session. // *Action: None. 00028, 00000, "your session has been killed" // *Cause: A privileged user has killed your session and you are no longer // logged on to the database. // *Action: Login again if you wish to continue working. 00029, 00000, "session is not a user session" // *Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command // was not a user session (for example, recursive, etc.). // *Action: Retry with a user session ID. 00030, 00000, "User session ID does not exist." // *Cause: The user session ID no longer exists, probably because the // session was logged out. // *Action: Use a valid session ID. 00031, 00000, "session marked for kill" // *Cause: The session specified in an ALTER SYSTEM KILL SESSION command // cannot be killed immediately (because it is rolling back or blocked // on a network operation), but it has been marked for kill. This // means it will be killed as soon as possible after its current // uninterruptable operation is done. // *Action: No action is required for the session to be killed, but further // executions of the ALTER SYSTEM KILL SESSION command on this session // may cause the session to be killed sooner. 00032, 00000, "invalid session migration password" // *Cause: The session migration password specified in a session creation // call was invalid (probably too long). // *Action: Retry with a valid password (less than 30 chars). 00033, 00000, "current session has empty migration password" // *Cause: An attempt was made to detach or clone the current session and // it has an empty migration password. This is not allowed. // *Action: Create the session with a non-empty migration password. 00034, 00000, "cannot %s in current PL/SQL session" // *Cause: An attempt was made to issue a commit or rollback from a PL/SQL // object (procedure, function, package) in a session that has this // disabled (by 'alter session disable commit in procedure') // *Action: Enable commits from PL/SQL in this session, or do not attempt // to use commit or rollback in PL/SQL when they are disabled // in the current session. 00035, 00000, "LICENSE_MAX_USERS cannot be less than current number of users" // *Cause: // *Action: 00036, 00000, "maximum number of recursive SQL levels (%s) exceeded" // *Cause: An attempt was made to go more than the specified number // of recursive SQL levels. // *Action: Remove the recursive SQL, possibly a recursive trigger. 00037, 00000, "cannot switch to a session belonging to a different server group" // *Cause: An attempt was made to switch to a session in a different server // group. This is not allowed. // *Action: Make sure the server switches to a session that belongs to its // server group. 00038, 00000, "Cannot create session: server group belongs to another user" // *Cause: An attempt was made to create a non-migratable session in a server // group that is owned by a different user. // *Action: A server group is owned by the first user who logs into a server // in the server group in non-migratable mode. All subsequent // non-migratable mode logins must be made by the user who owns // the server group. To have a different user login in non-migratable // mode, the ownership of the server group will have to be changed. // This can be done by logging off all current sessions and detaching // from all existing servers in the server group and then having the // new user login to become the new owner. 00039, 00000, "error during periodic action" // *Cause: An unexpected error occurred while executing a periodically invoked // action. // *Action: Check the error stack for detailed error information. 00040, 00000, "active time limit exceeded - call aborted" // *Cause: The Resource Manager SWITCH_TIME limit was exceeded. // *Action: Reduce the complexity of the update or query, or contact your // database administrator for more information. 00041, 00000, "active time limit exceeded - session terminated" // *Cause: The Resource Manager SWITCH_TIME limit was exceeded. // *Action: Reduce the complexity of the update or query, or contact your // database administrator for more information. 00042, 0000, "Unknown Service name %s" // *Cause: An attempt was made to use an invalid application service. // *Action: Use a valid service name from SERVICE$ or add a new // service using the DBMS_SERVICE package. 00043, 00000, "remote operation failed" // *Cause: Execution of the inter-instance operation failed. // *Action: Check the status of the target instance. The operation may // have partially executed. Verify the result of the intended // operation. 00044, 00000, "timed_statistics must be TRUE when statistics_level is not BASIC" // *Cause: The user attempted to set timed_statistics to FALSE when // statistics_level was not BASIC. timed_statistics is required to be // TRUE to collect meaningful statistics when statistics_level is // set to TYPICAL or ALL. // *Action: Either set timed_statistics to TRUE or set statistics_level to // BASIC. 00050, 00000, "operating system error occurred while obtaining an enqueue" // *Cause: Could not obtain the operating system resources necessary // to cover an oracle enqueue. This is normally the result // of an operating system user quota that is too low. // *Action: Look up the operating system error in your system documentation // and perform the needed action. 00051, 00000, "timeout occurred while waiting for a resource" // *Cause: Usually due to a dead instance. // *Action: Check for any dead, unrecovered instances and recover them. 00052, 00000, "maximum number of enqueue resources (%s) exceeded" // *Cause: Ran out of enqueue resources. // *Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter. 00053, 00000, "maximum number of enqueues exceeded" // *Cause: Ran out of enqueue state objects. // *Action: Increase the value of the ENQUEUES initialization parameter. 00054, 00000, "resource busy and acquire with NOWAIT specified or timeout expired" // *Cause: Interested resource is busy. // *Action: Retry if necessary or increase timeout. 00055, 00000, "maximum number of DML locks exceeded" // *Cause: Ran out of DML lock state objects. // *Action: Increase the value of the DML_LOCKS initialization parameter // and warm start. 00056, 00000, "DDL lock on object '%s.%s' is already held in an incompatible mode" // *Cause: An attempt was made to acquire a DDL lock that is already locked. // *Action: This happens if you attempt to drop a table that has parse locks // on it. 00057, 00000, "maximum number of temporary table locks exceeded" // *Cause: The number of temporary tables equals or exceeds the number of // temporary table locks. Temporary tables are often created by // large sorts. // *Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization // parameter and warm start. 00058, 00000, "DB_BLOCK_SIZE must be %s to mount this database (not %s)" // *Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database // being mounted. It does not match the value used to create the // database. // *Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database // that matches the value. 00059, 00000, "maximum number of DB_FILES exceeded" // *Cause: The value of the DB_FILES initialization parameter was exceeded. // *Action: Increase the value of the DB_FILES parameter and warm start. 00060, 00000, "deadlock detected while waiting for resource" // *Cause: Transactions deadlocked one another while waiting for resources. // *Action: Look at the trace file to see the transactions and resources // involved. Retry if necessary. 00061, 00000, "another instance has a different DML_LOCKS setting" // *Cause: The shared instance being started is using DML locks, and the // running instances are not, or vice-versa. // *Action: Ensure that all instances' INIT.ORA files specify // the DML_LOCKS parameter as 0 or all as non-zero. 00062, 00000, "DML full-table lock cannot be acquired; DML_LOCKS is 0" // *Cause: The instance was started with DML_LOCKS = 0, and the statement // being executed needs a full-table lock (S, X, or SSX). // *Action: Restart the instance with DML_LOCKS not equal to zero, and // reexecute the statement. 00063, 00000, "maximum number of log files exceeded %s" // *Cause: The number of log files specificied exceeded the maximum number // of log files supported in this release. // *Action: Re-create the control file with the highest number of log files // no greater than the maximum supported in this release. 00064, 00000, "object is too large to allocate on this O/S (%s,%s,%s)" // *Cause: An initialization parameter was set to a value that required // allocating more contiguous space than can be allocated on this // operating system. // *Action: Reduce the value of the initialization parameter. 00065, 00000, "initialization of FIXED_DATE failed" // *Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss. // *Action: Make sure the initialization parameter is in the correct date // format. 00066, 00000, "SID %s contains an illegal character" // *Cause: The specified SID contains an illegal character which cannot occur // in an SPFILE setting. Illegal characters include ,#"'=() and // whitespace. // *Action: Use a SID that does not contain a special character or whitespace. 00067, 00000, "invalid value %s for parameter %s; must be at least %s" // *Cause: The value for the initialization parameter is invalid. // *Action: Choose a value as indicated by the message. 00068, 00000, "invalid value %s for parameter %s, must be between %s and %s" // *Cause: The value for the initialization parameter is invalid. // *Action: Choose a value as indicated by the message. 00069, 00000, "cannot acquire lock -- table locks disabled for %s" // *Cause: A command was issued that tried to lock the table indicated in // the message. Examples of commands that can lock tables are: // LOCK TABLE, ALTER TABLE ... ADD (...), and so on. // *Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry // the command. / / 70 .. 90 generic debugger errors / 00070, 00000, "command %s is not valid" // *Cause: An invalid debugger command was specified. // *Action: Type HELP to see the list of available commands. 00071, 00000, "process number must be between 1 and %s" // *Cause: An invalid process number was specified. // *Action: Specify a valid process number. 00072, 00000, "process \"%s\" is not active" // *Cause: An invalid process was specified. // *Action: Specify a valid process. 00073, 00000, "command %s takes between %s and %s argument(s)" // *Cause: An incorrect number of arguments was specified. // *Action: Specify the correct number of arguments. Type HELP // to see the list of commands and their syntax. 00074, 00000, "no process has been specified" // *Cause: No debug process has been specified. // *Action: Specify a valid process. 00075, 00000, "process \"%s\" not found in this instance" // *Cause: The specified process was not logged on to the current instance. // *Action: Specify a valid process. 00076, 00000, "dump %s not found" // *Cause: An attempt was made to invoke a dump that does not exist. // *Action: Type DUMPLIST to see the list of available dumps. 00077, 00000, "dump %s is not valid" // *Cause: An attempt was made to invoke an invalid dump. // *Action: Try another dump. 00078, 00000, "cannot dump variables by name" // *Cause: An attempt was made to dump a variable by name on a system that // does not support this feature. // *Action: Try the PEEK command. 00079, 00000, "variable %s not found" // *Cause: An attempt was made to dump a variable that does not exist. // *Action: Use a valid variable name. 00080, 00000, "invalid global area specified by level %s" // *Cause: An attempt was made to dump an invalid global area. // *Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. // Use 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: 00098, 00000, "creating or mounting the database requires a parameter file" // *Cause: An attempt was made to create or mount the database when the // instance was started without a parameter file. // *Action: Restart the instance with a parameter file. 00099, 00000, "warning: no parameter file specified for %s instance" // *Cause: Even though no parameter file was specified, the instance was // started with all default values. // *Action: None. 00100, 00000, "no data found" // *Cause: An application made reference to unknown or inaccessible data. // *Action: Handle this condition within the application or make appropriate // modifications to the application code. // NOTE: If the application uses Oracle-mode SQL instead of // ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100. / / 101 .. 149 shared server errors / 00101, 00000, "invalid specification for system parameter DISPATCHERS" // *Cause: The syntax for the DISPATCHERS parameter is incorrect. // *Action: Refer to the manual for correct syntax. 00102, 00000, "network protocol %s cannot be used by dispatchers" // *Cause: The network specified in DISPATCHERS does not have the // functionality required by the dispatchers. // *Action: Refer to the manual on network protocols supported by the // dispatchers. 00103, 00000, "invalid network protocol; reserved for use by dispatchers" // *Cause: The network specified in the SQL*Net connect string is reserved // for use by the dispatchers. // *Action: Specify other network protocols in the connection string. 00104, 00000, "deadlock detected; all public servers blocked waiting for resources" // *Cause: All available public servers are servicing requests that require // resources locked by a client which is unable to get a public // server to release the resources. // *Action: Increase the limit for the system parameter MAX_SHARED_SERVERS // as the system will automaticaly start // up new servers to break the deadlock until the number of // servers reaches the value specified in MAX_SHARED_SERVERS. 00105, 00000, "too many dispatcher configurations" // *Cause: Too many dispatcher configurations have been specified. // No more can be added. // *Action: Consolidate the dispatcher configurations if possible. 00106, 00000, "cannot startup/shutdown database when connected to a dispatcher" // *Cause: An attempt was made to startup/shutdown database when connected to // a shared server via a dispatcher. // *Action: Re-connect as user INTERNAL without going through the dispatcher. // For most cases, this can be done by connect to INTERNAL without // specifying a network connect string. 00107, 00000, "failed to connect to ORACLE listener process" // *Cause: Most likely due to the fact that ORACLE listener has not been // started. // *Action: Start ORACLE listener if it has not been started. Or else // contact your ORACLE representative. 00108, 00000, "failed to set up dispatcher to accept connection asynchronously" // *Cause: Most likely due to the fact that the network protocol used by the // the dispatcher does not support aynchronous operations. // *Action: Contact your ORACLE representative. 00109, 00000, "invalid value for attribute %s: %s" // *Cause: The value specified for the attribute was incorrect. // *Action: Refer to the manual for the proper values. 00110, 00000, "invalid value %s for attribute %s, must be between %s and %s" // *Cause: The value specified for the attribute was incorrect. // *Action: Specify a value within the range allowed. 00111, 00000, "invalid attribute %s" // *Cause: The specified attribute was not recognized. // *Action: Refer to the manual for the proper keyword to use to specify // a dispatcher attribute. 00112, 00000, "value of %s is null" // *Cause: The attribute was specified with no value. // *Action: Specify a non-null value. 00113, 00000, "protocol name %s is too long" // *Cause: A protocol name specified in the DISPATCHERS system parameter // is too long. // *Action: Use a valid protocol name for the DISPATCHERS value. 00114, 00000, "missing value for system parameter SERVICE_NAMES" // *Cause: No value was specified for the SERVICE_NAMES system parameter, // nor for the DB_NAME parameter. // *Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. // By default, SERVICE_NAMES is the value of DB_NAME unless // SERVICE_NAMES is explicitly specified. 00115, 00000, "connection refused; dispatcher connection table is full" // *Cause: A connection request was refused by a dispatcher because the // dispatcher cannot support any more connections. // *Action: Connect to a different dispatcher, or use a dedicated server. 00116, 00000, "SERVICE_NAMES name is too long" // *Cause: A service name specified in the SERVICE_NAMES system parameter // is too long. // *Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars). 00117, 00000, "PROTOCOL, ADDRESS or DESCRIPTION must be specified" // *Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified. // *Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION // to specify the listening address for dispatchers. 00118, 00000, "Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified" // *Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified. // *Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION // to specify the listening address for dispatchers. 00119, 00000, "invalid specification for system parameter %s" // *Cause: The syntax for the specified parameter is incorrect. // *Action: Refer to the Oracle Reference Manual for the correct syntax. 00122, 00000, "cannot initialize network configuration" // *Cause: ORACLE could not initialize SQL*Net version 2. // *Action: Check the error stack for detailed information. 00123, 00000, "idle public server terminating" // *Cause: Too many idle servers were waiting on the common queue. // *Action: This error is used internally, no action is required. 00125, 00000, "connection refused; invalid presentation" // *Cause: The PRESENTATION in the CONNECT_DATA of the TNS address // DESCRIPTION is not correct or is not supported. // *Action: Correct the PRESENTATION specified in the TNS address. 00126, 00000, "connection refused; invalid duplicity" // *Cause: The DUPLICITY in the CONNECT_DATA of the TNS address // DESCRIPTION is not correct or is not supported. // *Action: Correct the DUPLICITY specified in the TNS address. 00127, 00000, "dispatcher %s does not exist" // *Cause: There is currently no dispatcher running with the specified // name. // *Action: Retry with a name of the form "D###" denoting an existing // dispatcher process. 00128, 00000, "this command requires a dispatcher name" // *Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN // *Action: Use correct syntax: // ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name' 00129, 00000, "listener address validation failed '%s'" // *Cause: An error was encountered while validating the listener address. // *Action: Resolve error or contact your ORACLE representative. 00130, 00000, "invalid listener address '%s'" // *Cause: The listener address specification is not valid. // *Action: Make sure that all fields in the listener address // (protocol, port, host, key, ...) are correct. 00131, 00000, "network protocol does not support registration '%s'" // *Cause: The specified protocol does not support async notification. // *Action: Refer to the manual for information on supported network // protocols. 00132, 00000, "syntax error or unresolved network name '%s'" // *Cause: Listener address has syntax error or cannot be resolved. // *Action: If a network name is specified, check that it corresponds // to an entry in TNSNAMES.ORA or other address repository // as configured for your system. Make sure that the entry // is syntactically correct. 00133, 00000, "value of %s is too long" // *Cause: The value specified for the attribute was too long. // *Action: Use shorter names and keywords or remove unneeded blanks. 00134, 00000, "invalid DISPATCHERS specification #%s" // *Cause: The syntax for the n-th DISPATCHERS specification was incorrect. // *Action: Refer to the Oracle Reference Manual for the correct syntax. 00135, 00000, "missing attribute %s" // *Cause: The indicated mandatory attribute was not specified. // *Action: Specify a non-null value for the attribute. 00136, 00000, "invalid LISTENER_NETWORKS specification #%s" // *Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid. // *Action: Refer to the Oracle Reference Manual for the correct syntax. 00137, 00000, "invalid LISTENER_NETWORKS specification with NAME=%s" // *Cause: The syntax for the LISTENER_NETWORKS specification with the // indicated NAME was invalid. // *Action: Refer to the Oracle Reference Manual for the correct syntax. 00138, 00000, "all addresses specified for attribute %s are invalid" // *Cause: All of the specified addresses or aliases for the attribute were // invalid. // *Action: Specify at least one valid address or alias. 00139, 00000, "duplicate attribute %s" // *Cause: The indicated attribute was specified more than once. // *Action: Specify the attribute at most once. / / 150 .. 159 Oracle*XA errors / 00150, 00000, "duplicate transaction ID" // *Cause: Attempted to start a new transaction with an ID already in use // by an existing transaction. // *Action: Check your application. 00151, 00000, "invalid transaction ID" // *Cause: The specified transaction ID does not correspond to an existing // valid transaction. // *Action: Check your application. 00152, 00000, "current session does not match requested session" // *Cause: The current session is not the same as the session that was // passed into a upixado() call. // *Action: Check your application. 00153, 00000, "internal error in XA library" // *Cause: The XA library could not access thread-specific pointers. // *Action: Contact customer support. 00154, 00000, "protocol error in transaction monitor" // *Cause: The transaction monitor returned TMJOIN on an AX_REG call but // the transaction was locally suspended. // *Action: Contact the transaction monitor customer support. 00155, 00000, "cannot perform work outside of global transaction" // *Cause: The application tried to perform some work on either an Oracle // 7.3 server or an Oracle8 server with local transactions disabled // while outside of a global transaction. // *Action: Check if the application is connected to an Oracle 7.3 server. The // Transaction monitor must not return a NULL XID on an AX_REG call // when the resource manager is Oracle 7.3. If the application is // connected to an Oracle8 server, either set nolocal=f in the // xa_open string or start a global transaction prior to attempting // the work. // / / 160 .. 199 Distributed transaction errors (continued) / 00160, 00000, "global transaction length %s is greater than maximum (%s)" // *Cause: An external global transaction ID with a too large length field // was passed in. // *Action: Report the problem to your external transaction coordinator // vendor. 00161, 00000, "transaction branch length %s is illegal (maximum allowed %s)" // *Cause: An external transaction branch ID with a length either too large // or 0 was passed in. // *Action: Report the problem to your external transaction coordinator // vendor. 00162, 00000, "external dbid length %s is greater than maximum (%s)" // *Cause: An external database name with too large a length field // was passed in. // *Action: Report the problem to your external transaction coordinator // vendor. 00163, 00000, "internal database name length %s is greater than maximum (%s)" // *Cause: An internal database name with a too large length field // was passed in. // *Action: Report the problem to your external transaction coordinator // vendor. 00164, 00000, "distributed autonomous transaction disallowed within migratable distributed transaction" // *Cause: A request was made by the application to start a distributed // autonomous transaction when the application was in a migratable // distributed transaction. // *Action: Roll back or commit the current distributed transaction first. 00165, 00000, "migratable distributed autonomous transaction with remote operation is not allowed" // *Cause: A request was made by the application to start a migratable // distributed autonomous transaction with remote operation. // *Action: / 00166, 00000, "remote/local nesting level is too deep" // *Cause: Too many remote table operations required a reverse trip // back to the local site, for example to execute a local // function on a remote table. // *Action: Rearrange the query or co-locate the functions with the tables. / / 200 .. 249 control file management errors / 00200, 00000, "control file could not be created" // *Cause: It was not possible to create the control file. // *Action: Check that there is sufficient disk space and no conflicts in // filenames and try to create the control file again. 00201, 00000, "control file version %s incompatible with ORACLE version %s" // *Cause: The control file was created by incompatible software. // *Action: Either restart with a compatible software release or use // CREATE CONTROLFILE to create a new control file that is // compatible with this release. 00202, 00000, "control file: '%s'" // *Cause: This message reports the name file involved in other messages. // *Action: See associated error messages for a description of the problem. 00203, 00000, "using the wrong control files" // *Cause: The mount ID in the control file is not the same as the // mount ID in the control file used by the first instance to // mount this database. The control files are for the same database // but they are not the same files. Most likely one instance is using // a backup control file. // *Action: Check that the correct control files were specified. 00204, 00000, "error in reading (block %s, # blocks %s) of control file" // *Cause: A disk I/O failure was detected on reading the control file. // *Action: Check if the disk is online, if it is not, bring it online and try // a warm start again. If it is online, then you need to recover // the disk. 00205, 00000, "error in identifying control file, check alert log for more info" // *Cause: The system could not find a control file of the specified name and // size. // *Action: Check that ALL control files are online and that they are the same // files that the system created at cold start time. 00206, 00000, "error in writing (block %s, # blocks %s) of control file" // *Cause: A disk I/O failure was detected on writing the control file. // *Action: Check if the disk is online, if it is not, bring it online and try // a warm start again. If it is online, then you need to // recover the disk. 00207, 00000, "control files are not for the same database" // *Cause: The database ID in the control file is not the same as the // database ID in the control file used by the first instance to // mount this database. Most likely one of the mounts used the wrong // control file or there are two databases with the same name. // *Action: Check that the control file is for the correct database and is // not an old version. 00208, 00000, "number of control file names exceeds limit of %s" // *Cause: An attempt was made to use more control files than Oracle supports. // *Action: Shut down Oracle. Reduce the number of control files specified in // the CONTROL_FILES parameter in the initialization parameter // file, and restart Oracle. Delete usused files. 00209, 00000, "control file blocksize mismatch, check alert log for more info" // *Cause: The block size in the control file header does not match the // size specified in the DB_BLOCK_SIZE parameter. // *Action: Look at the alert log for more information. 00210, 00000, "cannot open the specified control file" // *Cause: Cannot open the control file. // *Action: Check to make sure the control file exists and is not locked by // some other program. 00211, 00000, "control file does not match previous control files" // *Cause: A control file was specified that belongs to another database. // *Action: Find and install the correct control file. 00212, 00000, "block size %s below minimum required size of %s bytes" // *Cause: The block size specified was too small. Space for the // system overhead is required. // *Action: Specify a larger block size and retry the operation. 00213, 00000, "cannot reuse control file; old file size %s, %s required" // *Cause: To reuse a control file, it must be the same size as // the one previously used. // *Action: Either do not specify REUSE, or specify a matching combination of // MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and // MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE // statement. 00214, 00000, "control file '%s' version %s inconsistent with file '%s' version %s" // *Cause: An inconsistent set of control files, datafiles/logfiles, and redo // files was used. // *Action: Use a consistant set of control files, datafiles/logfiles, and redo // log files. That is, all the files must be for the same database // and from the same time period. 00215, 00000, "must be at least one control file" // *Cause: No control file is specified or the control file specified does // not exist. // *Action: Specify at least one valid control file and retry the operation. 00216, 00000, "control file could not be resized for migration from 8.0.2" // *Cause: The control file created by release 8.0.2 was missing some record // types. These record types are automatically added by resizing // the control file during mount. The resize has failed. // *Action: Look in the alert log for the reason that the resize has failed. // If indicated in the alert log, give the control file more space. // Otherwise, use the CREATE CONTROLFILE script dumped to the trace // file to create a new control file. 00217, 00000, "control file could not be resized for new record types" // *Cause: The control file was missing some new record types supported // by this release. These record types are automatically added // by resizing the contol file during mount. The resize has failed. // *Action: Look in the alert log for the reason that the resize has failed. // If indicated in the alert log, give the control file more space. // Otherwise, use the CREATE CONTROLFILE script dumped to the trace // file to create a new control file. 00218, 00000, "block size %s of control file '%s' does not match DB_BLOCK_SIZE (%s)" // *Cause: The block size as stored in the control file header is // different from the value of the initialization parameter // DB_BLOCK_SIZE. This might be due to an incorrect setting of // DB_BLOCK_SIZE, or else might indicate that the control file has // either been corrupted or belongs to a different database. // *Action: Restore a good copy of the control file. If the control file is // known to be clean set the DB_BLOCK_SIZE to match control file // headers block size value. 00219, 00000, "required control file size (%s logical blocks) exceeds maximum allowable size (%s logical blocks)" // *Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE // was executed specifying a combination of parameters that would // require the control file size in blocks to exceed the maximum // allowable value. // *Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a // different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, // MAXLOGHISTORY, and MAXINSTANCES clauses. 00220, 00000, "control file not mounted by first instance, check alert log for more info" // *Cause: The specified control file has a different mount ID than the // other control files that are being mounted. This means that // the first instance to mount the database did not use this // control file. // *Action: Find and install the correct control file. 00221, 00000, "error on write to control file" // *Cause: An error occurred when writing to one or more of the control files. // *Action: See accompanying messages. 00222, 00000, "operation would reuse name of a currently mounted control file" // *Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP // CONTROLFILE command or to cfileSetSnapshotName matches the // name of the specified currently mounted control file. // *Action: Retry the operation with a different filename. 00223, 00000, "convert file is invalid or incorrect version" // *Cause: An Oracle7 to Oracle8 convert file contains invalid data // or was created with an different version of the migration utility. // This error can also be caused by incorrect ORACLE_HOME environment // variable when ALTER DATABASE CONVERT command is issued. // *Action: Use a correct version of the convert file or regenerate it with // the migration utility. Make sure that the migration utility is the // same version as the Oracle8 RDBMS executable and that the // ORACLE_HOME environment variable is properly set. 00224, 00000, "control file resize attempted with illegal record type (%s)" // *Cause: An attempt was made to expand or shrink the control file by calling // cfileResizeSection using an invalid value for the RECORD_TYPE // parameter. // *Action: Use a value for the RECORD_TYPE parameter that specifies a // valid record type other than type 0 (valid range is 1-16). 00225, 00000, "expected size %s of control file differs from actual size %s" // *Cause: The expected size of the control file as stored in its // header was different than the actual operating system file size. // This usually indicates that the control file was corrupted. // *Action: Restore a good copy of the control file. 00226, 00000, "operation disallowed while alternate control file open" // *Cause: The attempted operation could not be executed at this time because // this process had an alternate control file open for fixed table // access. // *Action: Retry the operation after calling cfileUseCurrent. 00227, 00000, "corrupt block detected in control file: (block %s, # blocks %s)" // *Cause: A block header corruption or checksum error was detected on reading // the control file. // *Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP // CONTROLFILE command. 00228, 00000, "length of alternate control file name exceeds maximum of %s" // *Cause: The specified filename, which was supplied as a parameter // to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum // filename length for this operating system. // *Action: Retry the operation with a shorter filename. 00229, 00000, "operation disallowed: already hold snapshot control file enqueue" // *Cause: The attempted operation cannot be executed at this time because // this process currently holds the snapshot control file enqueue. // *Action: Retry the operation after calling cfileUseCurrent to release the // snapshot control file enqueue. 00230, 00000, "operation disallowed: snapshot control file enqueue unavailable" // *Cause: The attempted operation cannot be executed at this time because // another process currently holds the snapshot control file enqueue. // *Action: Retry the operation after the concurrent operation that is holding // the snapshot control file enqueue terminates. 00231, 00000, "snapshot control file has not been named" // *Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot // it was detected that no filename for the snapshot control file had // previously been specified. // *Action: Specify a name for the snapshot control file by calling // cfileSetSnapshotName. 00232, 00000, "snapshot control file is nonexistent, corrupt, or unreadable" // *Cause: The snapshot control file was found to be nonexistent, corrupt, // or unreadable during an invocation of cfileUseSnapshot. // *Action: Call cfileMakeAndUseSnapshot again (or for the first time). 00233, 00000, "copy control file is corrupt or unreadable" // *Cause: The specified copy control file was found to be corrupt or // unreadable during an invocation of cfileUseCopy. // *Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP // CONTROLFILE command and specify the same filename that was // specified for cfileUseCopy. 00234, 00000, "error in identifying or opening snapshot or copy control file" // *Cause: A snapshot or copy control file of the specified name // could not be found or opened during an invocation of // cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy. // *Action: Re-create the snapshot or copy control file using // cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, // respectively. 00235, 00000, "control file read without a lock inconsistent due to concurrent update" // *Cause: Concurrent update activity on a control file caused a process // to read inconsistent information from the control file // without a lock. // *Action: Retry the operation. 00236, 00000, "snapshot operation disallowed: mounted control file is a backup" // *Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, // or cfileUseSnapshot when the currently mounted control file is a // backup control file. // *Action: Mount a current control file and retry the operation. 00237, 00000, "snapshot operation disallowed: control file newly created" // *Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently // mounted control file that was newly created with CREATE CONTROLFILE // was made. // *Action: Mount a current control file and retry the operation. 00238, 00000, "operation would reuse a filename that is part of the database" // *Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP // CONTROLFILE command or to cfileSetSnapshotName matches the name of // a file that is currently part of the database. // *Action: Retry the operation with a different filename. 00239, 00000, "timeout waiting for control file enqueue: held by '%s' for more than %s seconds" // *Cause: The specified process waited the maximum allowed time for the control file enqueue. // *Action: Restart the blocking instance indicated in the incident trace file // or reboot the blocking node. 00240, 00000, "control file enqueue held for more than %s seconds" // *Cause: The current process did not release the control file enqueue within // the maximum allowed time. // *Action: Reissue any commands that failed and contact Oracle Support // Services with the incident information. 00241, 00000, "operation disallowed: control file inconsistent with data dictionary" // *Cause: The control file was either recently created via CREATE // CONTROLFILE or an incomplete recovery has been done. // Thus, the datafiles in the control file and the ones in the // data dictionary may not match. // *Action: Open the database, then retry the operation. 00242, 00000, "maximum allowed filename records used up in control file" // *Cause: Failed to create a new filename record entry in the control file // because the maximum allowed filename records have been allocated // and are in use. // *Action: Free up controlfile filename section entries by dropping unwanted // tablespaces/datafiles/redofiles. 00243, 00000, "failed to expand control file filename section by %s records" // *Cause: Failed to expand control file filename section. See alert log for // more details. // *Action: Retry the operation after increasing disk space for controlfile // expansion. 00244, 00000, "concurrent control file backup operation in progress" // *Cause: Failed to create a control file backup because concurrent control // file backup operation was in progress. // *Action: Retry backup creation later. 00245, 00000, "control file backup failed; target is likely on a local file system" // *Cause: Failed to create a control file backup because some process // signaled an error during backup creation. This is likely caused // by the backup target being on a local file system so it could not // be accessed by other instances. It can also be caused by other // I/O errors to the backup target. Any process of any instance that // starts a read/write control file transaction must have access // to the backup control file during backup creation. // *Action: Check alert files of all instances for further information. 00246, 00000, "control file backup failed; error accessing backup target" // *Cause: An attempt to create a control file backup failed because some process // signaled an I/O error when accessing the backup target. // *Action: Check alert and trace files for further information. / / 250 .. 299 archival & media recovery errors / 00250, 00000, "archiver not started" // *Cause: An attempt was made to stop automatic archiving, but the // archiver process was not running. // *Action: No action required. 00251, 00000, "LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string %s" // *Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST // parameter is the same as the destination specified by an ALTER // SYSTEM ARCHIVE LOG START TO command. // *Action: Specify a different destination for parameter // LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the // ALTER SYSTEM command. 00252, 00000, "log %s of thread %s is empty, cannot archive" // *Cause: A log must be used for redo generation before it can be archived. // The specified redo log was not been used since it was introduced // to the database. However it is possible that instance death during // a log switch left the log empty. // *Action: Empty logs do not need to be archived. Do not attempt to // archive the redo log file. 00253, 00000, "character limit %s exceeded by archive destination string %s" // *Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO // command was too long. // *Action: Retry the ALTER SYSTEM command using a string shorter than the // limit specified in the error message. 00254, 00000, "error in archive control string '%s'" // *Cause: The specified archive log location is invalid in the archive // command or the LOG_ARCHIVE_DEST initialization parameter. // *Action: Check the archive string used to make sure it refers to a valid // online device. 00255, 00000, "error archiving log %s of thread %s, sequence # %s" // *Cause: An error occurred during archiving. // *Action: Check the accompanying message stack for more detailed // information. // // If the online log is corrupted, // then the log can be cleared using the UNARCHIVED option. This will // make any existing backups useless for recovery to any time after // the log was created, but will allow the database to generate redo. 00256, 00000, "cannot translate archive destination string %s" // *Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO // command could not be translated. // *Action: Check the accompanying message stack for more detailed information. // Then, retry the ALTER SYSTEM command using a different string. 00257, 00000, "archiver error. Connect internal only, until freed." // *Cause: The archiver process received an error while trying to archive // a redo log. If the problem is not resolved soon, the database // will stop executing transactions. The most likely cause of this // message is the destination device is out of space to store the // redo log file. // *Action: Check archiver trace file for a detailed description // of the problem. Also verify that the // device specified in the initialization parameter // ARCHIVE_LOG_DEST is set up properly for archiving. 00258, 00000, "manual archiving in NOARCHIVELOG mode must identify log" // *Cause: The database is in NOARCHIVELOG mode and a command to manually // archive a log did not specify the log explicitly by sequence // number, group number or filename. // *Action: Specify log by filename, by group number or by thread and // sequence number. 00259, 00000, "log %s of open instance %s (thread %s) is the current log, cannot archive" // *Cause: An attempt was made to archive the current log of an open // thread. This is not allowed because the redo log file may // still be in use for the generation of redo entries. // *Action: Force a log switch in the instance where the thread is open. // If no instances are open, open the database so that instance // recovery can recover the thread. 00260, 00000, "cannot find online log sequence %s for thread %s" // *Cause: The log sequence number supplied to the archival command does // not match any of the online logs for the thread. The log might // have been reused for another sequence number, it might have been // dropped, the sequence number might be greater than the current // log sequence number, or the thread might not have any logs. // *Action: Check the ARCHIVE statement, then specify a valid log sequence // number. Specify a valid log sequence number. 00261, 00000, "log %s of thread %s is being archived or modified" // *Cause: The log is either being archived by another process or an // administrative command is modifying the log. Operations that // modify the log include clearing, adding a member, dropping a // member, renaming a member, and dropping the log. // *Action: Wait for the current operation to complete and try again. 00262, 00000, "current log %s of closed thread %s cannot switch" // *Cause: The log cannot be cleared or manually archived because it is // the current log of a closed thread, and it is not possible to // switch logs so another log is current. All other logs for the // thread need to be archived, or cleared, and cannot be reused. // *Action: Archive another log in the same thread first, or complete the // clearing. See attached errors for the reason the switch cannot // be completed. 00263, 00000, "there are no logs that need archiving for thread %s" // *Cause: An attempt was made to manually archive the unarchived logs in this // thread but no logs needed archiving. // *Action: No action required. 00264, 00000, "no recovery required" // *Cause: An attempt was made to perform media recovery on files that do not // need any type of recovery. // *Action: Do not attempt to perform media recovery on the selected // files. Check to see that the filenames were entered properly. // If not, retry the command with the proper filenames. 00265, 00000, "instance recovery required, cannot set ARCHIVELOG mode" // *Cause: The database either crashed or was shutdown with the ABORT // option. Media recovery cannot be enabled because the online // logs may not be sufficient to recover the current datafiles. // *Action: Open the database and then enter the SHUTDOWN command with the // NORMAL or IMMEDIATE option. 00266, 00000, "name of archived log file needed" // *Cause: During media recovery, the name of an archived redo log file // was requested, but no name was entered. // *Action: Mount the correct redo log file and enter its name when it // is requested. 00267, 00000, "name of archived log file not needed" // *Cause: During media recovery, the name of an archived redo log file // was entered, but no name was requested. // *Action: Continue media recovery, but do not enter a new log name. 00268, 00000, "specified log file does not exist '%s'" // *Cause: The given redo log file does not exist. // *Action: Check the spelling and capitalization of the filename and // retry the command. 00269, 00000, "specified log file is part of thread %s not %s" // *Cause: The given redo log file is not part of the given thread // *Action: Check that the thread of the redo log file matches the // thread on the command line. If not, use a redo log file // from the appropriate thread. Retry the command after // correcting the error. 00270, 00000, "error creating archive log %s" // *Cause: An error was encountered when either creating or opening // the destination file for archiving. // *Action: Check that the archive destination is valid and that there // is sufficient space on the destination device. 00271, 00000, "there are no logs that need archiving" // *Cause: An attempt was made to archive the unarchived redo log // files manually, but there are no files that need to be archived. // *Action: No action required. 00272, 00000, "error writing archive log %s" // *Cause: An I/O error occurred while archiving a redo log file. // *Action: Check that the output device is still available and correct // any device errors that may have occurred. Also, make certain // that sufficient space for archiving is available on the // output device. 00273, 00000, "media recovery of direct load data that was not logged" // *Cause: A media recovery session encountered a table that was loaded // by the direct loader without logging any redo information. Some // or all of the blocks in this table are now marked as corrupt. // *Action: The table must be dropped or truncated so that the corrupted // blocks can be reused. If a more recent backup of the file is // available, try to recover this file to eliminate this error. 00274, 00000, "illegal recovery option %s" // *Cause: An illegal option was specified for a recovery command. // *Action: Correct the syntax and retry the command. 00275, 00000, "media recovery has already been started" // *Cause: An attempt was made to start a second media recovery operation // in the same session. // *Action: Complete or cancel the first media recovery session or // start another session to perform media recovery. 00276, 00000, "CHANGE keyword specified but no change number given" // *Cause: The CHANGE keyword was specified on the command line, but // no change number was given. // *Action: Retry the command using a valid change number after the CHANGE // keyword. 00277, 00000, "illegal option to the UNTIL recovery flag %s" // *Cause: Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the // UNTIL keyword. // *Action: Correct the syntax. 00278, 00000, "log file '%s' no longer needed for this recovery" // *Cause: The specified redo log file is no longer needed for the current // recovery. // *Action: No action required. The archived redo log file may be removed // from its current location to conserve disk space, if needed. // However, the redo log file may still be required for another // recovery session in the future. 00279, 00000, "change %s generated at %s needed for thread %s" // *Cause: The requested log is required to proceed with recovery. // *Action: Please supply the requested log with "ALTER DATABASE RECOVER // LOGFILE " or cancel recovery with "ALTER DATABASE // RECOVER CANCEL". 00280, 00000, "change %s for thread %s is in sequence #%s" // *Cause: This message helps to locate the redo log file with the // specified change number requested by other messages. // *Action: Use the information provided in this message to specify the // required archived redo log files for other errors. 00281, 00000, "media recovery may not be performed using dispatcher" // *Cause: An attempt was made to use a dispatcher process for media // recovery. Memory requirements disallow this recovery method. // *Action: Connect to the instance via a dedicated server process to // perform media recovery. 00282, 00000, "UPI %s call not supported, use ALTER DATABASE RECOVER" // *Cause: The given UPI call is no longer supported. // *Action: Use the ALTER DATABASE RECOVER command for all recovery actions. 00283, 00000, "recovery session canceled due to errors" // *Cause: An error during recovery was determined to be fatal enough to end // the current recovery session. // *Action: More specific messages will accompany this message. Refer to // the other messages for the appropriate action. 00284, 00000, "recovery session still in progress" // *Cause: An error during recovery was determined to be minor enough to allow // the current recovery session to continue. // *Action: More specific messages will accompany this message. Refer to // the other messages for the appropriate action. 00285, 00000, "TIME not given as a string constant" // *Cause: UNTIL TIME was not followed by a string constant for the time. // *Action: Enter the time enclosed in single quotation marks. 00286, 00000, "no members available, or no member contains valid data" // *Cause: None of the members of a redo log file group are available, or // the available members do not contain complete data. // *Action: If a member is temporarily offline, attempt to make it available. // Make sure that the correct filenames are being used, especially // if the redo log file is being accessed from a remote location. 00287, 00000, "specified change number %s not found in thread %s" // *Cause: The given change number does not appear in any of the online // redo logs for the given thread. // *Action: Check the statement to make certain a valid change number // is given. Perhaps try to use the NEXT option for archiving logs. 00288, 00000, "to continue recovery type ALTER DATABASE RECOVER CONTINUE" // *Cause: During media recovery, a new log is not required but the // continuation command is necessary to do a checkpoint and // report errors. // *Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume. 00289, 00000, "suggestion : %s" // *Cause: This message reports the next redo log filename that is needed, // according to the initialization parameters LOG_ARCHIVE_DEST and // LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST // and LOG_ARCHIVE_FORMAT are the same now as when the required redo // log file was archived. // *Action: Consider using this filename for the next log needed for recovery. 00290, 00000, "operating system archival error occurred. See error below" // *Cause: While attempting to archive to a redo log file, the server // encountered an unexpected operating system error. // *Action: Correct the operating system error given in the messages and // retry the operation. See also your operating system-specific // Oracle documentation. 00291, 0000, "numeric value required for PARALLEL option" // *Cause: A recovery command was specified incorrectly. The PARALLEL option // must be followed by a numeric argument that specifies the degree // of parallelism. // *Action: Re-enter the command with a numeric argument specifying the // degree of parallelism desired. 00292, 00000, "parallel recovery feature not installed" // *Cause: A parallel recovery was requested when the parallel // recovery option is not installed. // *Action: Delete the PARALLEL clause from the RECOVER command. Also, // delete the RECOVERY_PARALLELISM parameter in the initialization // file. 00293, 00000, "control file out of sync with redo log" // *Cause: The redo log file and control file are out of sync because a // non-current controle file was specified when the instance // was started. // *Action: Retry the RECOVER command using the current control file, or retry // the RECOVER command using the USING BACKUP CONTROLFILE clause. 00294, 00000, "invalid archivelog format specifier '%s'" // *Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT // initialization parameter. The only characters permitted // following the % symbol are s, S, t, and T. // *Action: Correct the initialization file and re-start the instance. 00295, 00000, "datafile/tempfile number %s is invalid, must be between 1 and %s" // *Cause: An invalid file number was specified. // *Action: Specify a valid datafile or tempfile number // and retry the operation. 00296, 00000, "maximum number of files (%s) exceeded for RECOVER DATAFILE LIST" // *Cause: The RECOVER DATAFILE LIST command specified more datafiles than // are allowed by the DB_FILES initialization parameter. // This error occurs when doing recovery with Recovery Manager, and // the instance has been started with a DB_FILES parameter specifying // fewer datafiles than recovery manager needs to recover to satisfy // the user's RECOVER command. // *Action: Re-start the instance with a higher value for DB_FILES. 00297, 00000, "must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START" // *Cause: The RECOVER DATAFILE START command was issued, but no RECOVER // DATAFILE LIST commands had been issued. This only happens when // doing recovery with Recovery Manager, and is an internal error in // Recovery Manager, because Recovery Manager should always issue // RECOVER DATAFILE LIST before RECOVER DATAFILE START. // *Action: Contact customer support 00298, 00000, "Missing or invalid attribute value" // *Cause: A non-zero integer value is required when the following keyword // attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT // *Action: Correct the syntax and retry the command. 00299, 00000, "must use file-level media recovery on data file %s" // *Cause: The control file does not contain an entry for this file, so // block media recovery cannot be done. // *Action: Restore the data file and perform file-level media recovery. / / 300..369 - Redo File errors / 00300, 00000, "illegal redo log block size %s specified - exceeds limit of %s" // *Cause: The specified block size of the redo log is greater than the // maximum block size for the operating system. // *Action: Create the redo log on a device with a smaller block size 00301, 00000, "error in adding log file '%s' - file cannot be created" // *Cause: The creation of the redo log file failed // *Action: Check: 1) there is enough storage space on the device // 2) the name of the file is valid // 3) the device is online // 4) an IO error occurred // Also, it is possible REUSE was specified on the command line and // a file of the incorrect size exists. Either do not specify REUSE // or use a file of the correct size. 00302, 00000, "limit of %s logs exceeded" // *Cause: The maximum number of redo log files has been exceeded. // *Action: Use the CREATE CONTROLFILE command with a larger value // for MAXLOGFILES if the compatibility is lower than 10.2.0. // Otherwise, allocate more storage space for the control file. 00303, 00000, "cannot process Parallel Redo" // *Cause: A redo log containing Parallel Redo has been detected. // The current Oracle release cannot process this format of redo. // *Action: Use a later release that supports Parallel Redo. // to process this log. 00304, 00000, "requested INSTANCE_NUMBER is busy" // *Cause: An instance tried to start by using a value of the // initialization parameter INSTANCE_NUMBER that is already in use. // *Action: Either // a) specify another INSTANCE_NUMBER, // b) shut down the running instance with this number // c) wait for instance recovery to complete on the instance with // this number. 00305, 00000, "log %s of thread %s inconsistent; belongs to another database" // *Cause: The database ID in the redo log file does not match the database // ID in the control file. This redo log file is not from the // current database. // *Action: Specify the correct redo log file, then retry the operation. 00306, 00000, "limit of %s instances in this database" // *Cause: Starting this instance would exceed the maximum number // of instances allowed for this database. This message occurs // only with STARTUP shared and multiple instances. // *Action: You cannot start more than the lower of // a) port-specific limit as to the number of instances // b) the number of instances specified at create-database time 00307, 00000, "requested INSTANCE_NUMBER out of range, maximum is %s" // *Cause: The initialization parameter INSTANCE_NUMBER specified a // number that was out of range. // *Action: Change INSTANCE_NUMBER to a valid range and restart the // instance. The minimum value is one and the maximum value is // the lower of the operating system-specific maximum or // the MAXINSTANCES option specified in the CREATE DATABASE // statement. See also your operating system-specific Oracle // documentation. 00308, 00000, "cannot open archived log '%s'" // *Cause: The system cannot access a required archived redo log file. // *Action: Check that the off line log exists, the storage device is // online, and the archived file is in the correct location. // Then attempt to continue recovery or restart the recovery // session. 00309, 00000, "log belongs to wrong database" // *Cause: The system cannot access the archived redo log because it // belongs to another database. // *Action: Specify the correct redo log file, then retry the operation. 00310, 00000, "archived log contains sequence %s; sequence %s required" // *Cause: The archived log is out of sequence, probably because it // is corrupted or the wrong redo log filename was specified / during recovery. // *Action: Specify the correct redo log file; then retry the operation. 00311, 00000, "cannot read header from archived log" // *Cause: An I/O error occurred when attempting to read the log file header // from the specified archived redo log file. // *Action: Other messages will accompany this message. See the // associated messages for the appropriate action to take. 00312, 00000, "online log %s thread %s: '%s'" // *Cause: This message reports the filename for details of another message. // *Action: Other messages will accompany this message. See the // associated messages for the appropriate action to take. 00313, 00000, "open failed for members of log group %s of thread %s" // *Cause: The online log cannot be opened. May not be able to find file. // *Action: See accompanying errors and make log available. 00314, 00000, "log %s of thread %s, expected sequence# %s doesn't match %s" // *Cause: The online log is corrupted or is an old version. // *Action: Find and install correct version of log or reset logs. 00315, 00000, "log %s of thread %s, wrong thread # %s in header" // *Cause: The online log is corrupted or is an old version. // *Action: Find and install correct version of log or reset logs. 00316, 00000, "log %s of thread %s, type %s in header is not log file" // *Cause: The online log is corrupted or is an old version. // *Action: Find and install correct version of log or reset logs. 00317, 00000, "file type %s in header is not log file" // *Cause: This is not an archived log file. // *Action: Find the correct file and try again. 00318, 00000, "log %s of thread %s, expected file size %s doesn't match %s" // *Cause: On header read the file size indicated in the control // file did not match the file size contained in the log file. // *Action: Restore correct file or reset logs. 00319, 00000, "log %s of thread %s has incorrect log reset status" // *Cause: Check of log file header at database open found that an online // log has log reset data that is different from the control file. // The log is probably an incorrectly restored backup. // *Action: Restore correct file or reset logs. 00320, 00000, "cannot read file header from log %s of thread %s" // *Cause: The file is not available. // *Action: Restore the log file. 00321, 00000, "log %s of thread %s, cannot update log file header" // *Cause: Cannot write to the log file. // *Action: Restore the access to the file. 00322, 00000, "log %s of thread %s is not current copy" // *Cause: Check of log file header at database open found that an online // log appears to be an incorrectly restored backup. // *Action: Restore correct file or reset logs. 00323, 00000, "Current log of thread %s not useable and all others need archiving" // *Cause: Attempt to open thread failed because it is necessary to switch // redo generation to another online log, but all the other logs // need to be archived before they can be used. // *Action: Archive the logs for the thread then retry open. 00324, 00000, "log file '%s' translated name '%s' too long, %s characters exceeds %s limit" // *Cause: the translated name for a log file is too long. // *Action: Choose a untranslated name that yields a shorter translated name. 00325, 00000, "archived log for thread %s, wrong thread # %s in header" // *Cause: The archived log is corrupted or for another thread. Can not // use the log for applying redo. // *Action: Find correct archived log. 00326, 00000, "log begins at change %s, need earlier change %s" // *Cause: The archived log supplied for recovery was generated after the // log that is needed. Can not yet use the log for applying redo. // *Action: Find correct archived log. 00327, 00000, "log %s of thread %s, physical size %s less than needed %s" // *Cause: A log file has shrunk in size. This is likely // to have been caused by operator or operating system error. // *Action: Restore the log file from backup. If backup is not available, // drop this log and re-create. If the database was shut down // cleanly, no further action should be required; otherwise // incomplete recovery may be required. 00328, 00000, "archived log ends at change %s, need later change %s" // *Cause: The archived log supplied for recovery was generated before the // log that is needed. Can not use the log for applying redo. // *Action: Find correct archived log. 00329, 00000, "archived log begins at change %s, need change %s" // *Cause: The archived log is not the correct log. An earlier log is needed. // *Action: Restore the correct log file. 00330, 00000, "archived log ends at change %s, need change %s" // *Cause: The archived log is not the correct log. A later log is needed. // *Action: Restore the correct log file. 00331, 00000, "log version %s incompatible with ORACLE version %s" // *Cause: The log was written by incompatible version of Oracle. // *Action: Recover the database with the compatible software, shut it // down cleanly, then restart with current software. 00332, 00000, "archived log is too small - may be incompletely archived" // *Cause: The log is smaller than the space allocated in it. May be the // result of a shutdown abort while it was being written by the // archiver. // *Action: Get a complete version of this log and use it for recovery. There // should either be an online version of it or a copy that was // successfully archived. 00333, 00000, "redo log read error block %s count %s" // *Cause: An IO error occurred while reading the log described in the // accompanying error. // *Action: Restore accessibility to file, or get another copy of the file. 00334, 00000, "archived log: '%s'" // *Cause: Reporting filename for details of another error // *Action: See associated error messages 00335, 00000, "online log %s: No log with this number, log does not exist" // *Cause: Reporting filename for details of another error // *Action: See associated error messages 00336, 00000, "log file size %s blocks is less than minimum %s blocks" // *Cause: The log file size as specified in create database is too small. // *Action: Increase the log file size. 00337, 00000, "log file '%s' does not exist and no size specified" // *Cause: An attempt to add a log found neither an existing file // nor a size for creating the file. // *Action: Specify a size for the log file. 00338, 00000, "log %s of thread %s is more recent than control file" // *Cause: The control file change sequence number in the log file is // greater than the number in the control file. This implies that // the wrong control file is being used. Note that repeatedly causing // this error can make it stop happening without correcting the real // problem. Every attempt to open the database will advance the // control file change sequence number until it is great enough. // *Action: Use the current control file or do backup control file recovery to // make the control file current. Be sure to follow all restrictions // on doing a backup control file recovery. 00339, 00000, "archived log does not contain any redo" // *Cause: The archived log is not the correct log. It is a copy of a log file // that has never been used for redo generation, or was an online // log being prepared to be the current log. // *Action: Restore the correct log file. 00340, 00000, "IO error processing online log %s of thread %s" // *Cause: An IO error occurred on the named online log. // *Action: Restore accessibility to file, or restore file from backup. 00341, 00000, "log %s of thread %s, wrong log # %s in header" // *Cause: The internal information in an online log file does not // match the control file. // *Action: Restore correct file or reset logs. 00342, 00000, "archived log does not have expected resetlogs SCN %s" // *Cause: Recovery was given a log that does not belong to current // incarnation or one of the parent incarnation. There should be // another log that contains the correct redo. // *Action: Supply the correct log file. 00344, 00000, "unable to re-create online log '%s'" // *Cause: An I/O failure occurred when attempting to re-create an online as // part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE // CLEAR LOGFILE command. // *Action: Correct the file/device as indicated by accompanying errors. 00345, 00000, "redo log write error block %s count %s" // *Cause: An IO error has occurred while writing the log // *Action: Correct the cause of the error, and then restart the system. // If the log is lost, apply media/incomplete recovery. 00346, 00000, "log member marked as STALE and closed" // *Cause: A log file member was no longer complete. // *Action: Correct the underlying problem by referring to the other error // messages found with this one. 00347, 00000, "log %s of thread %s, expected block size %s doesn't match %s" // *Cause: On header read the blocksize indicated in the control // file did not match the blocksize contained in the log file. // *Action: Restore correct file or reset logs. 00348, 00000, "single-process redo failure. Must abort instance" // *Cause: A failure occurred during a critical portion of the log code // during single process operation. This error does not occur // during normal multi-process operation. // *Action: Shutdown abort and warmstart the database. 00349, 00000, "failure obtaining block size for '%s'" // *Cause: The operating system was unable to determine the blocksize // for the given filename. // *Action: Consult the accompanying error message, and correct the // device or specify another filename. 00350, 00000, "log %s of instance %s (thread %s) needs to be archived" // *Cause: The command cannot be done because the log has not been archived, // and media recovery has been enabled. // *Action: Archive the log or disable media recovery. If the command supports // an UNARCHIVED option then it can be used. However this may result // in making backups unuseable, and forcing the drop of some offline // files. 00351, 00000, "recover-to time invalid" // *Cause: The time specified in a recover-until statement must // be after January 1st 1988. // *Action: Specify a time after January 1st 1988. 00352, 00000, "all logs for thread %s need to be archived - cannot enable" // *Cause: Attempting to enable a thread with all logs needing to be // archived, and media recovery has been enabled. There is no log // that can be made the new current log for the thread. // *Action: Archive a log for the thread or disable media recovery. 00353, 00000, "log corruption near block %s change %s time %s" // *Cause: Some type of redo log corruption has been discovered. This error // describes the location of the corruption. Accompanying errors // describe the type of corruption. // *Action: Do recovery with a good version of the log or do incomplete // recovery up to the indicated change or time. 00354, 00000, "corrupt redo log block header" // *Cause: The block header on the redo block indicated by the accompanying // error, is not reasonable. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. If this happens when archiving, // archiving of the problem log can be skipped by clearing the log // with the UNARCHIVED option. This must be followed by a backup of // every datafile to insure recoverability of the database. 00355, 00000, "change numbers out of order" // *Cause: A change number found in the redo log is lower than a previously // encountered change number. The log is corrupted in some way. The // corruption may be at the earlier change or at this one. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. 00356, 00000, "inconsistent lengths in change description" // *Cause: A change record in the redo log contains lengths that do not add // up to a consistent value. The log is corrupted in some way. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. 00357, 00000, "too many members specified for log file, the maximum is %s" // *Cause: An add logfile or add logfile member command would result in a // log with too many members. The number of members is set when the // database is created. // *Action: Use fewer log file members. 00358, 00000, "Too many file members specified, the maximum is %s" // *Cause: A create or alter statement specified too many members in a // parenthesised file list. // *Action: Specify a number of file members that is within the port-defined // limit. 00359, 00000, "logfile group %s does not exist" // *Cause: An add logfile member or drop logfile request specified a logfile // group number that does not exist. // *Action: Check the configuration of the log files and reissue the command. 00360, 00000, "not a logfile member: %s" // *Cause: A filename was given to drop logfile member that is not a // part of the database, or which is a data file. // *Action: Supply a valid logfile member name. 00361, 00000, "cannot remove last log member %s for group %s" // *Cause: An attempt has been made to remove the last member of a log file // group. // *Action: If desired, delete the entire log, by using DROP LOGFILE. 00362, 00000, "member is required to form a valid logfile in group %s" // *Cause: A request to drop a logfile member was denied because it would // remove data required to form a complete logfile. // *Action: If desired, delete the entire log (after archiving if required), // by using DROP LOGFILE; 00363, 00000, "log is not the archived version" // *Cause: The log given to recovery is a backup of the online version from // the time it was the current log. The archived version of the log // would not be marked as end of thread. This error can also be // caused by failing to list the current log of an enabled thread // in a CREATE CONTROLFILE command. // *Action: Find the archived version of the log and supply its name. If this // is media recovery immediately following a CREATE CONTROLFILE, be // sure the current log for this thread was included. 00364, 00000, "cannot write header to new log member" // *Cause: An i/o error occurred when attempting to write the header to a // log member that is being added to an existing group. // *Action: See accompanying errors. Fix problem or use another file. 00365, 00000, "the specified log is not the correct next log" // *Cause: The specified log failed to pass checks to ensure it corresponds // to the log that was just applied. This is probably the result // of using a log that was generated against a cold backup image // of the database. // *Action: Find the log that was generated by this copy of the database // and give that filename to recovery. 00366, 00000, "log %s of thread %s, checksum error in the file header" // *Cause: The file header for the redo log contains a checksum that does // not match the value calculated from the file header as read from // disk. This means the file header is corrupted // *Action: Find and install correct version of log or reset logs. 00367, 00000, "checksum error in log file header" // *Cause: The file header for the redo log contains a checksum that does // not match the value calculated from the file header as read from // disk. This means the file header is corrupted // *Action: Find the correct file and try again. 00368, 00000, "checksum error in redo log block" // *Cause: The redo block indicated by the accompanying error, is not // vaild. It has a checksum that does not match the block contents. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. If this happens when archiving, // archiving of the problem log can be skipped by clearing the log // with the UNARCHIVED option. This must be followed by a backup of // every datafile to insure recoverability of the database. // *Action: Restore correct file or reset logs. 00369, 00000, "Current log of thread %s not useable and other log being cleared" // *Cause: Attempt to open thread failed because it is necessary to switch // redo generation to another online log, but all the other logs are // being cleared or need to be archived before they can be used. // *Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then // wait for it to complete. Otherwise reissue the CLEAR command. If // there are other online logs for the thread, that are not being // cleared, then archive the logs. / / 370-389 kcb external errors / 00370, 00000, "potential deadlock during kcbchange operation" // *Cause: Error code used internally by software. Should never be reported // *Action: Treat as internal error. See error 600. 00371, 00000, "not enough shared pool memory, should be atleast %s bytes" // *Cause: Init.ora parameter shared_pool_size is too small // *Action: Increase the parameter value 00372, 00000, "file %s cannot be modified at this time" // *Cause: attempting to modify the contents of a file that cannot be // modified. The file is most likely part of a read only tablespace // but may be in the process of going offline, or the database may // be in the process of closing. // *Action: check the status of the file and its tablespace 00373, 00000, "online log version %s incompatible with ORACLE version %s" // *Cause: The online log was written by incompatible version of Oracle. // Can occur when the log file was created by either a new or // older version of Oracle. // *Action: Recover the database with the compatible software, shut it // down cleanly, then restart with current software. 00374, 00000, "parameter db_block_size = %s invalid ; must be a multiple of %s in the range [%s..%s]" // *Cause: invalid value for db_block_size parameter // *Action: adjust parameter and restart 00375, 00000, "Cannot allocate buffer cache state object" // *Document: NO // *Cause: No state obeject elements on freelist // *Action: None. 00376, 00000, "file %s cannot be read at this time" // *Cause: attempting to read from a file that is not readable. Most likely // the file is offline. // *Action: Check the state of the file. Bring it online 00377, 00000, "Frequent backups of file %s causing write operation to stall" // *Cause: Backups are occurring too frequently on this file. Each time a new // backup is started for a file, any writes which have been previously // issued (but not completed) have to be re-issued. If hot backups // are started very, very frequently, it is possible that some writes // will be re-issued repeatedly and never complete. // *Action: Increase the interval between begin hot-backup commands for this // file. // 00378, 00000, "buffer pools cannot be created as specified" // *Cause: Either the number of buffers or the number of lru latches is // too small to satisfy the specified buffer pool configuration. // *Action: Either increase the number of buffers and/or number of lru latches // or configure smaller buffer pools. // 00379, 00000, "no free buffers available in buffer pool %s for block size %sK" // *Cause: All buffers in the specified buffer pool for the specified block size // are in use and no free buffers are available. // *Action: Increase the number of buffers in the specified pool for the specified // block size // 00380, 00000, "cannot specify db_%sk_cache_size since %sK is the standard block size" // *Cause: User specified the parameter db_nk_cache_size (where n is one of // 2,4,8,16,32), while the standard block size for this database is // equal to n Kbytes. This is illegal. // *Action: Specify the standard block size cache using db_cache_size (DEFAULT // pool) (and db_recycle_cache_size, db_keep_cache_size if additional // buffer pools are required). Do NOT use the corresponding // db_nk_cache_size parameter for the standard block size. // 00381, 00000, "cannot use both new and old parameters for buffer cache size specification" // *Cause: User specified one or more of { db_cache_size , // db_recycle_cache_size, db_keep_cache_size, // db_nk_cache_size (where n is one of 2,4,8,16,32), // db_cache_advice } AND one or more of { db_block_buffers, // buffer_pool_keep , buffer_pool_recycle }. This is illegal. // *Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new // ones. Don't specify both. If old size parameters are specified in // the parameter file, you may want to replace them with new parameters // since the new parameters can be modified dynamically and allow // you to configure additional caches for additional block sizes. // Cache advisory can only be enabled with the new cache parameters. // 00382, 00000, "%s not a valid block size, valid range [%s..%s]" // *Cause: User specified a value for db_nk_cache_size where n is one of // {2, 4, 8, 16, 32}, but nk is not a valid block size for this // platform. // *Action: Remove corresponding parameter from the "init.ora" file and // restart the instance. 00383, 00000, "DEFAULT cache for blocksize %s cannot be reduced to zero" // *Cause: User attempted to reduce db_cache_size to zero, or attempted to // to reduce db_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. 00385, 00000, "cannot enable Very Large Memory with new buffer cache parameters" // *Cause: User specified one or more of { db_cache_size , // db_recycle_cache_size, db_keep_cache_size, // db_nk_cache_size (where n is one of 2,4,8,16,32) } // AND use_indirect_data_buffers is set to TRUE. This is illegal. // *Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2) // parameters. 00386, 00000, "use_indirect_data_buffers not supported" // *Cause: The system could not allocate sufficient memory to grow the // cache to the specified size. // *Action: Attempt a smaller increase in the value of the parameter. 00387, 00000, "version of the block on disk may be stale" // *Document: NO // *Cause: Error code used internally by software. Used during flashback // before image logging to to indicate that on-disk version of the // block may be stale. This error is not expected to be user visible. // *Action: None. // // / / 390-399: more Redo log errors / 00390, 00000, "log %s of thread %s is being cleared, cannot become current log" // *Cause: An attempt to switch to a new online log for the redo thread // failed because no reusable log could be found. This log is being // cleared and will be useable when the clearing completes. The // command that began the clearing may have terminated without // completing the clearing. // *Action: If the clear command is still executing then wait for its // completion. If it terminated then reissue the clear command, or // drop the log. 00391, 00000, "All threads must switch to new log format at the same time" // *Cause: An attempt to switch the current log of a single thread is not // allowed because the compatiblity requirements force a new log // format version number. When changing log formats, all threads // must switch to the new format at the same time. // *Action: Open the database to cause the coordinated log switch. If that // is not possible then return to the same software version and // compatibility setting last used to open the database. 00392, 00000, "log %s of thread %s is being cleared, operation not allowed" // *Cause: An operation encountered this online log in the middle of being // cleared. The command that began the clearing may have terminated // without completing the clearing. // *Action: If the clear command is still executing then wait for its // completion. If it terminated then reissue the clear command, or // drop the log. 00393, 00000, "log %s of thread %s is needed for recovery of offline datafiles" // *Cause: Log cannot be cleared because the redo in it is needed to recover // offline datafiles. It has not been archived so there is no // other copy available. If the log is cleared the tablespaces // containing the files will have to be dropped. // *Action: Archive the log then repeat the clear command. If archiving is not // possible, and dropping the tablespaces is acceptible, then add the // clause UNRECOVERABLE DATAFILE at the end of the clear command. 00394, 00000, "online log reused while attempting to archive it" // *Cause: It has been detected that an online log that is being archived // has been reused // *Action: Cannot archive the logfile anymore since it has been overwritten 00395, 00000, "online logs for the clone database must be renamed" // *Cause: A clone database open forces logfile renaming to avoid // overwriting the primary logfiles // *Action Rename the logfiles manually or using the log_file_name_convert // initialization parameter 00396, 00000, "error %s required fallback to single-pass recovery" // *Cause: The indicated error caused two-pass instance or // crash recovery to fail. Recovery was retried with an // alternate (slower) method to avoid the error. // *Action Correct the cause of the indicated error (also recorded) // so that future instance or crash recovery can succeed with the // two-pass algorithm. This usually requires making more main // memory available to the recovery process. 00397, 00000, "instance recovery process terminated with error" // *Cause: The foreground process doing instance recovery died. // *Action: Check the foreground trace file for the cause of recovery failure. 00398, 00000, "abort thread recovery due to reconfiguration" // *Cause: Global enqueue service reconfiguration occurred during // instance/crash recovery. // *Action: This is used internally, no action is required. 00399, 0000, "corrupt change description in redo log" // *Cause: A change vector in the redo log failed validation checks. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. / / 400-420: KCK errors / 00400, 00000, "invalid release value %s for parameter %s" // *Cause: The release level given for the specified init parameter is // invalid. // *Action: Correct the parameter value in the parameter file and retry. 00401, 00000, "the value for parameter %s is not supported by this release" // *Cause: The value specified cannot be supported by this release of // the software. // *Action: Choose an appropriate value, or remove the parameter value to // use the default value. 00402, 00000, "database changes by release %s cannot be used by release %s" // *Cause: Changes have been made to the database that require a newer // software release or that violate the compatibility parameters. // *Action: Use a version of the software that can understand the changes or // relax the compatibility requirements in the init file. 00403, 00000, "%s (%s) is not the same as other instances (%s)" // *Cause: Another instance has set the compatible or compatible no // recovery parameters differently than this instance. // *Action: Change the parameters of the current instance to match other // instances already running. 00404, 00000, "Convert file not found: '%s'" // *Cause: The file used for converting the database from V7 to V8 could // not be found. // *Action: Verify that the migration process has been started on this // database and that the convert filename is accessable. 00405, 00000, "compatibility type \"%s\"" // *Cause: Reporting a type associated with another error. // *Action: See accompanying error 00406, 00000, "COMPATIBLE parameter needs to be %s or greater" // *Cause: The COMPATIBLE initialization parameter is not high // enough to allow the operation. Allowing the command would make // the database incompatible with the release specified by the // current COMPATIBLE parameter. // *Action: Shutdown and startup with a higher compatibility setting. 00407, 00000, "rolling upgrade from release %s.%s to %s.%s is not allowed" // *Cause: Another instance executing software at a different point release // already has the database mounted. // *Action: Shutdown all instances then startup with the new software. 00408, 00000, "parameter %s is set to TRUE" // *Cause: Reporting the parameter that resulted in the compatibility error. // *Action: Shutdown and startup with a higher compatibility setting. 00409, 00000, "COMPATIBLE needs to be %s or higher to use AUTO SEGMENT SPACE MANAGEMENT" // *Cause: This is due to migrating from an older release of Oracle with // tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. // To open the database, the COMPATIBLE parameter needs to // be set to the specified value. // *Action: Shutdown and startup with the specified compatibility setting. / / 436-439: Oracle licensing ercs / 00436, 00000, "ORACLE is not licensed. Contact Oracle Corp. for assistance" // *Cause: // *Action: 00437, 00000, "ORACLE feature is not licensed. Contact Oracle Corp. for assistance" // *Cause: ORACLE feature is not licensed. // *Action: Contact ORACLE for assistance. 00438, 00000, "%s Option not installed" // *Cause: The specified option is not installed. // *Action: Purchase and install the option. 00439, 00000, "feature not enabled: %s" // *Cause: The specified feature is not enabled. // *Action: Do not attempt to use this feature. / / 440-460 Detached process startup errors / 00443, 00000, "background process \"%s\" did not start" // *Cause: The specified process did not start. // *Action: Ensure that the executable image is in the correct place with // the correct protections, and that there is enough memory. 00444, 00000, "background process \"%s\" failed while starting" // *Cause: Usually due to a bad (or non-existent) background process image. // *Action: Get a good background process image. 00445, 00000, "background process \"%s\" did not start after %s seconds" // *Cause: The specified process did not start after the specified time. // *Action: Ensure that the background did not die and leave a trace file. 00446, 00000, "background process started when not expected" // *Cause: The background process specified started up AFTER the RDBMS was // already running. // *Action: If nobody at your site started the process, then this is an // internal error. 00447, 00000, "fatal error in background process" // *Cause: One of the background processes died unexpectedly. // *Action: Warm start the system. 00448, 00000, "normal completion of background process" // *Cause: One of the background processes completed normally (i.e. exited). // The background process thinks that somebody asked it to exit. // *Action: Warm start the system. 00449, 00000, "background process '%s' unexpectedly terminated with error %s" // *Cause: A foreground process needing service from a background // process has discovered the process died. // *Action: Consult the error code, and the trace file for the process. 00450, 00000, "background process '%s' did not start" // *Cause: The specified process did not start. // *Action: Consult the error code, and the trace file for the process. 00451, 00000, "foreground process died unexpectedly" // *Cause: The foreground process for the new connection did not start. // *Action: Reconnect to Oracle. 00452, 00000, "foreground process unexpectedly terminated with error %s" // *Cause: The foreground process for the new connection did not start. // *Action: Reconnect to Oracle. 00453, 00000, "backgroud process '%s' is dead" // *Cause: The background process that was being messaged was dead // or its incarnation was invalid. // *Action: Restart the background process. / / 469-486 Detached process death errors (signaled in foreground) / 00469, 00000, "CKPT process terminated with error" // *Cause: The checkpoint process died // *Action: Warm start instance 00470, 00000, "LGWR process terminated with error" // *Cause: The log writer process died // *Action: Warm start instance 00471, 00000, "DBWR process terminated with error" // *Cause: The database writer process died // *Action: Warm start instance 00472, 00000, "PMON process terminated with error" // *Cause: The process cleanup process died // *Action: Warm start instance 00473, 00000, "ARCH process terminated with error" // *Cause: The archive process died // *Action: Warm start instance 00474, 00000, "SMON process terminated with error" // *Cause: The system cleanup process died // *Action: Warm start instance 00475, 00000, "TRWR process terminated with error" // *Cause: The system tracing process died // *Action: Warm start instance 00476, 00000, "RECO process terminated with error" // *Cause: The distributed transaction (two-phase commit) recovery process // died. // *Action: Warm start instance 00477, 00000, "SNP* process terminated with error" // *Cause: A materialized view refresh process died // *Action: PMON will restart SNP process shortly. If SNP process does not // get started, contact Oracle support. 00478, 00000, "SMON process terminated due to error %s" // *Cause: SMON was unable to service the requests due to error in // cleanup of resources // *Action: Warm start instance 00479, 00000, "RVWR process terminated with error %s" // *Cause: The RVWR process died // *Action: Warm start instance 00480, 00000, "LCK* process terminated with error" // *Cause: A system lock process died // *Action: Warm start instance 00481, 00000, "LMON process terminated with error" // *Cause: The global enqueue service monitor process died // *Action: Warm start instance 00482, 00000, "LMD* process terminated with error" // *Cause: A global enqueue service daemon process died // *Action: Warm start instance 00483, 00000, "During shutdown a process abnormally terminated" // *Cause: One of the background processes did not exit normally at or near // the time of shutdown. // *Action: Use shutdown abort. 00484, 00000, "LMS* process terminated with error" // *Cause: A global cache service process died // *Action: Warm start instance 00485, 00000, "DIAG process terminated with error %s" // *Cause: A global diagnostic process died // *Action: Wait for process to restart 00486, 00000, "ASMB process terminated with error" // *Cause: An ASM background process died. // *Action: Warm start instance. Also check that ASM Instance is running. 00487, 00000, "CTWR process terminated with error" // *Cause: The change tracking process died // *Action: Warm start instance 00488, 00000, "RBAL process terminated with error" // *Cause: The ASM rebalance coordinator process died. // *Action: Warm start instance. 00489, 00000, "ARB* process terminated with error" // *Cause: An ASM rebalance worker process died. // *Action: Wait for process to restart. 00490, 00000, "PSP process terminated with error" // *Cause: The process spawner died // *Action: Warm start instance 00491, 00000, "RMS0 process terminated with error" // *Cause: The RAC Management Process died 00492, 00000, "GTX* process terminated with error" // *Cause: A global transaction background process died. // *Action: Warm start instance 00493, 00000, "GMON process terminated with error" // *Cause: The ASM disk group monitor process died // *Action: Warm start instance 00494, 00000, "enqueue %s held for too long (more than %s seconds) by 'inst %s, osid %s'" // *Cause: The specified process did not release the enqueue within // the maximum allowed time. // *Action: Reissue any commands that failed and contact Oracle Support // Services with the incident information. 00495, 00000, "GEN0 process terminated with error" // *Cause: The generic background processing process died. // *Action: Warm start the instance. 00496, 00000, "LMHB process terminated with error" // *Cause: The LM heartbeat monitor process died. // *Action: Warm start the instance. 00497, 00000, "XDMG process terminated with error" // *Cause: The Cell automation manager process terminated with error. // *Action: PMON will restart XDMG process shortly. If XDMG process does not // restart, contact Oracle Support Services. 00498, 00000, "XDWK process terminated with error" // *Cause: The Cell automation worker actions process terminated with error. // *Action: PMON will restart XDWK process shortly. If XDWK process does not // restart, contact Oracle Support Services. 00499, 00000, "XDMG repeatedly failed to initialize terminating the instance." // *Cause: The Cell automation manager process repeatedly failed to // initialize. // *Action: Examine the alert log for the reason prior attempts to start // XDMG failed. If it is due to user error or bad configuration, // fix it and restart the instance. Otherwise, contact Oracle // Support Services. / / 00500-00565 / 00566, 00000, "cannot request processor group - NUMA not enabled" // *Cause: Cannot start process in a requested processor group when // the NUMA feature is disabled. // *Action: Start the process without requesting a NUMA processor group. / 00567, 00000, "Requested processor group %s is too large (maximum %s)" // *Cause: The process could not be started in the requested processor group. // *Action: Start the process in another processor group. / 00568, 00000, "Maximum number of interrupt handlers exceeded" // *Cause: User specified too many ^c handlers // *Action: Remove some old handlers. / 00569, 00000, "Failed to acquire global enqueue." // *Cause: A prior error occurred on one of the instances in the cluster. // Typically errors are caused by shared pool resource contention. // *Action: Check for and resolve prior errors on all instances in the cluster. // If there is shared pool resource contention, increase the // SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, // CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization // parameters. / / 00570-00599 SQL*Connect Opening & Reading Files / 00574, 00000, "osndnt: $CANCEL failure (break)" // *Cause: // *Action: 00575, 00000, "osndnt: $QIO failure (send out-of-band break)" // *Cause: // *Action: 00576, 00000, "in-band break protocol error" // *Cause: // *Action: 00577, 00000, "out-of-band break protocol error" // *Cause: // *Action: 00578, 00000, "reset protocol error" // *Cause: // *Action: 00579, 00000, "osndnt: server received malformed connection request" // *Cause: // *Action: 00580, 00000, "protocol versions do not match" // *Cause: // *Action: 00581, 00000, "osndnt: cannot allocate context area" // *Cause: // *Action: 00582, 00000, "osndnt: cannot deallocate context area" // *Cause: // *Action: 00583, 00000, "osndnt: $TRNLOG failure" // *Cause: // *Action: 00584, 00000, "cannot close connection" // *Cause: // *Action: 00585, 00000, "host name has incorrect form" // *Cause: // *Action: 00586, 00000, "osndnt: LIB$ASN_WTH_MBX failure" // *Cause: // *Action: 00587, 00000, "cannot connect to remote host" // *Cause: // *Action: 00588, 00000, "message from host was too short" // *Cause: // *Action: 00589, 00000, "message from host had incorrect data length" // *Cause: // *Action: 00590, 00000, "message from host had incorrect message type" // *Cause: // *Action: 00591, 00000, "incorrect number of bytes written" // *Cause: // *Action: 00592, 00000, "osndnt: $QIO failure (mailbox queue)" // *Cause: // *Action: 00593, 00000, "osndnt: $DASSGN failure (network device)" // *Cause: // *Action: 00594, 00000, "osndnt: $DASSGN failure (mailbox)" // *Cause: // *Action: 00595, 00000, "osndnt: $QIO failure (receive)" // *Cause: // *Action: 00596, 00000, "osndnt: $QIO failure (send)" // *Cause: // *Action: 00597, 00000, "osndnt: $QIO failure (mailbox requeue)" // *Cause: // *Action: 00598, 00000, "osndnt: $QIO failure (mailbox read)" // *Cause: // *Action: 00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" // *Cause: This is the generic internal error number for Oracle program // exceptions. It indicates that a process has encountered a low-level, // unexpected condition. The first argument is the internal message // number. This argument and the database version number are critical in // identifying the root cause and the potential impact to your system. // // *Action: Visit My Oracle Support to access the ORA-00600 Lookup tool // (reference Note 600.1) for more information regarding the specific // ORA-00600 error encountered. // // An Incident has been created for this error in the Automatic // Diagnostic Repository (ADR). When logging a service request, use // the Incident Packaging Service (IPS) from the Support Workbench // or the ADR Command Interpreter (ADRCI) to automatically package the // relevant trace information (reference My Oracle Support Note 411.1). // // The following information should also be gathered to help determine // the root cause: // - changes leading up to the error // - events or unusual circumstances leading up to the error // - operations attempted prior to the error // - conditions of the operating system and databases at the time // of the error // // Note: The cause of this message may manifest itself as different // errors at different times. Be aware of the history of errors that // occurred before this internal error. 00601, 00000, "cleanup lock conflict" // *Cause: PMON process runs into lock conflict trying to recovery processes // *Action: This is trapped internally, no action necessary 00602, 00000, "internal programming exception" // *Cause: Internal programming exception // *Action: Report as bug / Caution: following error code not relocatable 00603, 00000, "ORACLE server session terminated by fatal error" // *Cause: An ORACLE server session was in an unrecoverable state. // *Action: Login to ORACLE again so a new server session will be created / automatically. Examine the session trace file for more / information. 00604, 00000, "error occurred at recursive SQL level %s" // *Cause: An error occurred while processing a recursive SQL statement // (a statement applying to internal dictionary tables). // *Action: If the situation described in the next error on the stack // can be corrected, do so; otherwise contact Oracle Support. / /0605 reserved for v2 compatibility / 00606, 00000, "Internal error code" // *Cause: A call to deferred upi functions was made in non deferred mode // *Action: Report as a bug. 00607, 00000, "Internal error occurred while making a change to a data block" // *Cause: An internal error or memory exception occurred while Oracle was // applying redo to a data block. // *Action: call Oracle Support 00608, 00000, "testing error [%s] [%s] [%s] [%s] [%s]" // *Cause: Internal error reserved for testing. // *Action: call Oracle Support 00609, 00000, "could not attach to incoming connection" // *Cause: Oracle process could not answer incoming connection // *Action: If the situation described in the next error on the stack // can be corrected, do so; otherwise contact Oracle Support. 00610, 00000, "Internal error code" // *Cause: Oracle process started too late // *Action: This error should never be seen by the customer. Contact // Oraclce Support 00700, 00000, "soft internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" // *Cause: Internal inconsistency that will not crash a process // *Action: Report as a bug - the first argument is the internal error. 00701, 00000, "object necessary for warmstarting database cannot be altered" // *Cause: Attempt to alter or drop a database object (table, cluster, or // index) which are needed for warmstarting the database. // *Action: None. 00702, 00000, "bootstrap verison '%s' inconsistent with version '%s'" // *Cause: The reading version of the boostrap is incompatible with // the current bootstrap version. // *Action: Restore a version of the software that is compatible with this // bootstrap version. 00703, 00000, "maximum number of row cache instance locks exceeded" // *Cause: There are not enough row cache enqueues. // *Action: Increase the row cache enqueue parameter and warm start the system. 00704, 00000, "bootstrap process failure" // *Cause: Failure in processing bootstrap data - see accompanying error. // *Action: Contact your customer support representative. 00705, 00000, "inconsistent state during start up; shut down the instance, then restart it" // *Cause: A previous attempt to start an instance was terminated. // *Action: Shut down the instance completely, then restart it. 00706, 00000, "error changing format of file '%s'" // *Cause: An attempt to change the block0 format of the specified file // failed because the file is read-only or offline. // *Action: Make the file read-write or bring the file online and set // the BLK0_FMTCHG event. / / 00710 - 00719 reserved for tablespace rename feature / 00710, 00000, "new tablespace name is the same as the old tablespace name" // *Cause: An attempt to rename a tablespace failed because the new // name is the same as the old name. // *Action: No action required. 00711, 00000, "new tablespace name is invalid" // *Cause: An attempt to rename a tablespace failed because the new name // is invalid. // *Action: Choose a valid new name and retry the command. 00712, 00000, "cannot rename system tablespace" // *Cause: An attempt to rename the system tablespace failed. // *Action: No action required. / / event 720 - 739 is reserved for compatibility issues / 00720, 00000, "ALTER DATABASE RESET COMPATIBILITY command has been de-supported" // *Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported // since Oracle 10i. // *Action: No action required. 00721, 00000, "changes by release %s cannot be used by release %s" // *Cause: An attempt to import a tablespace failed because the tablespace // contains changes that require a newer software release or that // violate the compatibility parameters. // *Action: Use a version of the software that can understand the changes or // relax the compatibility requirements in the initialization // parameter file. 00722, 00000, "Feature \"%s\"" // *Cause: Reporting name of the feature for details of another error. // *Action: See associated error message. 00723, 00000, "Initialization parameter COMPATIBLE must be explicitly set" // *Cause: Oracle detected that the initialization parameter COMPATIBLE was // not explicitly specified, and the compatibility of the database is // lower than the default value of the COMPATIBLE parameter. In order // to use the new compatible setting, the intialization parameter // must be explicitly set by the user. // *Action: Explicitly set the value of COMPATIBLE parameter either in PFILE // or SPFILE, whichever is used. 00724, 00000, "ALTER DATABASE CONVERT command has been de-supported" // *Cause: ALTER DATABASE CONVERT command has been de-supported since // Oracle 10i. // *Action: No action required. 00725, 00000, "Desupported ALTER DATABASE SET STANDBY clause specified: %s" // *Cause: A deprecated ALTER DATABASE SET STANDBY was specified. // *Action: No action required. / / event 740 - 741 is reserved for file size overflow issues / 00740, 00000, "datafile size of (%s) blocks exceeds maximum file size" // *Cause: The user specified datafile size exceeded maximum file size. // *Action: Please check REFERENCE for maximum size. Reduce the size and retry. 00741, 00000, "logfile size of (%s) blocks exceeds maximum logfile size" // *Cause: The user specified logfile size exceeded maximum logfile size. // *Action: Please check REFERENCE for maximum size. Reduce the size and retry. / / event 742 - 815 is reserved for recovery issues / 00750, 00000, "database has been previously mounted and dismounted" // *Cause: The instance has already mounted and dismounted the database, // which is only allowed once in its lifetime. // *Action: Shut down the database. 00751, 00000, "could not obtain resilvering status for file" // *Cause: An error occurred while obtaining the mirror resilvering status // of a file. // *Action: Refer to other error messages shown for additional details of // the problem. 00752, 00000, "recovery detected a lost write of a data block" // *Cause: A write of a data block to storage was lost during // normal database operation on the primary database. // *Action: Shutdown the primary database and activate the physical standby // database to failover. See the Data Guard Concepts and Administration // guide for details. 00816, 00000, "error message translation failed" // *Cause: // *Action: / / event 820-850 reserved for sga auto management issues 00820, 00000, "Specified value of sga_max_size is too small, needs to be at least %sM" // *Cause: The specified value of sga_max_size is too small for the SGA to // accommodate all of the necessary SGA components such as the // log buffer, buffer pools, shared pool, etc. // *Action: Set sga_max_size to the recommended value or reduce the values // of any SGA component size parameters you have specified. 00821, 00000, "Specified value of sga_target %sM is too small, needs to be at least %sM" // *Cause: The specified value of sga_target is too small for the SGA to // accommodate all of the necessary SGA components such as the // log buffer, buffer pools, shared pool, etc. // *Action: Set sga_target to the recommended value or reduce the values // of any SGA component size parameters you have specified. 00822, 00000, "MMAN process terminated with error" // *Cause: The Memory Management process died. // *Action: Warm start instance 00823, 00000, "Specified value of sga_target greater than sga_max_size" // *Cause: The specified value of sga_target is greater than sga_max_size. // *Action: Increase sga_max_size to match up with sga_target or decrease // sga_target to match up with sga_maxsize. 00824, 00000, "cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings" // *Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter settings. // *Action: Check the other error messages for additional information. 00825, 00000, "cannot set DB_BLOCK_BUFFERS if SGA_TARGET or MEMORY_TARGET is set" // *Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set. // *Action: Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters, // and do not use DB_BLOCK_BUFFERS which is an old cache parameter. 00826, 00000, "cannot set SGA_TARGET or MEMORY_TARGET for an ASM instance" // *Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance. // *Action: Do not set SGA_TARGET or MEMORY_TARGET. 00827, 00000, "could not shrink sga_target to specified value" // *Cause: Attempted to shrink the SGA to the specified value but did not // succeed because the SGA components could not be shrunk as they // were already at their minimum sizes. // *Action: Do not set sga_target to a value below the current value without // first shrinking the individual SGA components. 00828, 00000, "specified value of shared_pool_reserved_size inconsistent with internal settings" // *Cause: Unable to set shared_pool_reserved_size to specified value if // SGA_TARGET set, either because the specified value is too // small, or because it is too large for the current internal // size of shared pool. More details can be found in the alert log. // *Action: If possible, do not set shared_pool_reserved_size without setting // shared_pool_size if SGA_TARGET set. Examine the alert log for // information about current internal size of shared pool, and valid // range of values for shared_pool_reserved_size. 00829, 00000, "event to stress test self tuning SGA feature by forcing partial granules transfers" // *Document: NO // *Cause: // *Action: 00830, 00000, "cannot set statistics_level to BASIC with auto-tune SGA enabled" // *Cause: The user attempted to set statistics_level to BASIC with auto-tune // SGA enabled which cannot be done because auto-tune SGA cannot work // with statistics_level set to BASIC. // *Action: Disable auto-tune SGA and try setting the statistics_level to // BASIC again. 00831, 00000, "event to stress test self tuning SGA feature by doing random memory broker resizes" // *Document: NO // *Cause: // *Action: 00832, 00000, "no streams pool created and cannot automatically create one" // *Cause: A database feature which needs STREAMS SGA was being used, however, // the streams_pool_size parameter was not defined and the value of // db_cache_size was too small to permit an automatic transfer of SGA // to the streams pool from the buffer cache. // *Action: Please set the parameter streams_pool_size or set SGA_TARGET. 00833, 00000, "event to test cancellation and cache protection by pinning buffers for deferred mode requests" // *Document: NO // *Cause: // *Action: 00834, 00000, "Simulate 4031 during an immediate mode request in auto-sga" // *Document: NO // *Cause: // *Action: Set _memory_management_tracing=23 to track this event. 00835, 00000, "Simulate memory broker disabling for code coverage" // *Document: NO // *Cause: // *Action: It will be reenabled on next SGA_TARGET resize 00836, 00000, "Simulate memory transfer from system memory for startup request" // *Document: NO // *Cause: For code coverage. // *Action: None. 00837, 00000, "Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET" // *Cause: The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET. // *Action: Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET. 00838, 00000, "Specified value of MEMORY_TARGET is too small, needs to be at least %sM" // *Cause: The specified value of MEMORY_TARGET was less than the sum of the // specified values for SGA_TARGET and PGA_AGGREGATE_TARGET. // *Action: Set MEMORY_TARGET to at least the recommended value. 00839, 00000, "SGA_TARGET cannot be modified to the specified value" // *Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET. // *Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low. 00840, 00000, "PGA_AGGREGATE_TARGET cannot be modified to the specified value" // *Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET. // *Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET. 00841, 00000, "MEMORY_TARGET not supported on this system" // *Cause: MEMORY_TARGET parameter was not supported on this system as // shmfs was disabled. // *Action: Refer to documentation for a list of supported systems. 00842, 00000, "DB_BLOCK_BUFFERS cannot be set with SGA_TARGET or MEMORY_TARGET" // *Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and MEMORY_TARGET. // *Action: Remove the incompatible parameter setting. 00843, 00000, "Parameter not taking MEMORY_MAX_TARGET into account" // *Cause: The parameter was larger than MEMORY_MAX_TARGET. // *Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_MAX_TARGET. 00844, 00000, "Parameter not taking MEMORY_TARGET into account" // *Cause: The parameter was larger than MEMORY_TARGET. // *Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_TARGET. 00845, 00000, "MEMORY_TARGET not supported on this system" // *Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux. // *Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system. 00846, 00000, "could not shrink MEMORY_TARGET to specified value" // *Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not // succeed because the PGA and SGA components could not be shrunk. // *Action: Do not set MEMORY_TARGET to a value below the current value without // first shrinking the individual memory components. 00847, 00000, "MEMORY_TARGET/MEMORY_MAX_TARGET and LOCK_SGA cannot be set together" // *Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set // *Action:Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA is set to TRUE. 00848, 00000, "STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET" // *Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY_TARGET. // *Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPICAL or ALL to use SGA_TARGET or MEMORY_TARGET. 00849, 00000, "SGA_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s." // *Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value. // *Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET. 00850, 00000, "PGA_AGGREGATE_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s." // *Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value. // *Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET. 00851, 00000, "SGA_MAX_SIZE %s cannot be set to more than MEMORY_TARGET %s." // *Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value. // *Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET. 00852, 00000, "Rolling migration monitor process terminated." // *Cause: The ASM rolling migration monitor process died. // *Action: Warm start the instance. / MODIFIED / smangala 03/28/11 - Backport 11679567: correct 1280 action / avaliani 04/09/10 - reuse ORA-01088 / sslim 02/16/10 - Add 1379 testing event / ineall 08/12/09 - Bug 8658899: Add ORA-1366: failed to find all redo / logs required for terminal apply / jjlee 03/03/09 - change 1110 and 1156 / yohu 11/20/08 - update 1086 / aamor 10/02/08 - bug 6793044: update 976 error / rlong 09/25/08 - / smangala 09/17/08 - bug7114186: fix PSBY terminal log handling / shsong 08/07/08 - / jgalanes 08/06/08 - Add 1362 and 1363 for invalid parameters to mine_value / & column_present / jjlee 07/15/08 - comment change / shsong 03/05/08 - Update 1188 / jgalanes 01/11/07 - Add 1357 & 1358 for LogMiner logs version < dictionary / version / gviswana 10/13/06 - Update Cause, Action for 980 / smangala 09/21/04 - update 1345 text and remove unused messages / jgalanes 09/14/06 - Add error # 1339 for LogMiner build error / abrown 05/10/06 - add KRVX_STATUS_UNSUPPORTED_DDL / abrown 06/08/05 - bug 3776830: unwind dictionary / mtao 03/25/05 - add 1375/1376, Reader detected redo log corruption / gmulagun 02/20/05 - bug 4140708 cannot audit SYS users / mjstewar 01/26/05 - Add 1148 / psuvarna 09/28/04 - #3909055: rectify error message ORA-01438 / jnesheiw 11/04/04 - Add global name mismatch error / abrown 08/04/04 - better error msg when supplemental logging off / jnesheiw 05/06/04 - revise 1341 / smangala 04/16/04 - add 1346: LogMiner missed a branch / jnesheiw 03/01/04 - fix tense in 1329 / lilin 01/21/04 - add 912 input too long / jwlee 11/16/03 - fix typo in ORA-1167 / abrown 08/26/03 - fix logmnr 9i specific actions / banand 02/27/03 - bug 2707377 / jkundu 12/06/02 - change log-based replication to Streams / sdizdar 10/28/02 - / molagapp 07/26/02 - recovery area project / rjanders 10/02/02 - Enhance 1154 cause/action / dvoss 10/07/02 - add 1355 and 1356 / rjenkins 07/31/02 - reuse 911 for alternative quotes / ajadams 05/30/02 - purge unused LogMiner messages / rjanders 05/24/02 - Fix ORA-1126 message. / mtao 06/04/02 - logminer message 1301 / ajadams 05/28/02 - LogMiner 10i status enhancements / mdilman 05/09/02 - DB begin/end backup: change 1140, 1232 and 1260 / molagapp 04/23/02 - change 1264, 1269 / bgarin 08/05/02 - Change text for logminer corrupt redo log / jkundu 01/23/02 - logminer error messages 1373, 1374 / jkundu 11/20/01 - adding logminer error message / abrown 10/23/01 - dbms_logmnr_d.set_tablespace needs real error msgs / tcondie 11/07/01 - grabtrans 'ycao_ora904' / ycao 11/05/01 - change ora-904 message / aime 10/09/01 - / ajadams 10/08/01 - logminer messages / asundqui 10/04/01 - bug 2029014: added 1279 / tcondie 10/18/01 - Modify ORA-932 to take 2 args. / mjstewar 08/28/01 - Add file name to ORA-1276 / qiwang 08/08/01 - more logmnr error msg / bsinha 08/02/01 - extend 1010 for autonomous txn / smangala 07/02/01 - add 1344. / ygu 06/18/01 - add more err msg for logminer / qiwang 06/04/01 - more logmnr error msgs / eyho 07/26/01 - remove obsoleted messages / mdilman 07/02/01 - bug 1815522: added 1277, 1278 / msusaira 06/14/01 - modify 1257 error mesg / mjstewar 04/04/01 - New OMF message. / jingliu 03/06/01 - fix error in message 1298, 1466 / eyho 03/06/01 - RAC name changes / dgprice 01/11/01 - bug 1394096 define buffer size limits error / yuli 01/18/01 - 1539879: change Cause and Action part of 1114 / amsrivas 12/12/00 - 1029386: modify 1153 - resetlogs/backup conflict. / mjstewar 12/13/00 - Automated standby file management / nlee 11/13/00 - Forward merge fix for bug 553250. / gkulkarn 10/30/00 - Add LogMiner Out-of-Memory Error / rpang 09/15/00 - Updated the cause of "unsupported character set" error / yuli 10/24/00 - Update message of 1092 / gkulkarn 08/01/00 - Reserve more error numbers for LogMiner / ajadams 07/07/00 - logminer dictionary message / aime 06/29/00 - Fix compile error / mjstewar 06/13/00 - OMF errors / ajadams 06/26/00 - even more Logminer errors / ajadams 06/21/00 - more LogMiner messages / jkundu 06/09/00 - adding Logminer trace event / apareek 04/14/00 - change 1162 text / gkulkarn 05/14/00 - Update Error #01312 / rjenkins 03/29/00 - change 1441 / ajadams 03/31/00 - add error code 1315 for logmnr / robermar 04/18/00 - Inspection Comments / apadmana 01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW / gkulkarn 02/01/00 - Add LogMiner sql function error messgaes / mjstewar 01/18/00 - Automatic removal of OS files. / robermar 01/27/00 - DB End Backout / msusaira 12/19/99 - add err 1257 / vsrihari 07/14/99 - add file locks error message / jkundu 07/06/99 - adding more LogMiner messages / nireland 04/14/99 - Imporove action text for ORA-1220. #863107 / swerthei 10/28/98 - noarchivelog -> NOARCHIVELOG in 1108 / swerthei 10/20/98 - modify 1108 for bug 719176 - online/backup conflict / vsrihari 08/29/98 - modifying file identify error message / fsanchez 08/19/98 - fix_kcv_mig / mcusson 05/29/98 - adding error message for LogMiner / swerthei 04/21/98 - messages for Oracle-managed hot-backup mode / / 900-999 parse errors - / carried over from V5 - desirable to add arguments wherever possible / 00900, 00000, "invalid SQL statement" // *Cause: // *Action: 00901, 00000, "invalid CREATE command" // *Cause: // *Action: 00902, 00000, "invalid datatype" // *Cause: // *Action: 00903, 00000, "invalid table name" // *Cause: // *Action: 00904, 00000, "%s: invalid identifier" // *Cause: // *Action: 00905, 00000, "missing keyword" // *Cause: // *Action: 00906, 00000, "missing left parenthesis" // *Cause: // *Action: 00907, 00000, "missing right parenthesis" // *Cause: // *Action: 00908, 00000, "missing NULL keyword" // *Cause: // *Action: 00909, 00000, "invalid number of arguments" // *Cause: // *Action: 00910, 00000, "specified length too long for its datatype" // *Cause: for datatypes CHAR and RAW, the length specified was > 2000; // otherwise, the length specified was > 4000. // *Action: use a shorter length or switch to a datatype permitting a // longer length such as a VARCHAR2, LONG CHAR, or LONG RAW 00911, 00000, "invalid character" // *Cause: identifiers may not start with any ASCII character other than // letters and numbers. $#_ are also allowed after the first // character. Identifiers enclosed by doublequotes may contain // any character other than a doublequote. Alternative quotes // (q'#...#') cannot use spaces, tabs, or carriage returns as // delimiters. For all other contexts, consult the SQL Language // Reference Manual. // *Action: 00912, 00000, "input parameter too long" // *Cause: one of your input strings was too long // *Action:shorten the input parameter length 00913, 00000, "too many values" // *Cause: // *Action: 00914, 00000, "missing ADD keyword" // *Cause: // *Action: 00915, 00000, "network access of dictionary table not currently allowed" // *Cause: // *Action: 00917, 00000, "missing comma" // *Cause: // *Action: 00918, 00000, "column ambiguously defined" // *Cause: // *Action: 00919, 00000, "invalid function" // *Cause: // *Action: 00920, 00000, "invalid relational operator" // *Cause: // *Action: 00921, 00000, "unexpected end of SQL command" // *Cause: // *Action: 00922, 00000, "missing or invalid option" // *Cause: // *Action: 00923, 00000, "FROM keyword not found where expected" // *Cause: // *Action: 00924, 00000, "missing BY keyword" // *Cause: // *Action: 00925, 00000, "missing INTO keyword" // *Cause: // *Action: 00926, 00000, "missing VALUES keyword" // *Cause: // *Action: 00927, 00000, "missing equal sign" // *Cause: // *Action: 00928, 00000, "missing SELECT keyword" // *Cause: // *Action: 00929, 00000, "missing period" // *Cause: // *Action: 00930, 00000, "missing asterisk" // *Cause: // *Action: 00931, 00000, "missing identifier" // *Cause: // *Action: 00932, 00000, "inconsistent datatypes: expected %s got %s" // *Cause: // *Action: 00933, 00000, "SQL command not properly ended" // *Cause: // *Action: 00934, 00000, "group function is not allowed here" // *Cause: // *Action: 00935, 00000, "group function is nested too deeply" // *Cause: // *Action: 00936, 00000, "missing expression" // *Cause: // *Action: 00937, 00000, "not a single-group group function" // *Cause: // *Action: 00938, 00000, "not enough arguments for function" // *Cause: // *Action: 00939, 00000, "too many arguments for function" // *Cause: // *Action: 00940, 00000, "invalid ALTER command" // *Cause: // *Action: 00941, 00000, "missing cluster name" // *Cause: // *Action: 00942, 00000, "table or view does not exist" // *Cause: // *Action: 00943, 00000, "cluster does not exist" // *Cause: // *Action: 00944, 00000, "insufficient number of clustered columns" // *Cause: // *Action: 00945, 00000, "specified clustered column does not exist" // *Cause: // *Action: 00946, 00000, "missing TO keyword" // *Cause: // *Action: 00947, 00000, "not enough values" // *Cause: // *Action: 00948, 00000, "ALTER CLUSTER statement no longer supported" // *Cause: // *Action: 00949, 00000, "illegal reference to remote database" // *Cause: // *Action: 00950, 00000, "invalid DROP option" // *Cause: // *Action: 00951, 00000, "cluster not empty" // *Cause: // *Action: 00952, 00000, "missing GROUP keyword" // *Cause: // *Action: 00953, 00000, "missing or invalid index name" // *Cause: An index name of the form [ . ] 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, "Specified pseudocolumn or operator not allowed here." // *Cause: LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or // CONNECT_BY_ISCYCLE was specified at an illegal location. // *Action: Remove LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or // CONNECT_BY_ISCYCLE. 00977, 00000, "duplicate auditing option" // *Cause: AUDIT or NOAUDIT statement specifies an option more than once // *Action: Either use ALL with no other auditing options or make sure // no option is listed more than once. 00978, 00000, "nested group function without GROUP BY" // *Cause: // *Action: 00979, 00000, "not a GROUP BY expression" // *Cause: // *Action: 00980, 00000, "synonym translation is no longer valid" // *Cause: A synonym did not translate to a legal target object. This // could happen for one of the following reasons: // 1. The target schema does not exist. // 2. The target object does not exist. // 3. The synonym specifies an incorrect database link. // 4. The synonym is not versioned but specifies a versioned // target object. // *Action: Change the synonym definition so that the synonym points at // a legal target object. 00981, 00000, "cannot mix table and system auditing options" // *Cause: Table and system-wide auditing options were specified in the // same AUDIT or NOAUDIT statement. // *Action: You must issue table and system options in separate // statements. 00982, 00000, "missing plus sign" // *Cause: // *Action: 00983, 00000, "cannot audit or noaudit SYS user actions" // *Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions. // *Action: Execute the statement again with a valid user. 00984, 00000, "column not allowed here" // *Cause: // *Action: 00985, 00000, "invalid program name" // *Cause: // *Action: 00986, 00000, "missing or invalid group name(s)" // *Cause: // *Action: 00987, 00000, "missing or invalid username(s)" // *Cause: // *Action: 00988, 00000, "missing or invalid password(s)" // *Cause: // *Action: 00989, 00000, "too many passwords for usernames given" // *Cause: // *Action: 00990, 00000, "missing or invalid privilege" // *Cause: // *Action: 00991, 00000, "only MAC privileges may be granted to procedures" // *Cause: Object privileges or non-MAC system privileges // were granted to the procedure. // *Action: Only grant MAC privileges using the PROCEDURE clause. 00992, 00000, "invalid format for REVOKE command" // *Cause: // *Action: 00993, 00000, "missing GRANT keyword" // *Cause: // *Action: 00994, 00000, "missing OPTION keyword" // *Cause: // *Action: 00995, 00000, "missing or invalid synonym identifier" // *Cause: // *Action: 00996, 00000, "the concatenate operator is ||, not |" // *Cause: // *Action: 00997, 00000, "illegal use of LONG datatype" // *Cause: // *Action: 00998, 00000, "must name this expression with a column alias" // *Cause: // *Action: 00999, 00000, "invalid view name" // *Cause: // *Action: / / parse errors continue at 1700 / / 1000-1099 program interface errors / 01000, 00000, "maximum open cursors exceeded" // *Cause: // *Action: 01001, 00000, "invalid cursor" // *Cause: // *Action: 01002, 00000, "fetch out of sequence" // *Cause: This error means that a fetch has been attempted from a cursor // which is no longer valid. Note that a PL/SQL cursor loop // implicitly does fetches, and thus may also cause this error. // There are a number of possible causes for this error, including: // 1) Fetching from a cursor after the last row has been retrieved // and the ORA-1403 error returned. // 2) If the cursor has been opened with the FOR UPDATE clause, // fetching after a COMMIT has been issued will return the error. // 3) Rebinding any placeholders in the SQL statement, then issuing // a fetch before reexecuting the statement. // *Action: 1) Do not issue a fetch statement after the last row has been // retrieved - there are no more rows to fetch. // 2) Do not issue a COMMIT inside a fetch loop for a cursor // that has been opened FOR UPDATE. // 3) Reexecute the statement after rebinding, then attempt to // fetch again. 01003, 00000, "no statement parsed" // *Cause: // *Action: 01004, 00000, "default username feature not supported; logon denied" // *Cause: // *Action: 01005, 00000, "null password given; logon denied" // *Cause: // *Action: 01006, 00000, "bind variable does not exist" // *Cause: // *Action: 01007, 00000, "variable not in select list" // *Cause: // *Action: 01008, 00000, "not all variables bound" // *Cause: // *Action: 01009, 00000, "missing mandatory parameter" // *Cause: // *Action: 01010, 00000, "invalid OCI operation" // *Cause: One of the following: // 1) You attempted an invalid OCI operation. // 2) You are using an Oracle client application linked with // version 7.1 (or higher) libraries, the environment variable // ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to // connect to a version 7.0 (or lower) Oracle Server. // 3) You are connected to a version 7.1 (or higher) Oracle Server, // the initialization parameter DBLINK_ENCRYPT_LOGIN is set to // TRUE, and you attempted to use a database link pointing to a // version 7.0 (or lower) Oracle Server. // 4) You are connected to a version 9.0.2(or higher) Oracle Server // and you attempted to use a database link pointing to a version // 9.0.1(or lower) Oracle Server for distributed autonomous // transaction. // *Action: For the above causes: // 1) Do not use the invalid OCI operation. // 2) If you do not wish to use encrypted connect passwords in your // distributed database, set ORA_ENCRYPT_LOGIN to FALSE. // If you wish to use encrypted connect passwords, you must upgrade // all Oracle Servers to version 7.1 (or higher). // 3) If you do not wish to use encrypted database links in your // distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. // If you wish to use encrypted database links, you must upgrade // all Oracle Servers to version 7.1 (or higher). // 4) Do not attempt distributed autonomous transaction on version // 9.0.1(or lower) Oracle Server. 01011, 00000, "Cannot use v7 compatibility mode when talking to v6 server" // *Cause: // *Action: Use v6 sql language type. You may need to use the // 'SET COMPATIBILITY V6' command 01012, 00000, "not logged on" // *Cause: // *Action: 01013, 00000, "user requested cancel of current operation" // *Cause: // *Action: 01014, 00000, "ORACLE shutdown in progress" // *Cause: // *Action: 01015, 00000, "logon called recursively" // *Cause: // *Action: 01016, 00000, "This function can be called only after a fetch" // *Cause: Cursor in an invalid state. // *Action: Make sure that the oci/upi function is called after fetch. 01017, 00000, "invalid username/password; logon denied" // *Cause: // *Action: 01018, 00000, "column does not have a LONG datatype" // *Cause: // *Action: 01019, 00000, "unable to allocate memory in the user side" // *Cause: The user side memory allocator returned error. // *Action: Increase the processes heap size or switch to the old set of calls. 01020, 00000, "unknown context state" // *Cause: // *Action: 01021, 00000, "invalid context size specified" // *Cause: // *Action: 01022, 00000, "database operation not supported in this configuration" // *Cause: The attempted database operation does not conform to the user // programming interface (UPI) for the two communicating // ORACLE servers. // *Action: You may need to upgrade one or more of your ORACLE servers or // re-link your user side application with new libraries. Report // the problem to Worldwide Customer Support. 01023, 00000, "Cursor context not found (Invalid cursor number)" // *Cause: The cursor number is not a valid open cursor. // *Action: Make sure that the cursor is open. 01024, 00000, "invalid datatype in OCI call" // *Cause: // *Action: 01025, 00000, "UPI parameter out of range" // *Cause: An integer parameter to a upi function is out of range. // *Action: This usually indicates an error in a tool built on top // of the oracle dbms. Report the error to your customer // support representative. 01026, 00000, "multiple buffers of size > 4000 in the bind list" // *Cause: More than one long buffer in the bind list. // *Action: Change the buffer size to be less than 4000 for the bind variable // bound to a normal column. 01027, 00000, "bind variables not allowed for data definition operations" // *Cause: An attempt was made to use a bind variable in a SQL data definition // operation. // *Action: Such bind variables are not allowed. 01028, 00000, "internal two task error" // *Cause: Received send long message but don't have the cursor context. // *Action: Report as a bug. 01029, 00000, "internal two task error" // *Cause: Received a request to send the long again when there is no long // *Action: Report as a bug 01030, 00000, "SELECT ... INTO variable does not exist" // *Cause: The SELECT... INTO specified in the bind call does not // correspond to a variable in the SQL statement. // *Action: If it is not possible to correct the statement, call customer // support. 01031, 00000, "insufficient privileges" // *Cause: An attempt was made to change the current username or password // without the appropriate privilege. This error also occurs if // attempting to install a database without the necessary operating // system privileges. // When Trusted Oracle is configure in DBMS MAC, this error may occur // if the user was granted the necessary privilege at a higher label // than the current login. // *Action: Ask the database administrator to perform the operation or grant // the required privileges. // For Trusted Oracle users getting this error although granted the // the appropriate privilege at a higher label, ask the database // administrator to regrant the privilege at the appropriate label. 01032, 00000, "no such userid" // *Cause: This is an internal error message related to Export/Import. // *Action: Contact customer support. 01033, 00000, "ORACLE initialization or shutdown in progress" // *Cause: An attempt was made to log on while Oracle is being started up // or shutdown. // *Action: Wait a few minutes. Then retry the operation. 01034, 00000, "ORACLE not available" // *Cause: Oracle was not started up. Possible causes include the following: // - The SGA requires more space than was allocated for it. // - The operating-system variable pointing to the instance is // improperly defined. // *Action: Refer to accompanying messages for possible causes and correct // the problem mentioned in the other messages. // If Oracle has been initialized, then on some operating systems, // verify that Oracle was linked correctly. See the platform // specific Oracle documentation. 01035, 00000, "ORACLE only available to users with RESTRICTED SESSION privilege" // *Cause: Logins are disallowed because an instance started in restricted // mode. Only users with RESTRICTED SESSION system privilege can // log on. // *Action: Request that Oracle be restarted without the restricted option or // obtain the RESTRICTED SESSION system privilege. 01036, 00000, "illegal variable name/number" // *Cause: Unable to find bind context on user side // *Action: Make sure that the variable being bound is in the sql statement. 01037, 00000, "maximum cursor memory exceeded" // *Cause: Attempting to process a complex sql statement which consumed all // available memory of the cursor. // *Action: Simplify the complex sql statement. 01038, 00000, "cannot write database file version %s with ORACLE version %s" // *Cause: Attempting to write datafile headers in an old format. The new // format can not be used until after the database has been verified // as being compatible with this software version. // *Action: Open the database to advance to the new file formats, then repeat // the operation. If the operation is required before the database // can be opened, then use the previous software release to do the // operation. 01039, 00000, "insufficient privileges on underlying objects of the view" // *Cause: Attempting to explain plan on other people's view without // the necessary privileges on the underlying objects of the view. // *Action: Get necessary privileges or do not perform the offending operation. 01040, 00000, "invalid character in password; logon denied" // *Cause: There are multibyte characters in the password or some characters // in the password are not in US7ASCII range. // *Action: Resubmit password with valid characters. 01041, 00000, "internal error. hostdef extension doesn't exist" // *Cause: Pointer to hstdef extension in hstdef is null. // *Action: Report as a bug 01042, 00000, "detaching a session with open cursors not allowed" // *Cause: An attempt was made to detach a seesio n which had open cursors. // *Action: Close all the cursors before detaching the session. 01043, 00000, "user side memory corruption [%s], [%s], [%s], [%s]" // *Cause: The application code corrupted some of the usr memory used by oracle // *Action: Make sure that the application code is not overwriting memory. 01044, 00000, "size %s of buffer bound to variable exceeds maximum %s" // *Cause: An attempt was made to bind a buffer whose total size would exceed // the maximum size allowed. Total array size for arrays is // calculated as: (element_size)*(number of elements) // *Action: Reduce buffer size. 01045, 00000, "user %s lacks CREATE SESSION privilege; logon denied" // *Cause: A connect was attempted to a userid which does not have // create session privilege. // *Action: Grant the user CREATE SESSION privilege. 01046, 00000, "cannot acquire space to extend context area" // *Cause: // *Action: 01047, 00000, "The above error occurred in schema=%s, package=%s, procedure=%s" // *Cause: // *Action: Informational message 01048, 0000, "Couldn't find the specified procedure in the given context" // *Cause: The procedure user specified in deferred RPC doesn't exist. // *Action: Check to make sure that the procedure exists and is visible to the // replication process. 01049, 00000, "Bind by name is not spupportted in streamed RPC" // *Cause: A newer version of server is talking with this version requesting an // operation not supported in this version. // *Action: 01050, 00000, "cannot acquire space to open context area" // *Cause: // *Action: 01051, 00000, "deferred rpc buffer format invalid" // *Cause: The deferred rpc data in sys.def$_call is corrupted. // *Action: Contact your customer support representive. 01052, 00000, "required destination LOG_ARCHIVE_DUPLEX_DEST is not specified" // *Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not // specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to // two. // *Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or // reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one. 01053, 00000, "user storage address cannot be read" // *Cause: // *Action: 01054, 00000, "user storage address cannot be written" // *Cause: // *Action: 01055, 00000, "Object datatypes not supported for bind or define in this mode" // *Cause: Bind or Define used for objects with an invalid mode // *Action: Change the mode. 01057, 00000, "invalid or ambiguous block.field reference in user exit" // *Cause: // *Action: 01058, 00000, "internal New Upi interface error" // *Cause: Attempt to delete non existant hstdef extension. // *Action: Report as a bug. 01059, 00000, "parse expected before a bind or execute" // *Cause: The client application attempted to bind a variable or execute // a cursor opened in a PL/SQL block before the statement was parsed. // *Action: Ensure the statement is parsed before a bind or execute. 01060, 00000, "array binds or executes not allowed" // *Cause: The client application attempted to bind an array of cursors or // attempted to repeatedly execute against a PL/SQL block with a bind // variable of type cursor. // *Action: Bind a single cursor or execute the PL/SQL block once. 01061, 00000, "cannot start up a V8 server using a V7 client application" // *Cause: You are using an Oracle client application linked with version 7 // (or lower) libraries and you attempted to start up a V8 (or // higher) server. // *Action: Use a client application linked with V8 (or higher) libraries.60 01062, 00000, "unable to allocate memory for define buffer" // *Cause: Exceeded the maximum buffer size for current plaform // *Action: Use piecewise fetch with a smaller buffer size / 1070 - 1099: V6 program interface errors 01070, 00000, "Using an old version of Oracle for the server" // *Cause: Using pre 7.0.10.1 version of oracle for server // *Action: Upgrade server to post 7.0.10.1 version 01071, 00000, "cannot perform operation without starting up ORACLE" // *Cause: Obvious // *Action: 01072, 00000, "cannot stop ORACLE; ORACLE not running" // *Cause: Obvious // *Action: 01073, 00000, "fatal connection error: unrecognized call type" // *Cause: An illegal internal operation was attempted. // *Action: Contact your customer support representative. 01074, 00000, "cannot shut down ORACLE; inside a login session - log off first" // *Cause: Obvious // *Action: 01075, 00000, "you are currently logged on" // *Cause: Attempt to login while logged in. // *Action: 01076, 00000, "multiple logons per process not yet supported" // *Cause: Obvious // *Action: 01077, 00000, "background process initialization failure" // *Cause: Failure during initialization of ORACLE background processes. // *Action: Further diagnostic information should be in the error stack // or in the trace file. 01078, 00000, "failure in processing system parameters" // *Cause: Failure during processing of INIT.ORA parameters during // system startup. // *Action: Further diagnostic information should be in the error stack. 01079, 00000, "ORACLE database was not properly created, operation aborted" // *Cause: There was an error when the database or control file was created. // *Action: Check what error was signaled when the database was first // created or when the control file was recreated. Take appropriate // actions to recreate the database or a new control file. 01080, 00000, "error in shutting down ORACLE" // *Cause: Failure during system shutdown. // *Action: Further diagnostic information should be in the error stack. 01081, 00000, "cannot start already-running ORACLE - shut it down first" // *Cause: Obvious // *Action: 01082, 00000, "'row_locking = always' requires the transaction processing option" // *Cause: "row_locking = always" is specified in INIT.ORA file. // This feature is not supported by ORACLE without the // transaction processing option. // *Action: Remove it from INIT.ORA file or set it to "default" or "intent". 01083, 00000, "value of parameter \"%s\" is inconsistent with that of other instances" // *Cause: The value of the given parameter is required to be the same for all // instances in the cluster database configuration. ROW_LOCKING and // SERIALIZABLE are 2 examples. // *Action: Change the value of the parameter in INIT.ORA file to match // that of other cluster database instances. 01084, 00000, "invalid argument in OCI call" // *Cause: The failing OCI call contains an argument with an invalid value. // *Action: Use valid argument values. For more information, see the // Programmer's Guide to the Oracle Call Interfaces and the // appropriate programming language supplement. 01085, 00000, "preceding errors in deferred rpc to \"%s.%s.%s\"" // *Cause: Errors were encountered when the named procedure was executed // as a deferred remoted procedure call. // *Action: Correct the cause of the preceding errors. 01086, 00000, "savepoint '%s' never established in this session or is invalid" // *Cause: An attempt was made to roll back to a savepoint that was never // established in this session, or was invalid. // *Action: Try rolling back to the savepoint from the session where it is established. 01087, 00000, "cannot start up ORACLE - currently logged on" // *Cause: // *Action: Logoff and then issue the STARTUP command. 01088, 00000, "shutdown in progress - operation not permitted until restart" // *Cause: The SHUTDOWN command was used to shut down a running Oracle // instance but the shutdown operation was not complete. // *Action: Wait for the instance to be restarted or contact your // database administrator. 01089, 00000, "immediate shutdown in progress - no operations are permitted" // *Cause: The SHUTDOWN IMMEDIATE command was used to shut down // a running ORACLE instance, so your operations have been // terminated. // *Action: Wait for the instance to be restarted, or contact your DBA. 01090, 00000, "shutdown in progress - connection is not permitted" // *Cause: The SHUTDOWN command was used to shut down a running // ORACLE instance, so you cannot connect to ORACLE. // *Action: Wait for the instance to be restarted, or contact your DBA. 01091, 00000, "failure during startup force" // *Cause: Unable to destroy the old SGA. // *Action: Manually remove the old SGA and reissue the STARTUP command 01092, 00000, "ORACLE instance terminated. Disconnection forced" // *Cause: The instance this process was connected to was terminated // abnormally, probably via a shutdown abort. This process // was forced to disconnect from the instance. // *Action: Examine the alert log for more details. When the instance has been // restarted, retry action. 01093, 00000, "ALTER DATABASE CLOSE only permitted with no sessions connected" // *Cause: There is at least one more session other than the current one // logged into the instance. ALTER DATABASE CLOSE is not permitted. // *Action: Find the other sessions and log them out and resubmit the command 01094, 00000, "ALTER DATABASE CLOSE in progress. Connections not permitted" // *Cause: // *Action: 01095, 00000, "DML statement processed zero rows" // *Cause: During a call to OTEX, an update, delete, or insert statement // being executed processed zero rows. The execution // of statements by OTEX was halted at this point. // *Action: 01096, 00000, "program version (%s) incompatible with instance (%s)" // MERGE: 1095 RENUMBERED TO 1096 // *Cause: A program is trying to connect to an instance using a different // version of code than the database was started with. This is // not allowed. // *Action: Either relink the program with the same version as the database or // restart the database using the old version of code. 01097, 00000, "cannot shutdown while in a transaction - commit or rollback first" // *Cause: Obvious // *Action: 01098, 00000, "program Interface error during Long Insert" // *Cause: // *Action: 01099, 00000, "cannot mount database in SHARED mode if started in single process mode" // *Cause: Obvious // *Action: / / 1100 to 1279: db file errors (continue at 63000) / 01100, 00000, "database already mounted" // *Cause: A database is already mounted in this instance. // *Action: 01101, 00000, "database being created currently mounted by some other instance" // *Cause: Some other instance has the database of same name currently mounted // and you are trying to create it. // *Action: Either change the database name or shutdown the other instance. 01102, 00000, "cannot mount database in EXCLUSIVE mode" // *Cause: Some other instance has the database mounted exclusive or shared. // *Action: Shutdown other instance or mount in a compatible mode. 01103, 00000, "database name '%s' in control file is not '%s'" // *Cause: The database name in the control file does not match your // database name. // *Action: Either find the correct control file or change your database name. 01104, 00000, "number of control files (%s) does not equal %s" // *Cause: The number of control files used by this instance disagrees with // the number of control files in an existing instance. // *Action: Check to make sure that all control files are listed. 01105, 00000, "mount is incompatible with mounts by other instances" // *Cause: An attempt to mount the database discovered that another instance // mounted a database by the same name, but the mount is not // compatible. Additional errors are reported explaining why. // *Action: See accompanying errors. 01106, 00000, "database must be closed before dismounting" // *Cause: Obvious // *Action: 01107, 00000, "database must be mounted for media recovery" // *Cause: An attempt to perform media recovery was made but the database is // not mounted. // *Action: Mount the database. 01108, 00000, "file %s is in backup or media recovery" // *Cause: Either media recovery is actively being applied to the file, or // it is being backed up while the database is in NOARCHIVELOG mode. // It cannot be used for normal database access or crash recovery. // *Action: Complete or cancel the media recovery session or backup. 01109, 00000, "database not open" // *Cause: A command was attempted that requires the database to be open. // *Action: Open the database and try the command again 01110, 00000, "data file %s: '%s'" // *Cause: Reporting file name for details of another error. The reported // name can be of the old file if a data file move operation is // in progress. // *Action: See associated error message. 01111, 00000, "name for data file %s is unknown - rename to correct file" // *Cause: The data file was missing from a CREATE CONTROLFILE command or // backup control file recovery was done with a control file that // was saved before the file was created. // *Action: Rename the MISSING file to the name of the real file. 01112, 00000, "media recovery not started" // *Cause: An attempt to continue media recovery is being made but media // recovery was not started. // *Action: None. 01113, 00000, "file %s needs media recovery" // *Cause: An attempt was made to online or open a database with a file that // is in need of media recovery. // *Action: First apply media recovery to the file. 01114, 00000, "IO error writing block to file %s (block # %s)" // *Cause: The device on which the file resides is probably offline. If the // file is a temporary file, then it is also possible that the device // has run out of space. This could happen because disk space of // temporary files is not necessarily allocated at file creation time. // *Action: Restore access to the device or remove unnecessary files to free // up space. 01115, 00000, "IO error reading block from file %s (block # %s)" // *Cause: Device on which the file resides is probably offline // *Action: Restore access to the device 01116, 00000, "error in opening database file %s" // *Cause: Usually the file is not accessible. // *Action: Restore the database file. 01117, 00000, "adding file '%s' with illegal block size: %s; limit is %s" // *Cause: An attempt was made to add a database file with a block size // that is greater than the maximum block size allowed. // *Action: Retry the DDL command with a smaller block size. 01118, 00000, "cannot add any more database files: limit of %s exceeded" // *Cause: There is no more room in the control file for adding database // files. // *Action: Resize the control file or drop other tablespaces. 01119, 00000, "error in creating database file '%s'" // *Cause: Usually due to not having enough space on the device. // *Action: 01120, 00000, "cannot remove online database file %s" // *Cause: Attempting to drop a datafile when it is online // *Action: Take file offline before dropping. 01121, 00000, "cannot rename database file %s - file is in use or recovery" // *Cause: Attempted to use ALTER DATABASE RENAME to rename a // datafile that is online in an open instance or is being recovered. // *Action: Close database in all instances and end all recovery sessions. 01122, 00000, "database file %s failed verification check" // *Cause: The information in this file is inconsistent with information // from the control file. See accompanying message for reason. // *Action: Make certain that the db files and control files are the correct // files for this database. 01123, 00000, "cannot start online backup; media recovery not enabled" // *Cause: An attempt to start backup of an on-line tablespace failed because // media recovery is not enabled. // *Action: Enable media recovery and retry this operation. 01124, 00000, "cannot recover data file %s - file is in use or recovery" // *Cause: An attempt to do media recovery found that the file was not // available for recovery. Either it is online and the database is // open in some instance, or another process is curently doing // media recovery on the file. // *Action: Do not do media recovery. 01125, 00000, "cannot disable media recovery - file %s has online backup set" // *Cause: An attempt to disable media recovery found that an online backup is // still in progress. // *Action: End the backup of the offending tablespace and retry this command. 01126, 00000, "database must be mounted in this instance and not open in any instance" // *Cause: Obvious // *Action: 01127, 00000, "database name '%s' exceeds size limit of %s characters" // *Cause: Obvious // *Action: 01128, 00000, "cannot start online backup - file %s is offline" // *Cause: An attempt to start an online backup found that one of the files is // offline. // *Action: Bring the offending files online and retry this command or do a // cold backup. 01129, 00000, "user's default or temporary tablespace does not exist" // *Cause: The user's default or temporary tablespace was dropped. // *Action: Reassign the default or temporary tablespace. 01130, 00000, "database file version %s incompatible with ORACLE version %s" // *Cause: // *Action: 01131, 00000, "DB_FILES system parameter value %s exceeds limit of %s" // *Cause: // *Action: 01132, 00000, "length of database file name '%s' exceeds limit of %s characters" // *Cause: // *Action: 01133, 00000, "length of log file name '%s' exceeds limit of %s characters" // *Cause: // *Action: 01134, 00000, "database mounted exclusive by another instance" // *Cause: // *Action: 01135, 00000, "file %s accessed for DML/query is offline" // *Cause: Attempted to access a data file that is offline // *Action: Bring the data file back online 01136, 00000, "specified size of file %s (%s blocks) is less than original size of %s blocks" // *Cause: A file size was specified in the AS clause of ALTER DATABASE // CREATE DATAFILE, and the size was smaller the the size needed // *Action: Create the file with a larger size. 01137, 00000, "data file %s is still in the middle of going offline" // *Cause: It was not possible to get the lock for a file that is offline when // attempting to bring it online. The most likely cause is that the // lock is still held by the instance that is took it offline. // *Action: Wait a bit and try to online the file again. 01138, 00000, "database must either be open in this instance or not at all" // *Cause: The requested operation can not be done when the database is // mounted but not open in this instance, and another instance has // the database open. // *Action: Execute the operation in an open instance, open the datbase in // this instance, or close the database in the other instances. 01139, 00000, "RESETLOGS option only valid after an incomplete database recovery" // *Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there // has been no incomplete recovery session. // *Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS 01140, 00000, "cannot end online backup - all files are offline or readonly" // *Cause: All the files were found to be offline or readonly when attempting // to end an online backup. // *Action: None. Online backup does not need to be ended for this tablespace. 01141, 00000, "error renaming data file %s - new file '%s' not found" // *Cause: An attempt to change a data file's name in the control file // failed because no file was found with the new name. // *Action: Make sure that the data file has been properly renamed by the // operating system and retry. 01142, 00000, "cannot end online backup - none of the files are in backup" // *Cause: None of the files were found to be in online backup when attempting // to end an online backup. // *Action: None. Online backup does not need to be ended for this tablespace. 01143, 00000, "cannot disable media recovery - file %s needs media recovery" // *Cause: An attempt to disable media recovery found a file that needs media // recovery, thus media recovery cannot be disabled. // *Action: Recover the offending file or drop the tablespace it belongs to // and retry this command. 01144, 00000, "File size (%s blocks) exceeds maximum of %s blocks" // *Cause: Specified file size is larger than maximum allowable size value. // *Action: Specify a smaller size. 01145, 00000, "offline immediate disallowed unless media recovery enabled" // *Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE // ... OFFLINE is only allowed if database is in ARCHIVELOG mode. // *Action:Take tablespace offline normally or shutdown abort. Reconsider your // backup strategy. You could do this if you were archiving your logs. 01146, 00000, "cannot start online backup - file %s is already in backup" // *Cause: When starting an online backup it was noticed that an online backup // was already started for one of the data files. // *Action:End the first backup before beginning another. 01147, 00000, "SYSTEM tablespace file %s is offline" // *Cause: A file belonging to the SYSTEM tablespace has been marked offline // by the DBA. The database cannot be started until all SYSTEM // tablespace files are online and openable. // *Action: Bring the file online. 01148, 00000, "cannot refresh file size for datafile %s" // *Cause: An operating system or device error occurred when retrieving the // file's size. The device on which the file resides may have been // offline. // *Action: Restore access to the device. 01149, 00000, "cannot shutdown - file %s has online backup set" // *Cause: An attempt to shutdown normally found that an online backup is // still in progress. // *Action: End the backup of the offending tablespace and retry this command. 01150, 00000, "cannot prevent writes - file %s has online backup set" // *Cause: An attempt to make a tablespace read only or offline normal found // that an online backup is still in progress. It will be necessary // to write the file header to end the backup, but that would not // be allowed if this command succeeded. // *Action: End the backup of the offending tablespace and retry this command. 01151, 00000, "use media recovery to recover block, restore backup if needed" // *Cause: Error 1172 occurred. // *Action: This is additional information for error 1172. 01152, 00000, "file %s was not restored from a sufficiently old backup " // *Cause: An incomplete recovery session was started, but an insufficient // number of logs were applied to make the database consistent. This // file is still in the future of the last log applied. The most // likely cause of this error is forgetting to restore the file // from a backup before doing incomplete recovery. // *Action: Either apply more logs until the database is consistent or // restore the database file from an older backup and repeat recovery. 01153, 00000, "an incompatible media recovery is active" // *Cause: Attempted to start an incompatible media recovery or open resetlogs // during media recovery or RMAN backup . Media recovery sessions // are incompatible if they attempt to recover the same data file. // Incomplete media recovery or open resetlogs is incompatible with // any media recovery. Backup or restore by RMAN is incompatible // with open resetlogs // *Action: Complete or cancel the other media recovery session or RMAN backup 01154, 00000, "database busy. Open, close, mount, and dismount not allowed now" // *Cause: Some operation is in progress that expects the opened/mounted state // of this instance to remain the same. // *Action: Wait for the operation to complete then retry. If attempting to // do a shutdown, SHUTDOWN ABORT will work. If this is a shutdown // of a standby database that is operating in NO DATA LOSS mode, you // must shutdown the primary database first. 01155, 00000, "the database is being opened, closed, mounted or dismounted" // *Cause: The requested operation needs the instance to be in a particular // state but the state is being changed. // *Action: Wait for the open, close, mount, or dismount to complete then // retry the operation. If necessary, a SHUTDOWN ABORT will always // work. 01156, 00000, "recovery or flashback in progress may need access to files" // *Cause: Either media recovery, instance recovery, or flashback was // in progress. The recovery or flashback in progress may need // the files to which this operation is being applied. // *Action: Wait for recovery or flashback to complete. 01157, 00000, "cannot identify/lock data file %s - see DBWR trace file" // *Cause: The background process was either unable to find one of the data // files or failed to lock it because the file was already in use. // The database will prohibit access to this file but other files will // be unaffected. However the first instance to open the database will // need to access all online data files. Accompanying error from the // operating system describes why the file could not be identified. // *Action: Have operating system make file available to database. Then either // open the database or do ALTER SYSTEM CHECK DATAFILES. 01158, 00000, "database %s already mounted" // *Cause: Another instance has a database by this name mounted. // *Action: Find which instance is still running. Perhaps you have not lost // the control files after all. 01159, 00000, "file is not from same database as previous files - wrong database id" // *Cause: Not all of the files specified in CREATE CONTROLFILE are from the // same database. The database ID of this file does not match that // from the first file specified. // *Action: Please double check the list of files provided to the CREATE 01160, 00000, "file is not a %s" // *Cause: The named file in the DATAFILE or LOGFILE section of the CREATE // CONTROLFILE command does not appear to be as stated. // *Action: Please double check the mentioned file. 01161, 00000, "database name %s in file header does not match given name of %s" // *Cause: The database name given at the command line does not match the // database name found in the file header. // *Action: Chance are good that the database name specified at the command // line is incorrect. Resolve the descepency, and resubmit the command. // If you are attempting to change the database name, be sure to // use the SET DATABASE option. 01162, 00000, "block size %s in file header does not match configured block sizes" // *Cause: CREATE CONTROLFILE discovered that the block size for this file // is incompatible with any of the configured cache blocksizes in // the INIT.ORA file. // *Action:Configure the appropriate cache for this block size using one of the // various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, // db_16k_cache_size, db_32K_cache_size) parameters. 01163, 00000, "SIZE clause indicates %s (blocks), but should match header %s" // *Cause: The size specified in bytes in the SIZE clause of the CREATE // CONTROLFILE statement does not equate to the number of blocks // recorded in the header. // *Action: Specify the correct filename and size ( in bytes ). 01164, 00000, "MAXLOGFILES may not exceed %s" // *Cause: MAXLOGFILES specified on the command line too large. // *Action: Resubmit the command with a smaller MAXLOGFILES 01165, 00000, "MAXDATAFILES may not exceed %s" // *Cause: MAXDATAFILES specified on the command line too large. // *Action: Resubmit the command with a smaller MAXDATAFILES 01166, 00000, "file number %s is larger than %s (%s)" // *Cause: File mentioned in CREATE CONTROLFILE has a file number which is // larger than that specified for MAXDATAFILES or MAXLOGFILES. // *Action: Increase the maximum specified on the command line. 01167, 00000, "two files are the same file/group number or the same file" // *Cause: There is an overlap of file numbers in the files specified on // the command line or the same file is specified twice. If they are // not the exact same file then one is likely to be a backup of the // other. If they are two members of the same log they must be specified // together in a group file spec. This message will also appear if // the same control file appears more than once in the control_files // parameter in the init.ora file. If this happens, check for // additional error messages. // *Action: Confirm that the file mentioned is not a repeat of a file already // mentioned in the command. If they are different files then omit the // earlier backup. If they are members of the same log, insure they are // in the same group file specification. If this message appears because // of a duplicate control file, check the control_files parameter in the // init.ora file and see if a file is specified more than once. // If all files names appear to be unique, check to make sure that the // actual control files themselves are unique. For example, in UNIX // check for a symbolic or a hard link to another control file in the list. 01168, 00000, "physical block size %s does not match size %s of other members" // *Cause: The file is located on a device with a different physical block // size than the other members in the group // *Action: Use a physical device with matching block size. 01169, 00000, "DATAFILE number 1 not found. Must be present" // *Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command. // *Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE // command. 01170, 00000, "file not found '%s'" // *Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be // accessible by the process for CREATE CONTROLFILE. // *Action: The file specified probably contains a typing error. Double // check command and the existance of all files and then resubmit. 01171, 00000, "datafile %s going offline due to error advancing checkpoint" // *Cause: The checkpoint in the file header could not be advanced. See // accompanying errors for the reason. The datafile will be taken // offline the same as for a write error of a data block. // *Action: See accompanying errors for details. Restore access to the file, // do media recovery, and bring it back online. 01172, 00000, "recovery of thread %s stuck at block %s of file %s" // *Cause: Crash recovery or instance recovery could not apply a change to a // block because it was not the next change. This can happen if the // block was corrupted and then repaired during recovery. // *Action: Do a RECOVER DATAFILE for the file containing the block. If this // does not resolve the problem then restore the file from a backup // and recover it. 01173, 00000, "data dictionary indicates missing data file from system tablespace" // *Cause: Either the database has been recovered to a point in time in the // future of the control file or a datafile from the system tablespace was // omitted from the create control file command previously issued. // *Action: For the former problem you need to recover the database from a // more recent control file. For the latter problem, simply recreate the // control file checking to be sure that you include all the datafiles in // the system tablespace. 01174, 00000, "DB_FILES is %s buts needs to be %s to be compatible" // *Cause: The maximum number of database files supported by this instance // is not the same as for the other instances. All instances must // be able to open all the files any instance can open. // *Action: Change the value of the DB_FILES parameter to be compatible 01175, 00000, "data dictionary has more than the %s files allowed by the instance" // *Cause: The data dictionary is found to have more files than that which can // be supported by this instance. // *Action: Shutdown the instance and restart with a larger number of db_files 01176, 00000, "data dictionary has more than the %s files allowed by the controlfie" // *Cause: After a CREATE CONTROLFILE, the data dictionary was found to have // more datafiles than that supported by the control file. // *Action: Recreate the control file with a larger MAXDATAFILES. 01177, 00000, "data file does not match dictionary - probably old incarnation" // *Cause: When comparing the control file with the data dictionary after // a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this // datafile was inconsistent with the dictionary. Most likely the // file is a backup of a file that was dropped from the database, // and the same file number was reused for a new file. It may also // be that an incomplete recovery stopped at a time when this file // number was used for another datafile. // *Action: Do a CREATE CONTROLFILE with the correct file or none at all. 01178, 00000, "file %s created before last CREATE CONTROLFILE, cannot recreate" // *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a // datafile that existed at the last CREATE CONTROLFILE command. // The information needed to recreate the file was lost with the // control file that existed when the file was added to the database. // *Action: Find a backup of the file, and recover it. Do incomplete recovery // to time before file was originally created. 01179, 00000, "file %s does not exist" // *Cause: During datafile recovery, a file was listed which was not part // for the database. // *Action: Recheck the datafile name. Remember to use double quotes at the // SQLDBA command line and remember that the file name is translated in the // environment of the SQLDBA. 01180, 00000, "can not create datafile 1" // *Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE // DATAFILE. // *Action: Recover file from a backup or recreate database. 01181, 00000, "file %s created before last known RESETLOGS, cannot recreate" // *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a // datafile that existed before the last known RESETLOGS. // *Action: Find a backup of the file, and recover it. Do incomplete recovery // to time before file was originally created. 01182, 00000, "cannot create database file %s - file is in use or recovery" // *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a // datafile that is online in an open instance or is being recovered. // *Action: Close database in all instances and end all recovery sessions 01183, 00000, "cannot mount database in SHARED mode" // *Cause: Some other instance has the database mounted exclusive. // *Action: Shutdown other instance then mount shared. 01184, 00000, "logfile group %s already exists" // *Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for // the new log which is already in use. // *Action: Specify a different logfile number, or let the database choose // an unused value. 01185, 00000, "logfile group number %s is invalid" // *Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for // the new log which is too large. // *Action: Specify a correct logfile number. 01186, 00000, "file %s failed verification tests" // *Cause: The data file did not pass the checks to insure it is part of the // database. See the accompanying error messages for the reason the // verification failed. // *Action: Make the correct file available to the database. Then, either open // the database, or execute ALTER SYSTEM CHECK DATAFILES. 01187, 00000, "cannot read from file %s because it failed verification tests" // *Cause: The data file did not pass the checks to insure it is part of the // database. Reads are not allowed until it is verified. // *Action: Make the correct file available to the database. Then, either open // the database, or execute ALTER SYSTEM CHECK DATAFILES. 01188, 00000, "The block size specified %s does not match header block size %s" // *Cause: The block size specified in the BLOCKSIZE clause of the CREATE // CONTROLFILE statement does not equate to the block size // recorded in the log file header. // *Action: Specify the correct block size. 01189, 00000, "file is from a different RESETLOGS than previous files" // *Cause: In a CREATE CONTROLFILE command either this file or all previous // files were backups from before the last RESETLOGS. This may also // occur if this is a file that is offline and has been offline since // before the last RESETLOGS. // *Action: If the file was taken offline normal before the last RESETLOGS, // and is still offline, omit it from the CREATE CONTROLFILE command. // Rename and online the file after the database is open. Otherwise // find the version of the mentioned file consistent with the rest // of the datafiles and resubmit the command. 01190, 00000, "control file or data file %s is from before the last RESETLOGS" // *Cause: Attempting to use a data file when the log reset information in // the file does not match the control file. Either the data file // or the control file is a backup that was made before the most // recent ALTER DATABASE OPEN RESETLOGS. // *Action: Restore file from a more recent backup. 01191, 00000, "file %s is already offline - cannot do a normal offline" // *Cause: When attempting to do a normal tablespace offline it was discovered // that one of the files in the tablespace was already offline. // *Action: Either bring the datafile online first, or use another tablespace // offline option. 01192, 00000, "must have at least one enabled thread" // *Cause: You must specify at least two logfiles from at least one thread // at the create contolfile command line. // *Action: Find the missing logfiles and resubmit the command with the newly // found logfiles included in the command line. 01193, 00000, "file %s is not the same file seen at start of recovery" // *Cause: A different copy of the file was accessed the last time media // recovery looked at the file header. A backup of the file was // restored or the meaning of the file name changed during recovery. // *Action:Ensure the correct file is available, then retry recovery. 01194, 00000, "file %s needs more recovery to be consistent" // *Cause: An incomplete recovery session was started, but an insufficient // number of logs were applied to make the file consistent. The // reported file was not closed cleanly when it was last opened by // the database. It must be recovered to a time when it was not being // updated. The most likely cause of this error is forgetting to // restore the file from a backup before doing incomplete recovery. // *Action: Either apply more logs until the file is consistent or restore // the file from an older backup and repeat recovery. 01195, 00000, "online backup of file %s needs more recovery to be consistent" // *Cause: An incomplete recovery session was started, but an insufficient // number of logs were applied to make the file consistent. The // reported file is an online backup which must be recovered to the // time the backup ended. // *Action: Either apply more logs until the file is consistent or // restore the database files from an older backup and repeat recovery. 01196, 00000, "file %s is inconsistent due to a failed media recovery session" // *Cause: The file was being recovered but the recovery did not terminate // normally. This left the file in an inconsistent state. No more // recovery was successfully completed on this file. // *Action:Either apply more logs until the file is consistent or restore // the backup again and repeat recovery. 01197, 00000, "thread %s only contains one log" // *Cause: During CREATE CONTROLFILE all threads represented in the logs // must be represented by at least two logs. A "last log" and a second // log. The named thread does not contain two such logs. // *Action: Either find more logs from the named thread. Or use the // RESETLOGS option to CREATE CONTROLFILE. 01198, 00000, "must specify size for log file if RESETLOGS" // *Cause: File sizes must be given for all logfiles if doing a CREATE // CONTROLFILE with the RESETLOGS option. // *Action: Resubmit the command with the appropriate logfile size. 01199, 00000, "file %s is not in online backup mode" // *Cause: Attempting to end an online backup for a file that is not in online // backup. // *Action: Do not enter command since it is not needed. 01200, 00000, "actual file size of %s is smaller than correct size of %s blocks" // *Cause: The size of the file as returned by the operating system is smaller // than the size of the file as indicated in the file header and the // control file. Somehow the file has been truncated. Maybe it is the // result of a half completed copy. // *Action: Restore a good copy of the data file and do recovery as needed. 01201, 00000, "file %s header failed to write correctly" // *Cause: An I/O error was reported for the file header. The error was // trapped and a second attempt will be made. // *Action: The file probably will require recovery. Further error messages // will indicate what is needed. 01202, 00000, "wrong incarnation of this file - wrong creation time" // *Cause: The creation time in the file header is not the same as the // creation time in the control file. This is probably a copy of a // file that was dropped. // *Action: Restore a current copy of the data file and do recovery as needed. 01203, 00000, "wrong incarnation of this file - wrong creation SCN" // *Cause: The creation SCN in the file header is not the same as the // creation SCN in the control file. This is probably a copy of a // file that was dropped. // *Action: Restore a current copy of the data file and do recovery as needed. 01204, 00000, "file number is %s rather than %s - wrong file" // *Cause: The file number in the file header is not correct. This is probably // a restored backup of the wrong file, but from the same database. // *Action: Restore a copy of the correct data file and do recovery as needed. 01205, 00000, "not a data file - type number in header is %s" // *Cause: The file type in the header is not correct for a data file. This // is probably a log file or control file. If the type is not a small // non-zero positive number then the header is corrupted. // *Action: Restore a copy of the correct data file and do recovery as needed. 01206, 00000, "file is not part of this database - wrong database id" // *Cause: The database ID in the file header does not match the database id // in the control file. The file may be from a different database, or // it may not be a database file at all. If the database was rebuilt, // this may be a file from before the rebuild. Note that if you see // this error when the file is supposed to be plugged in from another // database via the Transportable Tablespace feature, it means the // database ID in the file header does not match the one expected. // *Action: Restore a copy of the correct data file and do recovery as needed. 01207, 00000, "file is more recent than control file - old control file" // *Cause: The control file change sequence number in the data file is // greater than the number in the control file. This implies that // the wrong control file is being used. Note that repeatedly causing // this error can make it stop happening without correcting the real // problem. Every attempt to open the database will advance the // control file change sequence number until it is great enough. // *Action: Use the current control file or do backup control file recovery to // make the control file current. Be sure to follow all restrictions // on doing a backup control file recovery. 01208, 00000, "data file is an old version - not accessing current version" // *Cause: The checkpoint in the file header is less recent than in the // control file. If opening a database that is already open by another // instance, or if another instance just brought this file online, // the file accessed by this instance is probably a different version. // Otherwise, a backup of the file probably was restored // while the file was in use. // *Action: Make the correct file available to the database. Then, either open // the database, or execute ALTER SYSTEM CHECK DATAFILES. 01209, 00000, "data file is from before the last RESETLOGS" // *Cause: The reset log data in the file header does not match the // control file. If the database is closed or the file is offline, // the backup is old because it was taken before the last ALTER // DATABASE OPEN RESETLOGS command. If opening a database that is // open already by another instance, or if another instance just // brought this file online, the file accessed by this instance is // probably a different version. Otherwise, a backup of the file // probably was restored while the file was in use. // *Action: Make the correct file available to the database. Then, either open // the database, or execute ALTER SYSTEM CHECK DATAFILES. 01210, 00000, "data file header is media corrupt" // *Cause: The file header block is internally inconsistent. The beginning // of the block has a header with a checksum and other data for // insuring the consistancy of the block. It is possible that // the last disk write did not operate correctly. The most likely // problem is that this is not a datafile for any database. // *Action: Have operating system make correct file available to database. // If the trace file dump indicates that only the checksum is wrong, // restore from a backup and do media recovery. 01211, 00000, "Oracle7 data file is not from migration to Oracle8" // *Cause: The file is not a copy of the file LAST used under Oracle7. This // datafile is either a backup taken from before the migration, or // the database was opened by Oracle7 after the migration utility was // run. When converting a database from Oracle7 to Oracle8, the migration // program MUST be the LAST utility to access the database under Oracle7. // Only the datafiles that were current when the migration was done // may be accessed by Oracle8. // *Action: Have operating system make correct data file available to database, // or repeat the Oracle7 to Oracle8 migration. Make sure that // database is NOT opened after migration utility is run. 01212, 00000, "MAXLOGMEMBERS may not exceed %s" // *Cause: MAXLOGMEMBERS specified on the command line too large. // *Action: Resubmit the command with a smaller MAXLOGMEMBERS 01213, 00000, "MAXINSTANCES may not exceed %s" // *Cause: MAXINSTANCES specified on the command line too large. // *Action: Resubmit the command with a smaller MAXINSTANCES 01214, 00000, "MAXLOGHISTORY may not exceed %s" // *Cause: MAXLOGHISTORY specified on the command line too large. // *Action: Resubmit the command with a smaller MAXLOGHISTORY 01215, 00000, "enabled thread %s is missing after CREATE CONTROLFILE" // *Cause: A CREATE CONTROLFILE statement was given which did not // list all the enabled threads for the database. // *Action: Reissue the CREATE CONTROLFILE statement, including all enabled // threads. 01216, 00000, "thread %s is expected to be disabled after CREATE CONTROLFILE" // *Cause: A thread that was given during CREATE CONTROLFILE is enabled, but // the datafiles indicate that it should be disabled. This is // probably because the logs supplied to the CREATE CONTROLFILE // are old (from before the disabling of the thread). // *Action: This thread is not required to run the database. The CREATE // CONTROLFILE statement can be reissued without the problem thread, // and, if desired, the thread can be recreated after the database // is open. 01217, 00000, "logfile member belongs to a different logfile group" // *Cause: A member of a multiple-member logfile group specified in a // CREATE CONTROLFILE is not part of the same group as previous // members. // *Action: Group together the correct members for the CREATE CONTROLFILE // command. 01218, 00000, "logfile member is not from the same point-in-time" // *Cause: A member of a multiple-member logfile group is from a different // point in time. One of the members specified may be an older // (backup) copy of the log. // *Action: Find the correct version of the log, or leave it out of the // CREATE CONTROLFILE command. 01219, 00000, "database not open: queries allowed on fixed tables/views only" // *Cause: A query was issued against an object not recognized as a fixed // table or fixed view before the database has been opened. // *Action: Re-phrase the query to include only fixed objects, or open the // database. 01220, 00000, "file based sort illegal before database is open" // *Cause: A query issued against a fixed table or view required a temporary // segment for sorting before the database was open. Only in-memory // sorts are supported before the database is open. // *Action: Re-phrase the query to avoid a large sort, increase the values // of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE // initialization parameters to enable the sort to be done in memory. 01221, 00000, "data file %s is not the same file to a background process" // *Cause: When the database writer opens the data file, it is accessing a // different physical file than the foreground doing the recovery. // The timestamp set in the file header by the foreground was not // found by the background. It may be that the background process // could not read the file at all. // *Action: Look in the DBWR trace file for the error it recieved when // attempting to read the file header. Reconfigure the operating // system as needed to have the file name successfully access the // same file when opened by a background process. 01222, 00000, "MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s" // *Cause: Attemping to create a database or control file that does not have // room for at least two logs per thread of redo. A thread of redo // must have two online logs in order to be enabled. It does not make // sense to allow more redo threads than can be supported by the logs. // *Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES. 01223, 00000, "RESETLOGS must be specified to set a new database name" // *Cause: The SET database name option was specified to CREATE CONTROLFILE, // but RESETLOGS was not specified. The database name can only be // changed when opening the database with RESETLOGS. // *Action: Either add the RESETLOGS option or drop the SET option to // CREATE CONTROLFILE. 01224, 00000, "group number in header %s does not match GROUP %s" // *Cause: Group number specified at CREATE CONTROLFILE does not match the // group number stored in the header. Most likely the specification // is wrong. // *Action: Omit the GROUP option or give the correct one. 01225, 00000, "thread number %s is greater than MAXINSTANCES %s" // *Cause: The log is for a thread greater than the MAXINSTANCES argument. // *Action:Increase the value for MAXINSTANCES and resubmit the command. 01226, 00000, "file header of log member is inconsistent with other members" // *Cause: The log file member in the accompanying error is for the same group // as the previous members, but other fields in the header are // different. Either a file header is corrupted, or some file is a // member of a deleted log. //*Action: Find the correct log member or omit this member from the command. 01227, 00000, "log %s is inconsistent with other logs" // *Cause: The log file in the accompanying error is inconsistent with the // contents of other logs given in the CREATE CONTROLFILE command. // Either a file header is corrupted, or some file is an old copy // rather than the current version. The problem may not be with the // log listed since all that can be detected is that there is an // inconsistancy. All log files listed in the command must be the // current versions of the online logs. //*Action: Find the correct online logs or use the RESETLOGS option. 01228, 00000, "SET DATABASE option required to install seed database" // *Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE // command when installing a seed database. The database does not have // a database ID because it is intended to be installed at multiple // sites, and each site needs to be a different database with its own // database id. Both the SET DATABASE and RESETLOGS options must be // specified to create the control file for this database. //*Action: Resubmit command with the SET DATABASE and RESETLOGS options. 01229, 00000, "data file %s is inconsistent with logs" // *Cause: The data file in the accompanying error is inconsistent with the // contents of the logs given in the CREATE CONTROLFILE command. // The most likely cause is that one or more of the online logs // was missing from the command. It is also possible that one or // more of the logs is an old copy rather than the current version. // All online log files must be listed in the command and must be the // current versions of the online logs. //*Action: Find the correct online logs or use the RESETLOGS option. 01230, 00000, "cannot make read only - file %s is offline" // *Cause: An attempt to make a tablespace read only found that one of its // files is offline. // *Action: Bring the file online and retry this command. 01231, 00000, "cannot make read write - file %s is offline" // *Cause: An attempt to make a tablespace read write found that one of its // files is offline. // *Action: Bring the file online and retry this command. 01232, 00000, "cannot start online backup - file %s is being made read-only" // *Cause: An attempt to start an online backup found that one of the files is // in transition to read-only mode. // *Action: Wait for the transition to complete and then retry the command, if // this is an ALTER DATABASE BEGIN BACKUP command, or take the backup // without any begin or end commands, if this is an ALTER TABLESPACE // BEGIN BACKUP command. 01233, 00000, "file %s is read only - cannot recover using backup control file" // *Cause: An attempt to do media recovery using a backup control file found // that one of the files is marked read only. Read only files do not // normally need to be recovered, but recovery with a backup // control file must recover all online files. // *Action: If the file really is read only, take it offline before the // recovery, and bring the read only tablespace online after the // database is open. If the file does need recovery use a control file // from the time the file was read-write. If the correct control file // is not available, use CREATE CONTROLFILE to make one. 01234, 00000, "cannot end backup of file %s - file is in use or recovery" // *Cause: Attempted to end an online backup of file when the file is busy. // Some operation such as recovery or rename may be active, or there // may still be some instance that has the database open with this // file online. // *Action: If there is an instance with the database open then the backup // can be ended there by using the ALTER TABLESPACE command. Otherwise // wait for the completion of the other operation. 01235, 00000, "END BACKUP failed for %s file(s) and succeeded for %s" // *Cause: One or more of the files in an end backup command failed. Some other // files given in the same command may have succeeded. // *Action: See the accompanying error messages for the reason the backups // could not be ended. Any files not listed in the error messages were // successful. 01236, 00000, "Error %s occurred during initialization of file header access" // *Cause: The indicated error occurred while doing initialization // processing of file headers. // *Action: The error indicated should be corrected. An attempt is made to // recover from this error by using a slower access algorithm. 01237, 00000, "cannot extend datafile %s" // *Cause: An operating system error occurred during the resize. // *Action: Fix the cause of the operating system error and retry the command. 01238, 00000, "cannot shrink datafile %s" // *Cause: An operating system error occurred during the resize. // *Action: The error is ignored, operation continues normally. 01239, 00000, "database must be in ARCHIVELOG mode to use external cache" // *Cause: An online file uses an external cache, but the database is in // NOARCHIVELOG mode. Since an external cache may require media // recovery this can not be allowed. // *Action: Change database to be in ARCHIVELOG mode or do not use an // external cache. 01240, 00000, "too many data files to add in one command" // *Cause: The command specifies adding more data files than can be done in // one command. It is necessary to fit all the file names into one // log entry, but that would make the entry too large. // *Action: If this is a CREATE TABLESPACE command, create with fewer files // then add the other files later. If this is an ADD DATAFILE command, // break it up into multiple commands. 01241, 00000, "an external cache has died" // *Cause: The external cache may have been restarted. // *Action: Take the file mentioned in the error stack offline, perform media // recovery, bring the file online, and retry the attempted // operation. You may also restart all instances to make sure // they access all data files through consistent external caches. 01242, 00000, "data file suffered media failure: database in NOARCHIVELOG mode" // *Cause: The database is in NOARCHIVELOG mode and a database file was // detected as inaccessible due to media failure. // *Action: Restore accessibility to the file mentioned in the error stack // and restart the instance. 01243, 00000, "system tablespace file suffered media failure" // *Cause: A system tablespace file was detected as inaccessible due to // media failure. // *Action: Restore accessibility to the file mentioned in the error stack // and restart the instance. 01244, 00000, "unnamed datafile(s) added to control file by media recovery" // *Cause: Media recovery with a backup control file or a control file that // was rebuilt, encountered the creation of a datafile that was not // in the control file. An entry has been added to the control file // for the new datafiles, but with the file name UNNAMEDnnnn, where // nnnn is the file number. Attached errors describe the file names // that were originally used to create the files. // *Action: Rename the files to valid file names and resume recovery. If // necessary the command ALTER DATABASE CREATE DATAFILE may be used // to create a file suitable for recovery and do the rename. If the // file is not going to be recovered then take it offline with the // FOR DROP option. 01245, 00000, "offline file %s will be lost if RESETLOGS is done" // *Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost // because it is offline. The file was not taken offline with the // FOR DROP option. // *Action: Either bring the file online and recover it, or take it offline // with the FOR DROP option. 01246, 00000, "recovering files through TSPITR of tablespace %s" // *Cause: The files named in the accompanying errors are backups that were // made before a tablespace point in time recovery of this tablespace. // They cannot be recovered to a time after the point in time // recovery. // *Action: Restore more recent backups and recover them. 01247, 00000, "database recovery through TSPITR of tablespace %s" // *Cause: Recovery of the whole database encountered redo indicating there // was a point in time recovery of the tablespace. The new version // of the files in the tablespace should be included in the recovery, // but that was not done. // *Action: If the tablespace should not be recovered, take its file offline // for drop. If it should be recovered, then restore or rename as // needed and restart the recovery. 01248, 00000, "file %s was created in the future of incomplete recovery" // *Cause: Attempting to do a RESETLOGS open with a file entry in the // control file that was originally created after the UNTIL time // of the incomplete recovery. // Allowing such an entry may hide the version of the file that // is needed at this time. The file number may be in use for // a different file which would be lost if the RESETLOGS was allowed. // *Action: If more recovery is desired then apply redo until the creation // time of the file is reached. If the file is not wanted and the // same file number is not in use at the stop time of the recovery, // then the file can be taken offline with the FOR DROP option. // Otherwise a different control file is needed to allow the RESETLOGS. // Another backup can be restored and recovered, or a control file can // be created via CREATE CONTROLFILE. 01249, 00000, "archiving not allowed in a clone database" // *Cause: Attempting to archive an online redo log or enable archiving // for a clone database. // *Action: Do not attempt to archive from a clone. The archive log destination // could easily be the same as the primary database destroying its // archived logs. If archiving is needed then recreate database as // not a clone. 01250, 00000, "Error %s occurred during termination of file header access" // *Cause: The indicated error occurred while terminating the // processing of file headers. The error was other than a write // error. // *Action: The indicated error should be corrected. 01251, 00000, "Unknown File Header Version read for file number %s" // *Cause: Read of the file header returned a record but its version cannot // be identified. Either the header has been corrupted, or the file // is not a valid database file. // *Action: Have the operating system make the correct file available to // the database, or recover the file. 01252, 00000, "cannot prevent writes - file %s in recovery manager backup" // *Cause: An attempt to make a tablespace read only or offline normal found // that a recovery manager proxy backup is in progress. If the file // is made offline or read-only, then the file header cannot be // updated when the backup is complete. // *Action: Wait for the Recovery Manager backup to complete and retry this // command. 01253, 00000, "cannot start online backup - file %s in recovery manager backup" // *Cause: The specified file is being backed up by Recovery Manager. // *Action: Wait for the Recovery Manager proxy backup to complete before // starting another backup. 01254, 00000, "cannot end online backup - file %s in recovery manager backup" // *Cause: The specified file is being backed up by Recovery Manager. // *Action: Wait for the Recovery Manager proxy backup to complete. Recovery // Manager backup mode cannot be initiated or terminated manually. 01255, 00000, "cannot shutdown - file %s in recovery manager backup" // *Cause: An attempt to shutdown normally found that a Recovery Manager // backup is still in progress. // *Action: Wait for the Recovery Manager proxy backup to complete and retry // this command. 01256, 00000, "error in locking database file %s" // *Cause: The file is in use by another database instance. // *Action: Determine which database instance legitimately owns the file. 01257, 00000, "cannot reuse database file %s, unknown file size" // *Cause: The size of the raw partion cannot be determined // *Action: Add the datafile/logfile by specifying the size parameter. 01258, 00000, "unable to delete temporary file %s" // *Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES // or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES // operation was not able to delete a temporary file in the // database. // *Action: Subsequent errors describe the operating system error that // prevented the file deletion. Fix the problem, if possible, and // manually purge the file. 01259, 00000, "unable to delete datafile %s" // *Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation // was not able to delete a datafile in the tablespace. // *Action: Subsequent errors describe the operating system error that // prevented the file deletion. Fix the problem, if possible, and // manually purge the file. 01260, 00000, "warning: END BACKUP succeeded but some files found not to be in backup mode" // *Cause: END BACKUP completed successfully for all files that were in online // backup mode. However one or more modifiable files were found not // to be in online backup mode. Backup of those files (if it was done) // can be invalid and, if restored, can result in an inconsistent // database. // *Action: Check the alert log for a list of the files that were found not // to be in backup mode. If there is a possibility that those files // have been modified during online backup, then replace their // backups with new ones. 01261, 00000, "Parameter %s destination string cannot be translated" // *Cause: The value for the specified parameter contained a destination // string that could not be translated. // *Action: Use a valid destination string in the specified parameter. 01262, 00000, "Stat failed on a file destination directory" // *Cause: Unable to get information about an Oracle managed files // destination directory. // *Action: Check the permissions on the directory or use a different // directory name. 01263, 00000, "Name given for file destination directory is invalid" // *Cause: The name given for an Oracle managed files destination // does not correspond to a directory. // *Action: Use a different name. 01264, 00000, "Unable to create %s file name" // *Cause: Unable to create an Oracle managed file name. // *Action: Check previous error messages for the reason Oracle // was unable to create the file name. Take corrective // action, if possible, and retry the command. 01265, 00000, "Unable to delete %s %s" // *Cause: An error prevented the file from being deleted. // *Action: See the subsequent error messsages that describe the operating // system error that prevented the file from being deleted. If // possible, fix the problem and manually delete the file. 01266, 00000, "Unable to create unique file name" // *Cause: Unable to create a unique file name for an Oracle managed file. // Oracle tried several names but each file name was already in use // in the default destination directory for the file type. // *Action: Retry the operation. If that fails, also, it may be // necessary to change the default destination directory for // the file type and then retry. 01267, 00000, "Failure getting date/time" // *Cause: Could not get date/time when trying to create unique // file name. // *Action: Internal error - contact Oracle Customer Support. 01268, 00000, "invalid TEMPFILE clause for alter of permanent TABLESPACE" // *Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for // a permanent tablespace. // *Action: Retry with a DATAFILE clause. 01269, 00000, "Destination parameter string is too long" // *Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or // DB_RECOVERY_FILE_DEST parameter was too long. // *Action: Replace the destination value for the specified parameter with // a shorter character string. 01270, 00000, "%s operation is not allowed if STANDBY_PRESERVES_NAMES is true" // *Cause: An operation that renames or adds/drops a file was attempted // at a standby database and STANDBY_PRESERVES_NAMES is true. // *Action: Set STANDBY_PRESERVES_NAMES false if the operation must be // performed. 01271, 00000, "Unable to create new file name for file %s" // *Cause: During standby database recovery an error occurred when trying // to create a new file name for the indicated file. // *Action: Use the ALTER DATABASE CREATE DATAFILE command with a new // unique name and then resume the standby database recovery. 01272, 00000, "REUSE only allowed when a file name is provided." // *Cause: The REUSE parameter was specified in a command without a // file name. // *Action: Either supply a file name or remove the REUSE parameter. 01273, 00000, "STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = %s or higher" // *Cause: The COMPATIBLE initialization parameter was not set to the // correct value for setting STANDBY_FILE_MANAGEMENT to AUTO. // *Action: Restart the instance with COMPATIBLE set to the correct release. // *Cause: Automated standby file management was disabled, so an added file 01274, 0000, "cannot add datafile '%s' - file could not be created" // *Cause: Automated standby file management was disabled, so an added file // could not automatically be created on the standby. // The error from the creation attempt is displayed in another message. // The control file file entry for the file is 'UNNAMEDnnnnn'. // *Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the // file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart // standby recovery. 01275, 00000, "Operation %s is not allowed if standby file management is automatic." // *Cause: An operation that renames, adds, or drops a file was attempted // at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO. // *Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be // performed. 01276, 00000, "Cannot add file %s. File has an Oracle Managed Files file name." // *Cause: An attempt was made to add to the database a datafile, log file, // control file, snapshot control file, backup control file, // datafile copy, control file copy or backuppiece with an Oracle // Managed Files file name. // *Action: Retry the operation with a new file name. 01277, 00000, "file '%s' already exists" // *Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' // command specified a file name which is already in use. // *Action: Either specify a different file name, or add the REUSE parameter // to the command to overwrite the existing file. 01278, 00000, "error creating file '%s'" // *Cause: An operating system error occurred while attempting to create a // trace file specified in the command ALTER DATABASE BACKUP // CONTROLFILE TO TRACE AS 'filename'. // *Action: Check the error stack for more detailed information. 01279, 00000, "db_files too large" // *Cause: db_files has been set too high to be supported by the system. // *Action: Decrease the number of db_files. / / 1280-1399 LogMiner errors / 01280, 00000, "Fatal LogMiner error." // *Cause: An internal error occurred inside LogMiner. // *Action: Check the alert log and trace files for further information. 01281, 00000, "SCN range specified is invalid" // *Cause: StartSCN may be greater than EndSCN, or the SCN specified may be // invalid. // *Action: Specify a valid SCN range. 01282, 00000, "date range specified is invalid" // *Cause: startTime may be greater than endTime. startTime or endTime may be // greater than year 2110. startTime may be less than year 1988. // *Action: Specify a valid date range. 01283, 00000, "Options specified is invalid" // *Cause: The specified options parameter is invalid for the procedure. // *Action: Specify valid Options parameter. 01284, 00000, "file %s cannot be opened" // *Cause: The file or directory may not exist or may be inaccessible. // Pathname exceeds 256 characters. // *Action: Ensure that the file and the directory exist and are accessible. 01285, 00000, "error reading file %s" // *Cause: The file or directory may not exist or is inaccessible. // *Action: Specify valid file or directory. Make sure that file and directory // are accessible. 01286, 00000, "start interval required" // *Cause: Options were supplied which require a starting time or starting SCN // *Action: Specify a starting interval (time or SCN). 01287, 00000, "file %s is from a different database incarnation" // *Cause: The logfile is produced by a different incarnation of the database. // *Action: Add a logfile that is produced by the same incarnation. 01288, 00000, "cannot apply this DDL to the Logminer Dictionary" // *Cause: A command that is not supported by Logminer was present in // a logfile. Commands that change the character set of the database // are not supported by Logminer. // "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer. // *Action: Do not execute unsupported commands when using Streams, Logical // Standby, or Logminer. Turn off DDL tracking in order for Logminer // to skip unsupported commands. 01289, 00000, "cannot add duplicate logfile %s" // *Cause: The logfile specified has already been added to the list of // logfiles. // *Action: Specify a different logfile. 01290, 00000, "cannot remove unlisted logfile %s" // *Cause: The user attempted to remove a logfile that is not present in the // list. // *Action: Specify a valid logfile. 01291, 00000, "missing logfile" // *Cause: Not all logfiles corresponding to the time or scn range specified // have been added to the list. // *Action: Check the v$logmnr_logs view to determine the missing scn // range, and add the relevant logfiles. 01292, 00000, "no log file has been specified for the current LogMiner session" // *Cause: No logfile has been specified for the LogMiner session. // *Action: Specify atleast one log file. 01293, 00000, "mounted database required for specified LogMiner options" // *Cause: Options were specified which required the database to be mounted // *Action: Specify different options or mount the database. 01294, 00000, "error occurred while processing information in dictionary file %s, possible corruption" // *Cause: The dictionary file is corrupt. // *Action: Get a new dictionary file. 01295, 00000, "DB_ID mismatch between dictionary %s and logfiles" // *Cause: The dictionary file is produced by a database that is different // from that produced the logfiles. // *Action: Specify a compatible dictionary file. 01296, 00000, "character set mismatch between dictionary %s and logfiles" // *Cause: The character set of the database that produced the dictionary // file is different from the charatcter set of the database // that produced the logfiles. // *Action: Specify a dictionary file with the same character set. 01297, 00000, "redo version mismatch between dictionary %s and logfiles" // *Cause: The redo version of the database generating the dictionary is // different from the one generating the logfiles. // *Action: 01298, 00000, "conflicting dictionary option" // *Cause: More than one dictionary source was specified or DDL_DICT_TRACKING // was specified with DICT_FROM_ONLINE_CATALOG. // *Action: 01299, 00000, "dictionary %s corresponds to a different database incarnation" // *Cause: The dictionary file was extracted from a different incarnation of // the database. // *Action: Specify a dictionary file extracted from the correct database // incarnation. 01300, 00000, "writable database required for specified LogMiner options" // *Cause: Options were specified which required the database to be writable. // *Action: Specify different options or open the database for write access. 01301, 00000, "error writing to file during flat file build" // *Cause: Error writing to file during flat file build // *Action: 01302, 00000, "dictionary build options missing or incorrect" // *Cause: Missing dictionary build options or incorrectly specified options // *Action: Specify either a build to redo log or to flat file. If build to // flat file, specify filename and directory. 01303, 00000, "subordinate process error: %u. Check alert and trace logs" // *Cause: A process subordinate to this Logminer process has exited with // this error status. // *Action: Search for this error in the alert log and trace files for // additional information. 01304, 00000, "subordinate process error. Check alert and trace logs" // *Cause: A process subordinate to this Logminer process has exited with an // error condition. // *Action: Look in the alert log and trace files for additional information. 01306, 00000, "dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents" // *Cause: A select was issued from v$logmnr_contents without first invoking // the dbms_logmnr.start_logmnr() procedure. // *Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing // a select from the v$logmnr_contents view. 01307, 00000, "no LogMiner session is currently active" // *Cause: A select was issued from v$logmnr_contents without first invoking // the dbms_logmnr.start_logmnr() procedure. Otherwise, // dbms_logmnr.end_logmnr() was called without a prior call to // dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile() // *Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing // a select from the v$logmnr_contents view. 01308, 00000, "initialization parameter utl_file_dir is not set" // *Cause: utl_file_dir is not set in the initialization file. // *Action: Set utl_file_dir to the appropriate directory. 01309, 00000, "invalid session" // *Cause: The specified Logminer session ID or session handle is invalid. // *Action: Use a valid Logminer session ID or session handle. 01310, 00000, "requested return type not supported by the lcr_mine function" // *Cause: The return type requested by the user is not supported by lcr_mine" // *Action: Pick a return type supported by the lcr_mine function" 01311, 00000, "Illegal invocation of the mine_value function" // *Cause: An attempt was made to use mine_value function on a column // other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS // or SYS.V$LOGMNR_CONTENTS fixed table/view. // *Action: Rewrite the SQL statement with a legal invocation of mine_value 01312, 00000, "Specified table/column does not exist" // *Cause: The table/column specified in the lcr_mine call does not exist // at the the specified SCN. The table/column definition has to exist // at the start SCN specified for lcr_mine to be able to identify // the table/column correctly. // *Action: Create a LogMiner session at a start SCN at which the table // definition is available. 01313, 00000, "LogMiner dictionary column type different from specified type" // *Cause: The return type specified for the column in lcr_mine call // is different from the actual type of the column. // *Action: Rewrite the lcr_mine invocation with the right return type. 01314, 00000, "Name of the column to be mined should be a string literal" // *Cause: The fully qualified name of the column to be mined // by the LogMiner functions should be string literal. // *Action: If the fully qualified name of the column to be mined is a.b.c.d, // enclose the column name in quotes as in 'a.b.c.d'. 01315, 00000, "Log file has been added or removed during select" // *Cause: A redo log file has been added or removed while selecting // on the v$logmnr_logs fixed view. // *Action: Re-issue the SQL select statement on the v$logmnr_logs view. 01316, 00000, "Already attached to a Logminer session" // *Cause: A Logminer attach session was issued while already attached // to a Logminer session. // *Action: Detach from the current Logminer session and attach to the // requested session. 01317, 00000, "Not attached to a Logminer session" // *Cause: A command or procedure was issued which requires an attached // Logminer session. // *Action: Attach to a Logminer session before issuing the command or // procedure. 01319, 00000, "Invalid Logminer session attribute" // *Cause: A session attribute was supplied which is invalid. // *Action: Re-issue with valid session attribute. 01320, 00000, "Invalid Logminer dictionar attribute" // *Cause: A Logminer dictionary attribute was supplied which is invalid. // *Action: Re-issue with valid dictionary attribute. 01321, 00000, "No Logminer Dictionary for requested start SCN" // *Cause: The requested session start SCN is less than the SCN of any // available Logminer Dictionary build. It is not possible to // unwind a Logminer Dictionary to the requested start SCN. // *Action: Re-issue the start_logminer request with a start SCN for // which a Logminer Dictionary is available. 01322, 00000, "No such table" // *Cause: An non-existent table was supplied to Logminer include_src_tbl() // or exclude_src_table(). // *Action: Re-issue with valid table name. 01323, 00000, "Invalid state" // *Cause: A Logminer routine was called from the wrong state. // *Action: 01324, 00000, "cannot add file %s due to DB_ID mismatch" // *Cause: The logfile is produced by a different database than other logfiles // already added to the list. // *Action: Specify a logfile produced by the same database. 01325, 00000, "archive log mode must be enabled to build into the logstream" // *Cause: Database does not have archivelog mode enabled. // *Action: Mount the database, then issue commands to enable archivelog mode. // startup pfile=init.ora mount // alter database archivelog // alter database open 01326, 00000, "compatability of 9.0 or greater required to build into the logstream" // *Cause: Compatibility mode set to some value less than 9.0 // *Action: Ensure that init.ora parameter establishing a compatability of // 9.0 or greater is set. For example: // compatible=9.0.0.0.0 01327, 00000, "failed to exclusively lock system dictionary as required by build" // *Cause: Other users are performing DDL operations. // *Action: 01328, 00000, "only one build operation may occur at one time" // *Cause: Another processes is simultaneously attempting to run build(); // *Action: Wait until the other processes completes. 01329, 00000, "unable to truncate required build table" // *Cause: The table may be missing, or locked by another user. // *Action: 01330, 00000, "problem loading a required build table" // *Cause: // *Action: 01331, 00000, "general error while running build" // *Cause: // *Action: 01332, 00000, "internal Logminer Dictionary error" // *Cause: Unexpected error condition // *Action: Check trace and/or alert logs 01333, 00000, "failed to establish Logminer Dictionary" // *Cause: No previously established Logminer Dictionary is available // and a complete gather of a source system data dictionary was not // found in the logstream. build() may not have been run // to force the gathering of a source system data dictiony. // Or add_log_file() may not have been called to add all log // files which contain the complete gathered system data dictionary. // *Action: If build() was not employed prior to this mining session // the Logminer Ad Hoc user may elect to employ an alternate // dictionary such as the current system catalog or a previously // built flat file dictionary. Other Logminer clients must run // build() prior to mining. If build() has been run, ensure that // all logfiles which comprise the gathered system dictionary // have beed added. The following query, run on the system which // build() was run, can be helpful in identifying the requried files. // // select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; // // Minimally a set of files beginning with one which has // DICTIONARY_BEGIN = 'YES' and all following log files through // one marked DICTIONARY_END = 'YES' must be added. 01334, 00000, "invalid or missing logminer dictionary processes context" // *Cause: Unexpected internal error condition // *Action: 01335, 00000, "feature not yet implemented" // *Cause: // *Action: 01336, 00000, "specified dictionary file cannot be opened" // *Cause: The dictionary file or directory does not exist or is inaccessible. // *Action: Make sure that the dictionary file and directory exist and are // accessible. 01337, 00000, "log file has a different compatibility version" // *Cause: The logfile has a different compatibility version then the rest // of the logfile in the session" // *Action: Make sure that the logfile has the same compatibility version // as the rest of the logfiles in the session. // 01338, 00000, "Other process is attached to LogMiner session" // *Cause: Can not do this when other process is attached to LogMiner session. // *Action: 01339, 0000, "LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary" // *Cause: Unexpected result while accessing system catalog metadata. // *Action: Check the alert log. 01340, 00000, "NLS error" // *Cause: Could not load NLS package. // *Action: 01341, 00000, "LogMiner out-of-memory" // *Cause: The LogMiner session requires more system resources than is // currently available. // *Action: Allocate more SGA for LogMiner. 01342, 00000, "LogMiner can not resume session due to inability of staging checkpointed data" // *Cause: Logmnr can not resume session because there is not enough SGA // memory available to read in checkpointed data. Logminer // periodically checkpoints data to enable faster crash recovery. // *Action: Specify a bigger max_sga for the given LogMiner session and // try again. 01343, 00000, "LogMiner encountered corruption in the logstream" // *Cause: Log file is missing a range of scn values. // *Action: Verify the contiguity of the scn range reprented by the log files // added to LogMiner. 01344, 00000, "LogMiner coordinator already attached" // *Cause: A coordinator process is already attached to the specified // logminer context. // *Action: Detach from the active coordinator session and retry the attach. 01345, 00000, "Must be a LogMiner coordinator process" // *Cause: A LogMiner client attempted to perform a privileged operation. // *Action: Issue the operation from the coordinator process. 01346, 00000, "LogMiner processed redo beyond specified reset log scn" // *Cause: LogMiner has detected a new branch with resetlogs scn information // prior to redo already mined. // *Action: Contact your customer support representative. 01347, 00000, "Supplemental log data no longer found" // *Cause: The source database instance producing log files for this LogMiner // session was altered to no longer log supplemental data. // *Action: Destroy this Logminer session. Re-enable supplemental log data // on the source system and create a new LogMiner session. 01348, 00000, "LogMiner testing event" // *Cause: // *Action: 01349, 00000, "LogMiner tracing event" // *Cause: // *Action: 01350, 00000, "must specify a tablespace name" // *Cause: Invocation failed to specify a valid tablespace // *Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include // the name of a valid tablespace. 01351, 00000, "tablespace given for Logminer dictionary does not exist" // *Cause: The tablespace name given as a parameter to // DBMS_LOGMNR_D.SET_TABLESPACE // does not exist. // *Action: Check spelling of the tablespace name. If spelling is correct // verify that the named tablespace has already been created. // DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace. 01352, 00000, "tablespace given for Logminer spill does not exist" // *Cause: The tablespace name given as the parameter to // DBMS_LOGMNR_D.SET_TABLESPACE // does not exist. // *Action: Check spelling of the tablespace name. If spelling is correct // verify that the named tablespace has already been created. // DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace. 01353, 00000, "existing Logminer session" // *Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while // a Logminer session(s) was active. // *Action: First cause all Logminer sessions to be closed. A Logminer // session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR // or as the result of using Oracle features such as // Data Guard SQL Apply or Streams which use Logminer. // Next, execute DBMS_LOGMNR_D.SET_TABLESPACE. 01354, 00000, "Supplemental log data must be added to run this command" // *Cause: An attempt was made to perform an operation that required // that supplemental log data be enabled. // *Action: Execute a command such as // ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; // and then reissue the command that failed with this error. 01355, 00000, "logminer tablespace change in progress" // *Cause: The tables used by logminer are in the process of being // moved to another tablespace. // *Action: Wait until the move is complete and try again. 01356, 00000, "active logminer sessions found" // *Cause: Logminer sessions are currently active. // *Action: End all logminer sessions and retry. 01358, 00000, "LogMiner version is less than mined dictionary version" // *Cause: An attempt was made to mine a LogMiner dictionary from redo logs. // The version of the Oracle database that created the logs was higher // than the Oracle database version that attempted to mine the logs. // *Action: Mine the logs using a newer version of the Oracle database having a // version number that is equal to or greater than the dictionary // version. 01360, 00000, "invalid token" // *Cause: // *Action: 01361, 00000, "global name mismatch" // *Cause : The database global name where the log file was generated did not // match the user-specified global name of the Streams Capture process. // *Action: Start a new capture process and ensure that the user-specified // global name matches that of the database that generated the log // file. // 01362, 00000, "Specified SQL_REDO_UNDO parameter is invalid" // *Cause: The specified input value for the parameter was not a valid number. // *Action: Specify a valid number and try again. // 01363, 00000, "Specified COLUMN_NAME parameter is NULL" // *Cause: NULL was specified for input value of parameter. // *Action: Specify a non-NULL value and try again. // 01364, 00000, "waiting for branch at SCN %s" // *Cause: LogMiner reader process has completed mining of physical standby // terminal logs up to the stop SCN. LogMiner reader is now waiting // for logs from the new branch. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. If there is a problem // with log transport, the files can be registered manually using the // ALTER DATABASE REGISTER LOGICAL LOGFILE statement. // 01365, 00000, "waiting for new branch registration" // *Cause: LogMiner reader process has completed mining of physical standby // terminal logs up to the stop SCN. The builder process is now // waiting for logs from the new branch to be registered before // continuing. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. If there is a problem // with log transport, the files may be registered manually using the // ALTER DATABASE REGISTER LOGICAL LOGFILE statement. // 01366, 00000, "failed to find redo logs required for terminal apply" // *Cause: LogMiner failed to find all the expected log files required // to complete the terminal apply, requested using the // FINISH APPLY clause. During terminal apply, LogMiner does not // wait for logs to be registered. It expects all logs between // the starting point and the last log on any redo branch // that it will or could mine through, to be present at the // mining site. // *Action: Examine system.logmnr_log$ to see which logs are known to // LogMiner. Then, locate or restore any missing logs and use the // ALTER DATABASE REGISTER LOGICAL LOGFILE statement to register // them. Alternatively, do not use the FINISH APPLY clause, but if // activating a logical standby, only do this when you are sure that // the missing log files can not be located and registered as this // can lead to data loss. // 01370, 00000, "Specified restart SCN is too old" // *Cause: specified restart scn is too old, logmnr could not // find a proper checkpoint. // *Action: Specify a bigger restart SCN to try again // 01371, 00000, "Complete LogMiner dictionary not found" // *Cause: One or more log files containing the LogMiner dictionary was not // found. // *Action: Add into LogMiner all log files containing the dictionary. // 01372, 00000, "Insufficient processes for specified LogMiner operation" // *Cause: The number of processes requested by the caller can not // be allocated // *Action: Increase number of parallel servers allocated to the instance // 01373, 00000, "insufficient memory for staging persistent LogMiner session" // *Cause: The maximum number of concurrent persistent LogMiner sessions // allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. // Not enough memory has been set aside at instance startup to // allocate the new LogMiner session. // *Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance. // 01374, 00000, "_log_parallelism_max greater than 1 not supported in this release" // *Cause: LogMiner does not mine redo records generated with // _log_parallelism_max set to a value greater than 1. // *Action: // 01375, 00000, "Corrupt logfile %s recovered" // *Cause: A corrupt logfile has been recovered by RFS // *Action: None. Logical Standby should automatically restart. If logfile is // still corrupt, may need to manually copy and reregister the logfile // on the standby. // 01376, 00000, "LogMiner testing event" // *Cause: // *Action: 01377, 00000, "Invalid log file block size" // *Cause: An invalid value was specified in the BLOCKSIZE clause. // *Action: Use correct syntax. 01378, 00000, "The logical block size (%s) of file %s is not compatible with the disk sector size (media sector size is %s and host sector size is %s)" // *Cause: One of the following occurred: // (1) An attempt was made to create a file. // (2) A file was moved to disks with different sector size. // *Action: Create file or move file to the proper disk. 01379, 00000, "LogMiner testing event" // *Cause: // *Action: 01380, 00000, "Instance %s (thread %s) has less than two %s block size log files" // *Cause: One of the following occurred: // (1) An attempt was made to switch to specified block size logs for // all threads. // (2) An attemp was made to open a thread. // *Action: Add log files to the thread that signals error, and try again. 01381, 00000, "Dropping log %s would leave less than two log files with block size %s for instance %s (thread %s)" // *Cause: The database was migrated to use a specified log block size. // Dropping all the logs specified would leave fewer than the required // two log files with the specified block size per enabled thread. // *Action: Either drop fewer logs or disable the thread before deleting the // logs. It may be possible to clear the log rather than drop it. 01382, 00000, "Thread %s failed to open log file %s. The log file's block size (%s) is larger than the disk sector size (%s)" // *Cause: Log file was created on bigger sector disks, and moved to smaller // sector disks. // *Action: Move the log file back to bigger sector disks. 01383, 00000, "Thread %s failed to open %s block size log file '%s' on %s sector native-mode disks" // *Cause: Log file was copied from smaller sector disks to larger sector // native-mode disks. // *Action: Move the log file back to smaller sector disks. / / 1384 - 1398 Reserved for 4K block size log file errors / / 01399, 00000, "LogMiner public event" // *Cause: // *Action: / / 1380-1399 KST tracing errors renumbered at 2480-2499 for MERGE / / 1400-1499 SQL execute phase errors / 01400, 00000, "cannot insert NULL into (%s)" // *Cause: An attempt was made to insert NULL into previously listed objects. // *Action: These objects cannot accept NULL values. 01401, 00000, "inserted value too large for column" // *Cause: The value inserted was too large for the given column. // *Action: Do not insert a value greater than what the column can hold. 01402, 00000, "view WITH CHECK OPTION where-clause violation" // *Cause: // *Action: 01403, 00000, "no data found" // *Cause: No data was found from the objects. // *Action: There was no data from the objects which may be due to end of fetch. 01404, 00000, "ALTER COLUMN will make an index too large" // *Cause: // *Action: 01405, 00000, "fetched column value is NULL" // *Cause: // *Action: 01406, 00000, "fetched column value was truncated" // *Cause: The fetched column values were truncated. // *Action: Use the right data types to avoid truncation. 01407, 00000, "cannot update (%s) to NULL" // *Cause: // *Action: 01408, 00000, "such column list already indexed" // *Cause: // *Action: 01409, 00000, "NOSORT option may not be used; rows are not in ascending order" // *Cause: Creation of index with NOSORT option when rows were not ascending. // For non-unique indexes the rowid is considered part of the index // key. Therefore, if you create an index nosort and two of the rows // in the table have the same key and are stored in ascending order, // but get split accross two extents where the dba of the first block // in the second extent is less than the dba of the last block in the // first extent, then the create index nosort may fail. // *Action: Create the index without the NOSORT option, or ensure table is // stored in one extent. 01410, 00000, "invalid ROWID" // *Cause: // *Action: 01411, 00000, "cannot store the length of column in the indicator" // *Cause: Tried to fetch a column of size more than 64K and couldn't store // the length of the column in the given indicator of size 2 bytes. // *Action: Use the new bind type with call backs to fetch the long column. 01412, 00000, "zero length not allowed for this datatype" // *Cause: The length for type 97 is 0 // *Action: Specify the correct length. 01413, 00000, "illegal value in packed decimal number buffer" // *Cause: The user buffer bound by the user as packed decimal number // contained an illegal value. // *Action: Use a legal value. 01414, 00000, "invalid array length when trying to bind array" // *Cause: An attempt was made to bind an array without either a current // array length pointer or a zero maximum array length. // *Action: Sepcify a valid length. 01415, 00000, "too many distinct aggregate functions" // *Cause: The query contains more distinct aggregates than can be processed. // The current limit is 255. // *Action: Reduce the number of distinct aggregate functions in the query. 01416, 00000, "two tables cannot be outer-joined to each other" // *Cause: // *Action: 01417, 00000, "a table may be outer joined to at most one other table" // *Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed // *Action: Check that this is really what you want, then join b and c first // in a view. 01418, 00000, "specified index does not exist" // *Cause: // *Action: 01419, 00000, "datdts: illegal format code" // *Cause: // *Action: 01420, 00000, "datstd: illegal format code" // *Cause: // *Action: 01421, 00000, "datrnd/dattrn: illegal precision specifier" // *Cause: // *Action: 01422, 00000, "exact fetch returns more than requested number of rows" // *Cause: The number specified in exact fetch is less than the rows returned. // *Action: Rewrite the query or change number of rows requested 01423, 00000, "error encountered while checking for extra rows in exact fetch" // *Cause: // *Action: See the following error and take appropriate action. 01424, 00000, "missing or illegal character following the escape character" // *Cause: The character following the escape character in LIKE pattern is // missing or not one of the escape character, '%', or '_'. // *Action: Remove the escape character or specify the missing character. 01425, 00000, "escape character must be character string of length 1" // *Cause: Given escape character for LIKE is not a character string of // length 1. // *Action: Change it to a character string of length 1. 01426, 00000, "numeric overflow" // *Cause: Evaluation of an value expression causes an overflow/underflow. // *Action: Reduce the operands. 01427, 00000, "single-row subquery returns more than one row" // *Cause: // *Action: 01428, 00000, "argument '%s' is out of range" // *Cause: // *Action: 01429, 00000, "Index-Organized Table: no data segment to store overflow row-pieces" // *Cause: No overflow segment defined. // *Action: Add overflow segment. 01430, 00000, "column being added already exists in table" // *Cause: // *Action: 01431, 00000, "internal inconsistency in GRANT command" // *Cause: // *Action: 01432, 00000, "public synonym to be dropped does not exist" // *Cause: // *Action: 01433, 00000, "synonym to be created is already defined" // *Cause: // *Action: 01434, 00000, "private synonym to be dropped does not exist" // *Cause: // *Action: 01435, 00000, "user does not exist" // *Cause: // *Action: 01436, 00000, "CONNECT BY loop in user data" // *Cause: // *Action: 01437, 00000, "cannot have join with CONNECT BY" // *Cause: // *Action: 01438, 00000, "value larger than specified precision allowed for this column" // *Cause: When inserting or updating records, a numeric value was entered // that exceeded the precision defined for the column. // *Action: Enter a value that complies with the numeric column's precision, // or use the MODIFY option with the ALTER TABLE command to expand // the precision. 01439, 00000, "column to be modified must be empty to change datatype" // *Cause: // *Action: 01440, 00000, "column to be modified must be empty to decrease precision or scale" // *Cause: // *Action: 01441, 00000, "cannot decrease column length because some value is too big" // *Cause: // *Action: 01442, 00000, "column to be modified to NOT NULL is already NOT NULL" // *Cause: // *Action: 01443, 00000, "internal inconsistency; illegal datatype in resultant view column" // *Cause: // *Action: 01444, 00000, "internal inconsistency; internal datatype maps to invalid external type" // *Cause: // *Action: 01445, 00000, "cannot select ROWID from, or sample, a join view without a key-preserved table" // *Cause: // *Action: 01446, 00000, "cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc." // *Cause: // *Action: 01447, 00000, "ALTER TABLE does not operate on clustered columns" // *Cause: // *Action: 01448, 00000, "index must be dropped before changing to desired type" // *Cause: // *Action: 01449, 00000, "column contains NULL values; cannot alter to NOT NULL" // *Cause: // *Action: 01450, 00000, "maximum key length (%s) exceeded" // *Cause: // *Action: 01451, 00000, "column to be modified to NULL cannot be modified to NULL" // *Cause: the column may already allow NULL values, the NOT NULL constraint // is part of a primary key or check constraint. // *Action: if a primary key or check constraint is enforcing the NOT NULL // constraint, then drop that constraint. 01452, 00000, "cannot CREATE UNIQUE INDEX; duplicate keys found" // *Cause: // *Action: 01453, 00000, "SET TRANSACTION must be first statement of transaction" // *Cause: self-evident // *Action: commit (or rollback) transaction, and re-execute 01454, 00000, "cannot convert column into numeric datatype" // *Cause: // *Action: 01455, 00000, "converting column overflows integer datatype" // *Cause: // *Action: 01456, 00000, "may not perform insert/delete/update operation inside a READ ONLY transaction" // *Cause: A non-DDL insert/delete/update or select for update operation // was attempted // *Action: commit (or rollback) transaction, and re-execute 01457, 00000, "converting column overflows decimal datatype" // *Cause: // *Action: 01458, 00000, "invalid length inside variable character string" // *Cause: // *Action: 01459, 00000, "invalid length for variable character string" // *Cause: // *Action: 01460, 00000, "unimplemented or unreasonable conversion requested" // *Cause: // *Action: 01461, 00000, "can bind a LONG value only for insert into a LONG column" // *Cause: // *Action: 01462, 00000, "cannot insert string literals longer than 4000 characters" // *Cause: // *Action: 01463, 00000, "cannot modify column datatype with current constraint(s)" // *Cause: An attempt was made to modify the datatype of column which // has referential constraints; or has check constraints which // only allows changing the datatype from CHAR to VARCHAR or // vise versa. // *Action: Remove the constraint(s) or do not perform the offending operation. 01464, 00000, "circular grant (granting to grant ancestor) of table or view" // *Cause: // *Action: 01465, 00000, "invalid hex number" // *Cause: // *Action: 01466, 00000, "unable to read data - table definition has changed" // *Cause: Query parsed after tbl (or index) change, and executed // w/old snapshot // *Action: commit (or rollback) transaction, and re-execute 01467, 00000, "sort key too long" // *Cause: // *Action: 01468, 00000, "a predicate may reference only one outer-joined table" // *Cause: // *Action: 01469, 00000, "PRIOR can only be followed by a column name" // *Cause: Attempting to specify "PRIOR " 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: / / Copyright (c) Oracle Corporation 1999, 2001. All rights reserved. / / NAME / e1500.msg / DESCRIPTION / Error messages for Oracle / NOTES / Language : American / Character set : US7ASCII / / List of ORACLE errors / / This file is converted to header/message files using lmsgen.c. / / The first col is the ORACLE error number. / The second column is reserved and must (for now) be x00000. / The remainder of the line is the error text (max 76 characters). / / Adding an error: / Check out this file, add the error, and check it back in. / Error numbers should always be ordered. / The second column should always be x00000. / Pseudo-error debugging events: / Error codes 10000 .. 10999 are reserved for debug event codes / that are not really errors. / / MODIFIED / mabhatta 04/20/09 - rename us.oracle.com to example.com / jjlee 03/03/09 - edit ORA-1516 / ssonawan 11/17/08 - bug 7503761: edit 1931 / ptearle 02/05/09 - add documentation for ORA-2014 / kquinn 02/13/09 - 5687266: ensure ora-1722 is documented / yohu 11/20/08 - update 2051 / nmacnaug 10/16/08 - change error message / madhanap 09/12/08 - bug 7387947: removing %s and %d from timezone region / errors / mabhatta 08/06/08 - edit 1554 / yuli 05/28/08 - edit 1679 / mbastawa 03/26/08 - add 01805 / dapte 03/12/08 - add documentation for err-1795 / dkoppar 03/11/08 - #(6835153) add err mesg for divide by zero / yohu 02/19/08 - change ORA-01640 to for in-doubt txn only / yohu 03/25/07 - more information for ORA-2051 / mabhatta 11/30/06 - changing 1535 message to include rbs using _SYSSMU / prefix / akruglik 09/17/06 - modify Cause of msg 1752 to exclude read-only views / since an attempt to delete from a read-only view / will now be reported as msg 42399 / akruglik 09/12/06 - replace EDITIONING VIEW with Editioning View / akruglik 09/01/06 - Column Map Views got rechristened as Editioning / Views / akruglik 05/10/06 - correct text of CAUSE for msg 1702 per request from / errors_us / akruglik 03/01/06 - Add a mention of use of a view in a definition of an / Editioning View among causes of msg 1702 / yohu 11/28/05 - change 2079 / bemeng 04/21/05 - explicitly specify unit of size for out-of-space msg / gmulagun 02/14/05 - bug 4177854 change 1999 / nireland 02/24/05 - Explicitly specify unit of size. #4050567 / qyu 11/15/04 - change 1874 / mdilman 09/16/04 - change 1566 to more generic / nmanappa 05/13/04 - change message 1994 for password file / molagapp 04/25/04 - change 1537 / rjenkins 07/08/03 - add a comment / lilin 12/16/02 - Eliminate Thread Number add/change error messages / jarnett 11/21/02 - bug 2634530 - delete reference to / distributed_transactions / ddas 10/16/02 - OPTIMIZER_GOAL parameter is obsolete / asundqui 09/05/02 - update error 1506 to only mention init.ora parameter / swerthei 09/20/02 - block change tracking / sdizdar 09/03/02 - reuse 1586 / mjstewar 09/29/02 - Add flashback cause to ORA-1588 / jmuller 08/08/02 - Bug 2462292: clarify ORA-2064 documentation / mjstewar 07/24/02 - Add Flashback action to ORA-1507 / yuli 04/15/02 - remove 1576 / snutakki 10/24/01 - 1970332: Add new error mesg 1560 / mjaeger 07/05/01 - bug 479696: 01516: alter db datafile/tempfile /------------------------------------------------------------------------------- / 1500 - 1699 V6 Execution errors / 01500, 00000, "failure in getting date/time" // *Cause: During create database or alter tablespace, there was a failure // in getting the date and time. // *Action: Contact your customer support representative. 01501, 00000, "CREATE DATABASE failed" // *Cause: An error occurred during create database // *Action: See accompanying errors. 01502, 00000, "index '%s.%s' or partition of such index is in unusable state" // MERGE: 1489 RENUMBERED TO 1502 // *Cause: An attempt has been made to access an index or index partition // that has been marked unusable by a direct load or by a DDL // operation // *Action: DROP the specified index, or REBUILD the specified index, or // REBUILD the unusable index partition 01503, 00000, "CREATE CONTROLFILE failed" // *Cause: An error occurred during CREATE CONTROLFILE // *Action: See accompanying errors. 01504, 00000, "database name '%s' does not match parameter db_name '%s'" // *Cause: The name in a database create or mount does not match the name // given in the INIT.ORA parameter db_name. // *Action: correct or omit one of the two names. 01505, 00000, "error in adding log files" // *Cause: During create or alter database, error(s) occurred when // adding new log files. // *Action: Check error stack for detailed error information. 01506, 00000, "missing or illegal database name" // *Cause: No db_name INIT.ORA aprameter was specified. // *Action: The database name must be given in the db_name // INIT.ORA parameter. 01507, 00000, "database not mounted" // *Cause: A command was attempted that requires the database to be mounted. // *Action: If you are using the ALTER DATABASE statement via the SQLDBA // startup command, specify the MOUNT option to startup; // else if you are directly doing an ALTER DATABASE DISMOUNT, // do nothing; else specify the MOUNT option to ALTER DATABASE. // If you are doing a backup or copy, you must first mount the // desired database. // If you are doing a FLASHBACK DATABASE, you must first mount // the desired database. 01508, 00000, "cannot create database; error in file '%s' at line %s" // *Cause: CREATE DATABASE was unable to process the specified file. // *Action: Check the offending line in the specified file. 01509, 00000, "specified name '%s' does not match actual '%s'" // *Cause: The database name specified in ALTER DATABASE does not // match the name of the currently mounted database. // *Action: Correct the database name spelling or DISMOUNT the mounted // database. 01510, 00000, "error in deleting log files" // *Cause: During ALTER DATABASE, an error occurred while dropping // log files. // *Action: Check the error stack for detailed error information. 01511, 00000, "error in renaming log/data files" // *Cause: An error occurred during the ALTER DATABASE RENAME FILE command. // *Action: Check the error stack for detailed error information. 01512, 00000, "error renaming log file %s - new file %s not found" // *Cause: An attempt to change a log file's name in the control file // failed because no file was found with the new name. // *Action: Make sure that the log file has been properly renamed by the // operating system and retry. 01513, 00000, "invalid current time returned by operating system" // *Cause: The operating system returned a time that was not between // 1988 and 2121. // *Action: Correct the time kept by the operating system. 01514, 00000, "error in log specification: no such log" // *Cause: A log file name, or list of member names, did not correspond // to an existing log. // *Action: Specify an existing log file. 01515, 00000, "error dropping log group %s: no such log" // *Cause: ALTER DATABASE is attempting to drop a log file which // is not known to the database control file. // *Action: Specify the name of an existing log file. 01516, 00000, "nonexistent log file, data file, or temporary file \"%s\"" // *Cause: An attempt was made to use ALTER DATABASE to rename // a log file, data file, or temporary file; or to change attributes // of a data file or temporary file (for example, resize, autoextend, // online or offline); or to re-create or move a data file. // The attempt failed because the specified file // is not known to the database's control file // or is not of a type supported by the request. // *Action: Specify the name or number of an existing file // of the correct type, as appropriate. // Check the relevant V$ table for a list of possible files. 01517, 00000, "log member: '%s'" // *Cause: Used to print member names // *Action: See top level error for information 01518, 00000, "CREATE DATABASE must specify more than one log file" // *Cause: Only one log file was specified in the CREATE DATABASE statement. // *Action: Specify at least two log files. 01519, 00000, "error while processing file '%s' near line %s" // *Cause: CREATE DATABASE encountered a problem while processing // specified file. The specified file is bad. // *Action: Retry your system installation procedure or contact // your customer support representative. 01520, 00000, "number of data files to add (%s) exceeds limit of %s" // *Cause: CREATE TABLESPACE statement specifies more files than // is permitted for this database. // *Action: Use fewer files or re-create the database with a // larger value of MAXDATAFILES. 01521, 00000, "error in adding data files" // *Cause: During CREATE or ALTER TABLESPACE, an error was detected // while adding data files. // *Action: Check the error stack for detailed error information. 01522, 00000, "file '%s' to be renamed does not exist" // *Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not // found in the database control file. // *Action: Specify the correct file name. 01523, 00000, "cannot rename data file to '%s' - file already part of database" // *Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, // the new name of a file is already present in the control file. // *Action: Rename the file to a name not already being used as part of // the database. 01524, 00000, "cannot create data file as '%s' - file already part of database" // *Cause: During ALTER DATABASE CREATE DATAFILE, // the new name of a file is already present in the control file. // *Action: Create the file as a name not already being used as part of // the database. 01525, 00000, "error in renaming data files" // *Cause: An error occurred when renaming files as part of ALTER TABLESPACE. // *Action: Check the error stack for detailed information. // All files are renamed except for those mentioned in the // error stack. 01526, 00000, "error in opening file '%s'" // *Cause: CREATE DATABASE was not able to open the specified file. // This is probably due to a system installation error. // *Action: Retry your system installation procedure or contact // your customer support representative. 01527, 00000, "error while reading file" // *Cause: CREATE DATABASE was not able to read the specified file. // This is probably due to a system installation error. // *Action: Retry your system installation procedure or contact // your customer support representative. 01528, 00000, "EOF while processing SQL statement" // *Cause: CREATE DATABASE unexpectedly hit EOF while reading the // specified file. The sql.bsq file is bad. // *Action: Retry your system installation procedure or contact // your customer support representative. 01529, 00000, "error closing file '%s'" // *Cause: CREATE DATABASE was not able to close the specified file. // *Action: Retry your system installation procedure or contact // your customer support representative. 01530, 00000, "a database already mounted by the instance" // *Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount // a database on an instance in which a database is or has previously // been mounted. // *Action: If you wish to mount the database, shutdown the instance // and then startup the instance and retry the operation. 01531, 00000, "a database already open by the instance" // *Cause: During ALTER DATABASE, an attempt was made to open // a database on an instance for which there is already // an open database. // *Action: If you wish to open a new database on the instance, first // shutdown the instance and then startup the instance and // retry the operation. 01532, 00000, "cannot create database; instance being started elsewhere" // *Cause: During CREATE DATABASE, another user appears to be // simultaneously altering the instance. // *Action: Make sure no one else is simultaneously altering the // instance. If no one is, contact your customer support // representative; otherwise, retry the operation. 01533, 00000, "cannot rename file '%s'; file does not belong to tablespace" // *Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not // found in the argument tablespace. // *Action: Specify the correct file name or the correct tablespace name. 01534, 00000, "rollback segment '%s' doesn't exist" // *Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified // rollback segment name is unknown. // *Action: Use the correct rollback segment name. 01535, 00000, "rollback segment '%s' already exists or given name has prefix _SYSSMU" // *Cause: Specified rollback segment already exists or given name starts with // _SYSSMU. // *Action: Use a different name. Note that _SYSSMU is an illegal prefix to // an RBU segment. 01536, 00000, "space quota exceeded for tablespace '%s'" // *Cause: The space quota for the segment owner in the tablespace has // been exhausted and the operation attempted the creation of a // new segment extent in the tablespace. // *Action: Either drop unnecessary objects in the tablespace to reclaim // space or have a privileged user increase the quota on this // tablespace for the segment owner. 01537, 00000, "cannot add file '%s' - file already part of database" // *Cause: During CREATE or ALTER TABLESPACE, a file being added is already // part of the database. // *Action: Use a different file name. 01538, 00000, "failed to acquire any rollback segment" // *Cause: Failed to acquire any rollback segment during startup in shared mode // *Action: Startup in exclusive mode to create one more public segment or // specify available private segments in the INIT.ORA parameter // rollback_segments_required, then startup in shared mode 01539, 00000, "tablespace '%s' is not online" // *Cause: Failed to either make a tablespace read-only or offline because // it is not online. A tblespace must be online before it can // become read-only or offline normal. // *Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY // options to force all files offline. Bring the tablespace online // before making it read-only. 01540, 00000, "tablespace '%s' is not offline" // *Cause: Failed to bring a tablespace online because it is not offline // *Action: Check the status of the tablespace 01541, 00000, "system tablespace cannot be brought offline; shut down if necessary" // *Cause: Tried to bring system tablespace offline // *Action: Shutdown if necessary to do recovery 01542, 00000, "tablespace '%s' is offline, cannot allocate space in it" // *Cause: Tried to allocate space in an offline tablespace // *Action: Bring the tablespace online or create the object in other // tablespace 01543, 00000, "tablespace '%s' already exists" // *Cause: Tried to create a tablespace which already exists // *Action: Use a different name for the new tablespace 01544, 00000, "cannot drop system rollback segment" // *Cause: Tried to drop system rollback segment // *Action: None 01545, 00000, "rollback segment '%s' specified not available" // *Cause: Either: // 1) An attempt was made to bring a rollback segment online that is // unavailable during startup; for example, the rollback segment // is in an offline tablespace. // 2) An attempt was made to bring a rollback segment online that is // already online. This is because the rollback segment is // specified twice in the ROLLBACK_SEGMENTS parameter in the // initialization parameter file or the rollback segment is already // online by another instance. // 3) An attempt was made to drop a rollback segment that is // currently online. // 4) An attempt was made to alter a rollback segment that is // currently online to use unlimited extents. // 5) An attempt was made to online a rollback segment that is // corrupted. This is because the rollback is specified in // _corrupted_rollback_segments parameter in initialization // parameter file. // *Action: Either: // 1) Make the rollback segment available; for example, bring an // offline tablespace online. // 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name // is a duplicate or if another instance has already acquired the // rollback segment. // 3) Bring the rollback segment offline first. This may involve // waiting for the active transactions to finish, or, if the // rollback segment needs recovery, discover which errors are // holding up the rolling back of the transactions and take // appropriate actions. // 4) Same as 3). // 5) Remove the name from the _corrupted_rollback_segments parameter. 01546, 00000, "tablespace contains active rollback segment '%s'" // *Cause: Tried to make a tablespace that contains active rollback segment(s) // offline or read-only // *Action: Shutdown instances that use the active rollback segments in the // tablespace and then make the tablespace offline or read-only 01547, 00000, "warning: RECOVER succeeded but OPEN RESETLOGS would get error below" // *Cause: Media recovery with one of the incomplete recovery options ended // without error. However, if the ALTER DATABASE OPEN RESETLOGS command // were attempted now, it would fail with the specified error. // The most likely cause of this error is forgetting to restore one or // more datafiles from a sufficiently old backup before executing the // incomplete recovery. // *Action: Rerun the incomplete media recovery using different datafile // backups, a different control file, or different stop criteria. 01548, 00000, "active rollback segment '%s' found, terminate dropping tablespace" // *Cause: Tried to drop a tablespace that contains active rollback segment(s) // *Action: Shutdown instances that use the active rollback segments in the // tablespace and then drop the tablespace 01549, 00000, "tablespace not empty, use INCLUDING CONTENTS option" // *Cause: Tried to drop a non-empty tablespace // *Action: To drop all the objects in the tablespace, use the INCLUDING // CONTENTS option 01550, 00000, "cannot drop system tablespace" // *Cause: Tried to drop system tablespace // *Action: None 01551, 00000, "extended rollback segment, pinned blocks released" // *Cause: Doing recursive extent of rollback segment, trapped internally // by the system // *Action: None 01552, 00000, "cannot use system rollback segment for non-system tablespace '%s'" // *Cause: Tried to use the system rollback segment for operations involving // non-system tablespace. If this is a clone database then this will // happen when attempting any data modification outside of the system // tablespace. Only the system rollback segment can be online in a // clone database. // *Action: Create one or more private/public segment(s), shutdown and then // startup again. May need to modify the INIT.ORA parameter // rollback_segments to acquire private rollback segment. If this is // a clone database being used for tablspace point in time recovery // then this operation is not allowed. If the non-system tablespace // has AUTO segment space management, then create an undo tablespace. 01553, 00000, "MAXEXTENTS must be no smaller than the %s extents currently allocated" // *Cause: The number of extents allocated is greater than the MAXEXTENTS // specified. // *Action: Specify a larger MAXEXTENTS value. 01554, 00000, "transaction concurrency limit reached reason:%s params:%s, %s" // *Cause: Too many concurrent transactions // *Action: Shutdown the system, modify the INIT.ORA parameters transactions, // rollback_segments or rollback_segments_required, then // startup again. 01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small" // *Cause: rollback records needed by a reader for consistent read are // overwritten by other writers // *Action: If in Automatic Undo Management mode, increase undo_retention // setting. Otherwise, use larger rollback segments 01556, 00000, "MINEXTENTS for rollback segment must be greater than 1" // *Cause: Specified MINEXTENTS of less than 2 for rollback segment // *Action: Specify larger MINEXTENTS 01557, 00000, "rollback segment extents must be at least %s blocks" // *Cause: Specified extent of less than minimum size for rollback segment // *Action: Specify larger extents 01558, 00000, "out of transaction ID's in rollback segment %s" // *Cause: All the available transaction id's have been used // *Action: Shutdown the instance and restart using other rollback segment(s), // then drop the rollback segment that has no more transaction id's. 01559, 00000, "MAXEXTENTS for rollback segment must be greater than 1" // *Cause: Specified MAXEXTENTS of less than 2 for rollback segment // *Action: Specify larger MAXEXTENTS 01560, 00000, "LIKE pattern contains partial or illegal character" // *Cause: like pattern is not formed correctly // *Action: make sure like pattern is specified correctly 01561, 00000, "failed to remove all objects in the tablespace specified" // *Cause: Failed to remove all objects when dropping a tablespace // *Action: Retry the drop tablespace until all objects are dropped 01562, 00000, "failed to extend rollback segment number %s" // *Cause: Failure occurred when trying to extend rollback segment // *Action: This is normally followed by another error message that caused // the failure. You may take the rollback segment offline to perform // maintainence. Use the alter rollback segment offline command // to take the rollback segment offline. 01563, 00000, "rollback segment is PUBLIC, need to use the keyword PUBLIC" // *Cause: Did not use the keyword PUBLIC to identified public rollback segment // *Action: Use the keyword PUBLIC when identifying public rollback segment 01564, 00000, "rollback segment is not PUBLIC" // *Cause: The rollback segment segment identified is not public // *Action: Do not use the keyword PUBLIC when identifying private rollback // segment 01565, 00000, "error in identifying file '%s'" // *Cause: An error occurred while trying to identify a file. // *Action: Check the error stack for detailed information. 01566, 00000, "file specified more than once in ALTER DATABASE" // *Cause: The list of files supplied to the command contained at least one // duplicate. // *Action: Remove the duplicate file specification and retry. 01567, 00000, "dropping log %s would leave less than 2 log files for instance %s (thread %s)" // *Cause: Dropping all the logs specified would leave fewer than the required // two log files per enabled thread. // *Action: Either drop fewer logs or disable the thread before deleting the // logs. It may be possible to clear the log rather than drop it. 01568, 00000, "cannot set space quota on PUBLIC" // MERGE: 1568 PROBABLY OBSOLETE // *Cause: Trying to set space quota on a tablespace for PUBLIC. // *Action: If trying to grant system-wide or tablespace-wide space priviledges // to all users, use GRANT RESOURCE [ON ] TO PUBLIC. 01569, 00000, "data file too small for system dictionary tables" // *Cause: The datafile specified during creation of the database is too // small to hold the system dictionary tables. // *Action: Recreate the database by specifying a larger file or more files. 01570, 00000, "MINEXTENTS must be no larger than the %s extents currently allocated" // *Cause: The number of extents allocated is smaller than the MINEXTENTS // specified. // *Action: Specify a smaller MINEXTENTS value. 01571, 00000, "redo version %s incompatible with ORACLE version %s" // *Cause: This software version can not read the current redo logs, and // either crash recovery is required or there are offline database // files that need media recovery. If a file name is listed then // it needs media recovery. // *Action: Shutdown and startup using the compatible software. Do any required // media recovery, and open the database. Shutdown and then startup // using current software. If the file is going to be dropped then // take it offline with the DROP option to skip this check. 01572, 00000, "rollback segment '%s' cannot be brought online, %s extents exceeded" // *Cause: The number of extents in the rollback segment exceeds the hard limit. // It cannot be brought online for writing. // *Action: Drop and recreate the rollback segment. 01573, 00000, "shutting down instance, no further change allowed" // *Cause: Some process tries to make changes while the db is being shutdown // *Action: None 01574, 00000, "maximum number of concurrent transactions exceeded" // *Cause: the limit on the number of concurrent transactions has been hit // *Action: shutdown the system, increase the INIT.ORA parameter 'transactions' // , and then restart the system. 01575, 00000, "timeout waiting for space management resource" // *Cause: failed to acquire necessary resource to do space management. // *Action: Retry the operation. 01576, 00000, "The instance %s is not enabled" // *Cause: The thread associated with instance is not enabled. // *Action: Enable the thread associated with the instance using // ALTER DATABASE ENABLE INSTANCE command. 01577, 00000, "cannot add log file '%s' - file already part of database" // *Cause: During CREATE or ALTER DATABASE, a file being added is already // part of the database. // *Action: Use a different file name. 01578, 00000, "ORACLE data block corrupted (file # %s, block # %s)" // *Cause: The data block indicated was corrupted, mostly due to software // errors. // *Action: Try to restore the segment containing the block indicated. This // may involve dropping the segment and recreating it. If there // is a trace file, report the errors in it to your ORACLE // representative. 01579, 00000, "write error occurred during recovery" // *Cause: A write error occurred during recovery // *Action: Consult trace files for the nature of the write error, and // correct error. 01580, 00000, "error creating control backup file %s" // *Cause: An operating system error occurred while attempting to create a // control file backup. // *Action: Check the error stack for more detailed information 01581, 00000, "attempt to use rollback segment (%s) new extent (%s) which is being allocated" // *Cause: Undo generated to extend a rollback segment run out of current // undo block space and is attempting to write into the new extent // which has not been completely allocated. // *Action: The rollback segment extending will be rollbacked by the system, // no more extension will be possible untill the next extent is // freed up by rolling back or committing other transactions. 01582, 00000, "unable to open control file for backup" // *Cause: An operating system error occurred while attempting to open a // control file for backup. // *Action: Check the error stack for more detailed information 01583, 00000, "unable to get block size of control file to be backed up" // *Cause: An operating system error occurred while attempting to // get the block size of a control file for backup. // *Action: Check the error stack for more detailed information 01584, 00000, "unable to get file size of control file to be backed up" // *Cause: An operating system error occurred while attempting to // get the file size of a control file for backup. // *Action: Check the error stack for more detailed information 01585, 00000, "error identifying backup file %s" // *Cause: An operating system error occurred when attempting to identify // the file to be used for control file backup. // *Action: Check the error stack for more detailed information 01586, 00000, "database must be mounted EXCLUSIVE and not open for this operation" // *Cause: Attempting to DROP DATABASE when the database is not mounted // EXCLUSIVE. // *Action: Mount the database in EXCLUSIVE mode. 01587, 00000, "error during control file backup file copy" // *Cause: // // *Action: 01588, 00000, "must use RESETLOGS option for database open" // *Cause: An earlier attempt to open the database with the RESETLOGS option // did not complete, or recovery was done with a control file backup, // or a FLASHBACK DATABASE was done. // *Action: Use the RESETLOGS option when opening the database. 01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open" // *Cause: Either incomplete or backup control file recovery has been // performed. After these types of recovery you must specify either // the RESETLOGS option or the NORESETLOGS option to open your // database. // *Action: Specify the appropriate option. 01590, 00000, "number of segment free list (%s) exceeds maximum of %s" // *Cause: storage parameter FREELIST GROUPS is too large. // *Action: Reduce storage parameters FREELIST GROUPS 01591, 00000, "lock held by in-doubt distributed transaction %s" // *Cause: Trying to access resource that is locked by a dead two-phase commit // transaction that is in prepared state. // *Action: DBA should query the pending_trans$ and related tables, and attempt // to repair network connection(s) to coordinator and commit point. // If timely repair is not possible, DBA should contact DBA at commit // point if known or end user for correct outcome, or use heuristic // default if given to issue a heuristic commit or abort command to // finalize the local portion of the distributed transaction. 01592, 00000, "error converting Version 7 rollback segment (%s) to Oracle 8 format" // *Cause: Look at the accompanying internal error; Version 7 database may not // have shutdown cleanly. // *Action: Investigate the internal error; may have to reload the Version 7 // *Action: Investigate the internal error; may have to reload the Version 7 // database (from backup) and shutdown the database cleanly. 01593, 00000, "rollback segment optimal size (%s blks) is smaller than the computed initial size (%s blks)" // *Cause: Specified OPTIMAL size is smaller than the cumulative size of the // initial extents during create rollback segment. // *Action: Specify a larger OPTIMAL size. 01594, 00000, "attempt to wrap into rollback segment (%s) extent (%s) which is being freed" // *Cause: Undo generated to free a rollback segment extent is attempting // to write into the same extent due to small extents and/or too // many extents to free // *Action: The rollback segment shrinking will be rollbacked by the system; // increase the optimal size of the rollback segment. 01595, 00000, "error freeing extent (%s) of rollback segment (%s))" // *Cause: Some error occurred while freeing inactive rollback segment extents. // *Action: Investigate the accompanying error. 01596, 00000, "cannot specify system in %s parameter" // *Cause: The system rollback segment is specified in the INIT.ORA parameter // referred to in the error message // *Action: change the INIT.ORA parameter 01597, 00000, "cannot alter system rollback segment online or offline" // *Cause: Tried to online or offline the system rollback segment // *Action: None 01598, 00000, "rollback segment '%s' is not online" // *Cause: Could have been taken offline before by DBA or cleaned up // by SMON. // *Action: Check the status of rollback segment in undo$ or dba_rollback_segs // to make sure the rollback segment is actually online. 01599, 00000, "failed to acquire rollback segment (%s), cache space is full" // *Cause: the amount statically allocated is not enough based on // max_rollback_segments parameter. // *Action: For now take another rollback segment offline or increase the // parameter max_rollback_segments 01600, 00000, "at most one \"%s\" in clause \"%s\" of %s" // *Cause: The INIT.ORA parameter was mis-specified. // *Action: Correct the INIT.ORA parameter and restart the instance. 01601, 00000, "illegal bucket size in clause \"%s\" of %s" // *Cause: The bucket size was invalid for this parameter. // *Action: Correct the INIT.ORA parameter and restart the instance. 01603, 00000, "illegal grouping size in clause \"%s\" of %s" // *Cause: The grouping size was invalid for this parameter. // *Action: Correct the INIT.ORA parameter and restart the instance. 01604, 00000, "illegal number range in clause \"%s\" of %s" // *Cause: The number range was invalid for this parameter. // *Action: Correct the INIT.ORA parameter and restart the instance. 01605, 00000, "missing numbers in clause \"%s\" of %s" // *Cause: The numbers were missing for this parameter. // *Action: Correct the INIT.ORA parameter and restart the instance. 01606, 00000, "parameter not identical to that of another mounted instance" // *Cause: A parameter was different on two instances. // *Action: Modify the initialization parameter and restart. 01607, 00000, "cannot add logfile to the specified instance" // *Cause: The limit on the number of instances supported by the // control file has been reached. // *Action: Use an instance name supported by the control file, or resize // the thread record and/or checkpoint progress record secions of the // control file. 01608, 00000, "cannot bring rollback segment '%s' online, its status is (%s)" // *Cause: Could have been brought online before by DBA or left as a result // of process crash. // *Action: Check the status of rollback segment in undo$ or dba_rollback_segs 01609, 00000, "log %s is the current log for thread %s - cannot drop members" // *Cause: A member of the current log for a thread cannot be dropped. // *Action: If the thread is opened, request a log switch by the instance // that is using it. If it is not open, disable the thread, manually // archive the log, or clear it. 01610, 00000, "recovery using the BACKUP CONTROLFILE option must be done" // *Cause: Either an earlier database recovery session specified BACKUP // CONTROLFILE, or the control file was recreated with the RESETLOGS // option, or the control file being used is a backup control file. // After that only BACKUP CONTROLFILE recovery is allowed // and it must be followed by a log reset at the next database open. // *Action: Perform recovery using the BACKUP CONTROFILE option. 01611, 00000, "thread number %s is invalid - must be between 1 and %s" // *Cause: A thread number in a command is greater than the number of threads // supported by the control file. // *Action: Use a thread number that is valid, or resize the thread record // and/or checkpoint progress record sections of the control file. 01612, 00000, "instance %s (thread %s) is already enabled" // *Cause: An attempt was made to enable a thread that is already enabled. // *Action: Either use this thread or enable another thread. 01613, 00000, "instance %s (thread %s) only has %s logs - at least 2 logs required to enable." // *Cause: The thread cannot be enabled because it only has two online log // files associated with it. // *Action: Add logs to the thread or pick another thread to enable 01614, 00000, "instance %s (thread %s) is busy - cannot enable" // *Cause: The mount enqueue for the thread could not be acquired when // attempting to enable the thread. This probably means that another // process has already started enabling this thread. // *Action: Wait and try again, or find another thread to enable. 01615, 00000, "instance %s (thread %s) is mounted - cannot disable" // *Cause: Some instance, possibly this one, has allocated the thread for its // use. The thread can not be disabled while in use. // *Action: Shut the instance down cleany using the thread. 01616, 00000, "instance %s (thread %s) is open - cannot disable" // *Cause: The thread is not closed. The last instance to use the thread died // leaving the thread open. A thread cannot be disabled until it is // closed. It is still required for crash or instance recovery. // *Action: If the database is open, instance recovery should close the thread // soon - wait a few minutes. Otherwise open the database - crash // recovery will close the thread. 01617, 00000, "cannot mount: %s is not a valid thread number" // *Cause: The INIT.ORA parameter "thread" is not between 1 and the // number of threads allowed by the control file. // *Action: Shut down the instance, change the INIT.ORA parameter and // startup, or resize the thread record and/or checkpoint progress // record sections of the control file. 01618, 00000, "redo thread %s is not enabled - cannot mount" // *Cause: The INIT.ORA parameter "thread" requests a thread that is not // enabled. A thread must be enabled before it can be mounted. // *Action: Shutdown the instance, change the INIT.ORA parameter and startup // mounting a different thread. If the database is open in another // instance then the thread may be enabled. 01619, 00000, "thread %s is mounted by another instance" // *Cause: The INIT.ORA parameter "thread" requests a thread that has been // mounted by another instance. Only one instance may use a thread. // *Action: Shutdown the instance, change the INIT.ORA parameter and startup // mounting a different thread. 01620, 00000, "no public threads are available for mounting" // *Cause: The INIT.ORA parameter "thread" is zero, its default value. // There are no threads which have been publicly enabled, and not // mounted. // *Action: Shutdown the instance, change the INIT.ORA parameter to a thread // which is privately enabled and not mounted. If the database is // open in another instance, then a thread may be publicly enabled. 01621, 00000, "cannot rename member of current log if database is open" // *Cause: This is a rename command for a member of the current log for // an open thread. If the database is open anywhere, the log may be // in use, so the rename cannot be done. // *Action: Wait until the log is not current, or mount the database // exclusively. 01622, 00000, "thread number must be specified - default not specific" // *Cause: The thread was not specified when adding a log, and the currently // mounted thread was chosen by default at mount time. Since the // current thread was not specified explicitly the user cannot know // which thread the log will be added to. // *Action: Explicitly specify the thread number either in the INIT.ORA // parameter "thread", or in the add command. 01623, 00000, "log %s is current log for instance %s (thread %s) - cannot drop" // *Cause: A thread's current log cannot be dropped even if the thread is // closed. A disabled thread usually does not have a current log, // but a half completed disable may need to be disabled again. // *Action: If the database is not open then disable the thread. If the // database is open and an instance has the thread open, then the // instance can be requested to switch logs. If the database is // closed the log can be archived or cleared to force a switch. 01624, 00000, "log %s needed for crash recovery of instance %s (thread %s)" // *Cause: A log cannot be dropped or cleared until the thread's checkpoint // has advanced out of the log. // *Action: If the database is not open, then open it. Crash recovery will // advance the checkpoint. If the database is open force a global // checkpoint. If the log is corrupted so that the database cannot // be opened, it may be necessary to do incomplete recovery until // cancel at this log. 01625, 00000, "rollback segment '%s' does not belong to this instance" // *Cause: Trying to shrink or take a rollback segment offline that does not // belong to this instance. // *Action: 01626, 00000, "rollback segment number '%s' cannot handle more transactions" // *Cause: Too many transactions in this segment. // *Action: Choose a different rollback segment, or reduce the number // of concurrent transactions. 01627, 00000, "rollback segment number '%s' is not online" // *Cause: Could have been taken offline before by DBA or cleaned up // by SMON. // *Action: Check the status of rollback segment in undo$ or dba_rollback_segs // to make sure the rollback segment is actually online. 01628, 00000, "max # extents (%s) reached for rollback segment %s" // *Cause: An attempt was made to extend a rollback segment that was // already at the MAXEXTENTS value. // *Action: If the value of the MAXEXTENTS storage parameter is less than // the maximum allowed by the system, raise this value. 01629, 00000, "max # extents (%s) reached saving undo for tablespace %s" // *Cause: Save undo for the offline tablespace at max extents // *Action: Check the storage parameters for the system tablespace. The // tablespace needs to be brought back online so the undo can be // applied . 01630, 00000, "max # extents (%s) reached in temp segment in tablespace %s" // *Cause: A temp segment tried to extend past max extents. // *Action: If maxextents for the tablespace is less than the the system // maximum, you can raise that. Otherwise, raise pctincrease for the // tablespace 01631, 00000, "max # extents (%s) reached in table %s.%s" // *Cause: A table tried to extend past maxextents // *Action: If maxextents is less than the system maximum, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params 01632, 00000, "max # extents (%s) reached in index %s.%s" // *Cause: An index tried to extend past maxextents // *Action: If maxextents is less than the system max, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params. 01633, 00000, "Real Application Clusters Option needed for this operation" // *Cause: System doesn't have Real Application Clusters configured // *Action: Obtain Real Application Clusters option 01634, 00000, "rollback segment number '%s' is about to go offline" // *Cause: The rollback segment specified was marked to go offline by DBA. // *Action: Bring the rollback segment online first. 01635, 00000, "rollback segment #%s specified not available" // *Cause: (same as 1545) // *Action: (same as 1545) 01636, 00000, "rollback segment '%s' is already online" // *Cause: The instance is trying to online an already online RS // *Action: 01637, 00000, "rollback segment '%s' is being used by another instance (#%s)" // *Cause: The instance is trying to online a RS already in use by another // instance // *Action: 01638, 00000, "parameter %s does not allow ORACLE version %s to mount cluster database" // *Cause: The recovery compatible parameter is set too low to allow this // software version to mount in cluster database mode. // *Action:Either use an earlier software release or advance the // recovery_compatible parameter. If this happens when no // recovery_compatible parameter has been specified then set it // to the current software release. 01639, 00000, " instance %s has no thread assigned to it" // *Cause: There is no mapping from instance to thread for this instance in // the control file. // *Action:Make sure that this instance has a thread assigned to it by adding // logfiles to this instance or by starting the instance with an // existing thread which will automatically create a mapping. 01640, 00000, "cannot make tablespace read-only with changes by in-doubt transactions" // *Cause: An attempt was made to alter a tablespace read-only while there were // changes in the tablespace made by in-doubt distributed transactions. // The in-doubt transactions must commit or rollback to ensure that // there is no undo for a tablespace before it can be made read-only. // *Action: Any in-doubt transactions that made changes to the tablespace must // be resolved. 01641, 00000, "tablespace '%s' is not online - cannot add data file" // *Cause: Attempting to add a datafile to a tablespace that has been set // to read-only or offline. // *Action: Make the tablespace online and read write then add the datafile. 01642, 00000, "begin backup not needed for read-only tablespace '%s'" // *Cause: Attempting to begin or end a backup for a tablespace that has // been set to read-only. // *Action: Take the backup without any begin or end commands. The files // are not being modified so the backup will be consistent. 01643, 00000, "system tablespace can not be made read-only" // *Cause: Attempting to set the system tablespace to read-only. The system // tablespace must remain read write for database operation. // *Action: Leave system tablespace read write. 01644, 00000, "tablespace '%s' is already read-only" // *Cause: Attempting to make tablespace read-only that is already read-only. // *Action: Leave tablespace read-only, or make read write then make // read-only again. 01645, 00000, "previous attempt to make read write is half complete" // *Cause: A failure while making the tablespace read write left it read // only, but the checkpoint was advanced. The tablespace will not // be useable after a resetlogs if its files are offline. // *Action: Repeat the command to make the tablespace read write. 01646, 00000, "tablespace '%s' is not read-only - cannot make read write" // *Cause: Attempting to make a tablespace read write that is not read-only. // It may be either online or offline. // *Action: Leave tablespace read write. 01647, 00000, "tablespace '%s' is read-only, cannot allocate space in it" // *Cause: Tried to allocate space in a read-only tablespace // *Action: Create the object in another tablespace 01648, 00000, "log %s is the current log of disabled instance %s (thread %s)" // *Cause: An attempt to enable the thread failed after it was half completed. // This log was left as the current log even though the thread is still // disabled. Since a log switch cannot be done until the thread is // enabled, the log can not be cleared or archived. // *Action:Complete the thread enable by issuing the enable command again. 01649, 00000, "operation not allowed with a backup control file" // *Cause: An attempt is being made to perform a command that does not make // sense when the control file is a restored backup. // *Action:Wait until after the database has been opened and try again. 01650, 00000, "unable to extend rollback segment %s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // a rollback segment in the tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01651, 00000, "unable to extend save undo segment by %s for tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // saving undo entries for the indicated offline tablespace. // *Action: Check the storage parameters for the SYSTEM tablespace. The // tablespace needs to be brought back online so the undo can be // applied. 01652, 00000, "unable to extend temp segment by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // a temporary segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01653, 00000, "unable to extend table %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // a table segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01654, 00000, "unable to extend index %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // an index segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01655, 00000, "unable to extend cluster %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // a cluster segment in tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01656, 00000, "max # extents (%s) reached in cluster %s.%s" // *Cause: A cluster tried to extend past maxextents // *Action: If maxextents is less than the system maximum, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params 01657, 00000, "invalid SHRINK option value" // *Cause: The specified value must be an integer. // *Action: Choose an appropriate integer value. 01658, 00000, "unable to create INITIAL extent for segment in tablespace %s" // *Cause: Failed to find sufficient contiguous space to allocate INITIAL // extent for segment being created. // *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the // tablespace or retry with a smaller value for INITIAL 01659, 00000, "unable to allocate MINEXTENTS beyond %s in tablespace %s" // *Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS // for the segment being created. // *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the // tablespace or retry with smaller value for MINEXTENTS, NEXT or // PCTINCREASE 01660, 00000, "tablespace '%s' is already permanent" // *Cause: Attempting to make tablespace permanent that is already permanent. // *Action: Leave tablespace permanent. 01661, 00000, "tablespace '%s' is already temporary" // *Cause: Attempting to make tablespace temporary that is already temporary. // *Action: Leave tablespace permanent. 01662, 00000, "tablespace '%s' is non-empty and cannot be made temporary" // *Cause: Tried to convert a non-empty tablespace to a temporary tablespace // *Action: To drop all the objects in the tablespace. 01663, 00000, "the contents of tablespace '%s' is constantly changing" // *Cause: The contents of the tablespace is always changing between PERMANENT // and TEMPORARY. // *Action: To decide what the tablespace contents should be and stay with it. 01664, 00000, "Transaction which has expanded the Sort Segment has aborted" // *Cause: Internal Error. // *Action: Contact Oracle Support. 01665, 00000, "control file is not a standby control file" // *Cause: Attempting to mount, recover or activate a standby database // without a standby control file. // *Action: Create a standby control file before attempting to use the database // as a standby database. 01666, 00000, "control file is for a standby database" // *Cause: Attempting to mount, recover, or open a standby database without // the appropriate command option to designate a standby database. // *Action: Use the standby option or appropriate commands, or mount with // the primary control file. 01667, 00000, "cannot add any more tablespaces: limit of %s exceeded" // *Cause: There is no more room in the control file for adding tablespaces. // *Action: Resize the control file or drop other tablespaces. 01668, 00000, "standby database requires DROP option for offline of data file" // *Cause: Attempting to take a datafile offline in a standby database without // specifying the DROP option. Files that are offline in a standby // database are not recovered, and are likely to be unusable if // the standby is activated. Note that specifying DROP does not // prevent bringing the file online later. // *Action: Specify the DROP option or leave the file online. 01669, 00000, "standby database control file not consistent" // *Cause: Attempting to activate a standby database with a control file that // has not been recovered to the same point as the data files. Most // likely the control file was just copied from the primary database // and has not been used for recovery. // *Action: Recover the standby database until all the files are consistent. 01670, 00000, "new datafile %s needed for standby database recovery" // *Cause: Standby database recovery noticed that a file was added to the // primary database, but is not available on the standby. // *Action: Either copy the file from the primary database or do an ALTER // DATABASE CREATE DATAFILE command on the standby to create a // file to recover. 01671, 00000, "control file is a backup, cannot make a standby control file" // *Cause: The currently mounted control file is a backup control file, and // attempting to create a control file for a standby database. // *Action: Complete any needed recovery and open the database with the // resetlogs option. 01672, 00000, "control file may be missing files or have extra ones" // *Cause: Attempting to create a standby control file, but the control file // was either recently created via CREATE CONTROLFILE or an incomplete // recovery has been done. Thus the datafiles in the control file // and the ones in the data dictionary may not match. // *Action: Open the database, then retry the operation. 01673, 00000, "data file %s has not been identified" // *Cause: This data file was not in the control file after an incomplete // recovery or CREATE CONTROLFILE. Since information from its // header is needed for standby database recovery, we can not // create a standby control file. // *Action: Find the file and bring it online. If desired it may be taken // offline again. If you intend to drop this file, then taking it // offline with the DROP option will avoid this error. 01674, 00000, "data file %s is an old incarnation rather than current file" // *Cause: Recovery encountered redo that indicates this file was dropped // from the database and another file was added using the same file // number. This implies that a CREATE CONTROLFILE command was given // the old file which was dropped rather than the latest file. // *Action: Rebuild the control file using CREATE CONTROLFILE, and give the // correct file. 01675, 00000, "max_commit_propagation_delay inconsistent with other instances" // *Cause: The max_commit_propagation_delay INIT.ORA parameter is // inconsistent with those in other instances. // *Action: Make sure all instances have the same max_commit_propagation_delay. 01676, 00000, "standby file name convert of '%s' exceeds maximum length of %s" // *Cause: When the given file name is converted to the name used for the // standby database, the converted name is bigger than the maximum // allowed file name. // *Action: Change initialization parameter DB_FILE_STANDBY_NAME_CONVERT or // LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name. 01677, 00000, "standby file name convert parameters differ from other instance" // *Cause: The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT // initialization parameters are not the same as in other instances // that already have the database mounted. // *Action: Change initialization parameters DB_FILE_STANDBY_NAME_CONVERT and // LOG_FILE_STANDBY_NAME_CONVERT to match other instances. 01678, 00000, "parameter %s must be pairs of pattern and replacement strings" // *Cause: The initialization parameter does not have even number of strings // for its value. The odd numbered strings are patterns to be found in // file names. The even numbered strings are used to replace the // corresponding patterns when found in file names. // *Action:Specify even number of strings for the parameter, or omit the // parameter. 01679, 00000, "database is being opened" // *Cause: An attempt was made to activate a standby database when the // database was in the middle of being opened. // *Action: Wait for database open to finish and retry the ACTIVATE command. 01680, 00000, "unable to extend LOB segment by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // a LOB segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01681, 00000, "max # extents (%s) reached in LOB segment in tablespace %s" // *Cause: A LOB segment tried to extend past max extents. // *Action: If maxextents for the tablespace is less than the the system // maximum, you can raise that. Otherwise, raise pctincrease for the // tablespace 01682, 00000, "read-only DB cannot allocate temporary space in tablespace %s" // *Cause: Temporary space (usually for sorting) could not be allocated in // either main storage or a tempfile. An attempt was made to // allocate the space from the tablespace named, but the database is // opened read-only. The database open requires a sort work space. // *Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE // initialization parameter), or create a temporary tablespace before // making the database read-only. Use ALTER TABLESPACE ADD TEMPFILE // statement to add temporary files to the temporary tablespace. 01683, 00000, "unable to extend index %s.%s partition %s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // index segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01684, 00000, "max # extents (%s) reached in table %s.%s partition %s" // *Cause: A table tried to extend past maxextents // *Action: If maxextents is less than the system maximum, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params 01685, 00000, "max # extents (%s) reached in index %s.%s partition %s" // *Cause: An index tried to extend past maxextents // *Action: If maxextents is less than the system max, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params. 01686, 00000, "max # files (%s) reached for the tablespace %s" // *Cause: The number of files for a given tablespace has reached its maximum // value // *Action: Resize existing files in the tablespace, or partition the objects // among multiple tablespaces, or move some objects to a different // tablespace. 01687, 00000, "specified logging attribute for tablespace '%s' is same as the existing" // *Cause: Attempting to change the tablespace default logging attribute // (LOGGING or NOLOGGING) to be the same as the existing logging // attribute // *Action: Change the specified logging attribute 01688, 00000, "unable to extend table %s.%s partition %s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // table segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01689, 00000, "syntax error in clause \"%s\" of %s" // *Cause: There was a syntax in the INIT.ORA parameter. // *Action: Fix the syntax error and restart the instance. 01690, 00000, "sort area size too small" // *Cause: sort area size too small to fit two records in memory // *Action: increase sort_area_size 01691, 00000, "unable to extend lob segment %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // LOB segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01692, 00000, "unable to extend lob segment %s.%s partition %s by %s in tablespace %s" // *Cause: Failed to allocate an extent of the required number of blocks for // LOB segment in the tablespace indicated. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01693, 00000, "max # extents (%s) reached in lob segment %s.%s" // *Cause: A LOB segment tried to extend past maxextents // *Action: If maxextents is less than the system max, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params. 01694, 00000, "max # extents (%s) reached in lob segment %s.%s partition %s" // *Cause: A LOB segment tried to extend past maxextents // *Action: If maxextents is less than the system max, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params. 01695, 00000, "error converting rollback segment %s to version 8.0.2" // *Cause: Version 8.0.1 database may not have shutdown cleanly // *Action: May have to reload the 8.0.1 database and shutdown cleanly 01696, 00000, "control file is not a clone control file" // *Cause: Attempting to mount, a database as a clone when it is already // mounted by another instance not as a clone or attempting to use // a current control file for a clone. // *Action: Mount without the clone option or use a backup control file and // shutdown the other instances before mounting as a clone. 01697, 00000, "control file is for a clone database" // *Cause: Attempting to mount a clone database without the appropriate // command option to designate a clone database. // *Action: Use the clone option or appropriate commands, or mount with // the primary control file. 01698, 00000, "a clone database may only have SYSTEM rollback segment online" // *Cause: Attempting to online a rollback segment in a clone database. // *Action: Do not use this command. 01699, 00000, "tablespace '%s' is being imported for point in time recovery" // *Cause: Attempting to online a tablespace or begin another point in // time import while a point in time import is already in progress // *Action: Wait until the import complets // / / 1700 - 1799 Parse errors continued from 900 - 999 / 01700, 00000, "duplicate username in list" // *Cause: // *Action: 01701, 00000, "a cluster is not appropriate here" // *Cause: // *Action: 01702, 00000, "a view is not appropriate here" // *Cause: Among other possible causes, this message will be produced if an // attempt was made to define an Editioning View over a view. // *Action: An Editioning View may only be created over a base table. 01703, 00000, "missing SYNONYM keyword" // *Cause: // *Action: 01704, 00000, "string literal too long" // *Cause: The string literal is longer than 4000 characters. // *Action: Use a string literal of at most 4000 characters. // Longer values may only be entered using bind variables. 01705, 00000, "an outer join cannot be specified on a correlation column" // *Cause: // *Action: 01706, 00000, "user function result value was too large" // *Cause: // *Action: 01707, 00000, "missing LIST keyword" // *Cause: // *Action: 01708, 00000, "ACCESS or SESSION expected" // *Cause: // *Action: 01709, 00000, "program does not exist" // *Cause: // *Action: 01710, 00000, "missing OF keyword" // *Cause: // *Action: 01711, 00000, "duplicate privilege listed" // *Cause: // *Action: 01712, 00000, "you cannot grant a privilege which you do not have" // *Cause: // *Action: 01713, 00000, "GRANT OPTION does not exist for that privilege" // *Cause: // *Action: 01714, 00000, "error in execution of user function" // *Cause: // *Action: 01715, 00000, "UNIQUE may not be used with a cluster index" // *Cause: An attempt was made to create a cluster index with the // UNIQUE attribute. // *Action: Remove UNIQUE from the CREATE INDEX statement. 01716, 00000, "NOSORT may not be used with a cluster index" // *Cause: An attempt was made to create a cluster index using // the NOSORT option. // *Action: Remove NOSORT from the CREATE INDEX statement. 01717, 00000, "seccta: invalid access mode token passed" // *Cause: // *Action: 01718, 00000, "BY ACCESS | SESSION clause not allowed for NOAUDIT" // *Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement. // *Action: Remove BY ACCESS | SESSION. 01719, 00000, "outer join operator (+) not allowed in operand of OR or IN" // *Cause: An outer join appears in an or clause. // *Action: If A and B are predicates, to get the effect of (A(+) or B), // try (select where (A(+) and not B)) union all (select where (B)). 01720, 00000, "grant option does not exist for '%s.%s'" // *Cause: A grant was being performed on a view and the grant option was // not present for an underlying object. // *Action: Obtain the grant option on all underlying objects of the view. 01721, 00000, "USERENV(COMMITSCN) invoked more than once in a transaction" // *Cause: The USERENV('COMMITSCN') function can only be used once in a // transaction. // *Action: Re-write the transactioin to use USERENV('COMMITSCN') only once 01722, 00000, "invalid number" // *Cause: The specified number was invalid. // *Action: Specify a valid number. 01723, 00000, "zero-length columns are not allowed" // *Cause: Columns with zero length were not allowed. // *Action: Correct the use of the column. 01724, 00000, "floating point precision is out of range (1 to 126)" // *Cause: The specified number had an invalid range. // *Action: Use a floating point precision that is in the correct precision. 01725, 00000, "USERENV('COMMITSCN') not allowed here" // *Cause: The function USERENV('COMMITSCN') is only allowed as a top-level // expression in the VALUES clause of an INSERT statement, and on // the right-hand side of an assignment in an UPDATE statement. // *Action: Correct the use of the function. 01726, 00000, "a table is not appropriate here" // *Cause: // *Action: 01727, 00000, "numeric precision specifier is out of range (1 to 38)" // *Cause: // *Action: 01728, 00000, "numeric scale specifier is out of range (-84 to 127)" // *Cause: // *Action: 01729, 00000, "database link name expected" // *Cause: // *Action: 01730, 00000, "invalid number of column names specified" // *Cause: // *Action: 01731, 00000, "circular view definition encountered" // *Cause: // *Action: 01732, 00000, "data manipulation operation not legal on this view" // *Cause: // *Action: 01733, 00000, "virtual column not allowed here" // *Cause: // *Action: 01734, 00000, "illegal parameters - EXTENT MIN higher than EXTENT MAX" // *Cause: A wrong value is specified for the parameter. // *Action: Correct the parameter and reissue the statement. 01735, 00000, "invalid ALTER TABLE option" // *Cause: // *Action: 01736, 00000, "[NOT] SUCCESSFUL expected" // *Cause: // *Action: 01737, 00000, "valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE" // *Cause: // *Action: Valid lock modes are SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, // SHARE ROW EXCLUSIVE, and SHARE UPDATE. 01738, 00000, "missing IN keyword" // *Cause: // *Action: 01739, 00000, "missing MODE keyword" // *Cause: // *Action: 01740, 00000, "missing double quote in identifier" // *Cause: // *Action: 01741, 00000, "illegal zero-length identifier" // *Cause: // *Action: 01742, 00000, "comment not terminated properly" // *Cause: The indicated comment or hint begun with the /* token did not // have the terminating */. // *Action: Properly terminate the comment or hint with a */. 01743, 00000, "only pure functions can be indexed" // *Cause: The indexed function uses SYSDATE or the user environment. // *Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL // expressions must not use SYSDATE, USER, USERENV(), or anything // else dependent on the session state. NLS-dependent functions // are OK. 01744, 00000, "inappropriate INTO" // *Cause: // *Action: 01745, 00000, "invalid host/bind variable name" // *Cause: // *Action: 01746, 00000, "indicator variable not permitted here" // *Cause: // *Action: 01747, 00000, "invalid user.table.column, table.column, or column specification" // *Cause: // *Action: 01748, 00000, "only simple column names allowed here" // *Cause: // *Action: 01749, 00000, "you may not GRANT/REVOKE privileges to/from yourself" // *Cause: // *Action: 01750, 00000, "UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column" // *Cause: // *Action: 01751, 00000, "Invalid dump undo option" // *Cause: An invalid option is specified in the ALTER DUMP UNDO command. // *Action: Correct and reissue the command. 01752, 00000, "cannot delete from view without exactly one key-preserved table" // *Cause: The deleted table had // - no key-preserved tables, // - more than one key-preserved table, or // - the key-preserved table was an unmerged view. // *Action: Redefine the view or delete it from the underlying base tables. 01753, 00000, "column definition incompatible with clustered column definition" // *Cause: // *Action: 01754, 00000, "a table may contain only one column of type LONG" // *Cause: An attempt was made to add a LONG column to a table which already // had a LONG column. Note that even if the LONG column currently // in the table has already been marked unused, another LONG column // may not be added until the unused columns are dropped. // *Action: Remove the LONG column currently in the table by using the ALTER // TABLE command. 01755, 00000, "Must specify an extent number or block number" // *Cause: Expecting an extent or block number but something else was // specified. // *Action: Correct the error and reissue the command. 01756, 00000, "quoted string not properly terminated" // *Cause: // *Action: 01757, 00000, "Must specify an object number" // *Cause: Expecting an object number but something else was specified. // *Action: Correct the error and reissue the command. 01758, 00000, "table must be empty to add mandatory (NOT NULL) column" // *Cause: // *Action: 01759, 00000, "user function is incorrectly defined" // *Cause: // *Action: 01760, 00000, "illegal argument for function" // *Cause: // *Action: 01761, 00000, "DML operation does not map to a unique table in the join" // *Cause: The primary table is the base table against which the update, // insert or delete operation is finally being done. For delete // either there is no primary table in the join query or there is // more than one. For update or insert the columns specified map // to more than one base table. // *Action: Change the join specification. 01762, 00000, "vopdrv: view query block not in FROM" // *Cause: // *Action: 01763, 00000, "update or delete involves outer joined table" // *Cause: For deletes, the table being deleted from is outer joined to some // other table. For updates, either the table being updated is outer- // joined to some other table, or some table reachable from the primary // table is being outer joined to a table not reachable from the // primary table. // *Action: Change the join specification. 01764, 00000, "new update value of join is not guaranteed to be unique" // *Cause: A row of a join query table is being updated using a row of a // table that is not guaranteed to have exactly one value for the // row being updated. // *Action: Change the join specification. 01765, 00000, "specifying owner's name of the table is not allowed" // *Cause: An attempt was made to rename the object with dotted object name. // *Action: Do not specify username.tablename in query for table name. 01766, 00000, "dictionary table not allowed in this context" // *Cause: // *Action: 01767, 00000, "UPDATE ... SET expression must be a subquery" // *Cause: // *Action: 01768, 00000, "number string too long" // *Cause: // *Action: 01769, 00000, "duplicate CLUSTER option specifications" // *Cause: During a CREATE of a clustered table, the user attempted to specify // more than one CLUSTER option. // *Action: Remove the extra CLUSTER option. 01770, 00000, "CLUSTER option not allowed in CREATE CLUSTER command" // *Cause: // *Action: 01771, 00000, "illegal option for a clustered table" // *Cause: During a CREATE or ALTER of a clustered table, the user attempted // to enter one or more of the following options: // INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. // These options may only be specified for the cluster itself. // *Action: Remove the illegal option(s). 01772, 00000, "Must specify a value for LEVEL" // *Cause: Expecting the value of LEVEL but something else was specified. // *Action: Correct the error and reissue the command. 01773, 00000, "may not specify column datatypes in this CREATE TABLE" // *Cause: // *Action: 01774, 00000, "Dump undo option specified more than once" // *Cause: The same option for ALTER DUMP UNDO was specified twice. // *Action: Remove the redundant options and reissue the command. 01775, 00000, "looping chain of synonyms" // *Cause: // *Action: 01776, 00000, "cannot modify more than one base table through a join view" // *Cause: Columns belonging to more than one underlying table were either // inserted into or updated. // *Action: Phrase the statement as two or more separate statements. 01777, 00000, "WITH GRANT OPTION not allowed in this system" // *Cause: // *Action: 01778, 00000, "maximum subquery nesting level exceeded" // *Cause: // *Action: 01779, 00000, "cannot modify a column which maps to a non key-preserved table" // *Cause: An attempt was made to insert or update columns of a join view which // map to a non-key-preserved table. // *Action: Modify the underlying base tables directly. 01780, 00000, "string literal required" // *Cause: // *Action: / 01781, 00000, "UNRECOVERABLE cannot be specified without AS SELECT" // *Cause: UNRECOVERABLE was specified in a CREATE TABLE statement // without also specifying a populating subquery with an AS clause. // *Action: Do not specify UNRECOVERABLE. / 01782, 00000, "UNRECOVERABLE cannot be specified for a cluster or clustered table" // *Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement // specified UNRECOVERABLE. // *Action: Do not specify UNRECOVERABLE. / 01783, 00000, "only one RECOVERABLE or UNRECOVERABLE clause may be specified" // *Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified // more than once, or both RECOVERABLE and UNRECOVERABLE were specified // in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement. // *Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and // reissue the statement. / 01784, 00000, "RECOVERABLE cannot be specified with database media recovery disabled" // *Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE // when the database was running in NOARCHIVELOG mode. Since logs // are not being archived, they will be overwritten and the object // being created cannot be recovered from a backup taken before the // object was created. // *Action: Do not specify RECOVERABLE, or restart the database with media // recovery enabled. / 01785, 00000, "ORDER BY item must be the number of a SELECT-list expression" // *Cause: // *Action: 01786, 00000, "FOR UPDATE of this query expression is not allowed" // *Cause: // *Action: 01787, 00000, "only one clause allowed per query block" // *Cause: // *Action: 01788, 00000, "CONNECT BY clause required in this query block" // *Cause: // *Action: 01789, 00000, "query block has incorrect number of result columns" // *Cause: // *Action: 01790, 00000, "expression must have same datatype as corresponding expression" // *Cause: // *Action: 01791, 00000, "not a SELECTed expression" // *Cause: // *Action: 01792, 00000, "maximum number of columns in a table or view is 1000" // *Cause: An attempt was made to create a table or view with more than 1000 // columns, or to add more columns to a table or view which pushes // it over the maximum allowable limit of 1000. Note that unused // columns in the table are counted toward the 1000 column limit. // *Action: If the error is a result of a CREATE command, then reduce the // number of columns in the command and resubmit. If the error is // a result of an ALTER TABLE command, then there are two options: // 1) If the table contained unused columns, remove them by executing // ALTER TABLE DROP UNUSED COLUMNS before adding new columns; // 2) Reduce the number of columns in the command and resubmit. 01793, 00000, "maximum number of index columns is 32" // *Cause: // *Action: 01794, 00000, "maximum number of cluster columns is 32" // *Cause: // *Action: 01795, 00000, "maximum number of expressions in a list is 1000" // *Cause: Number of expressions in the query exceeded than 1000. // Note that unused column/expressions are also counted // Maximum number of expressions that are allowed are 1000. // *Action: Reduce the number of expressions in the list and resubmit. 01796, 00000, "this operator cannot be used with lists" // *Cause: // *Action: 01797, 00000, "this operator must be followed by ANY or ALL" // *Cause: // *Action: 01798, 00000, "missing EXCEPTION keyword" // *Cause: // *Action: 01799, 00000, "a column may not be outer-joined to a subquery" // *Cause: (+) () is not allowed. // *Action: Either remove the (+) or make a view out of the subquery. // In V6 and before, the (+) was just ignored in this case. / / parse errors continued at 2000 / / 1800 - 1899 Date function errors / 1800 - 1809 Overflow conditions / 01800, 00000, "a literal in the date format was too large to process" // *Cause: // *Action: 01801, 00000, "date format is too long for internal buffer" // *Cause: // *Action: 01802, 00000, "Julian date is out of range" // *Cause: // *Action: 01803, 00000, "failure in getting date/time" // *Cause: // *Action: 01804, 00000, "failure to initialize timezone information" // *Cause: The timezone information file was not properly read. // *Action: Please contact Oracle Customer Support. 01805, 00000, "possible error in date/time operation" // *Cause: The timezone files on client and server do not match. // Operation can potentially result in incorrect results based on // local timezone file. // *Action: Please ensure client and server timezone versions are same. / / 1810 - 1829 Conflicting date input format / 01810, 00000, "format code appears twice" // *Cause: // *Action: 01811, 00000, "Julian date precludes use of day of year" // *Cause: // *Action: 01812, 00000, "year may only be specified once" // *Cause: // *Action: 01813, 00000, "hour may only be specified once" // *Cause: // *Action: 01814, 00000, "AM/PM conflicts with use of A.M./P.M." // *Cause: // *Action: 01815, 00000, "BC/AD conflicts with use of B.C./A.D." // *Cause: // *Action: 01816, 00000, "month may only be specified once" // *Cause: // *Action: 01817, 00000, "day of week may only be specified once" // *Cause: // *Action: 01818, 00000, "'HH24' precludes use of meridian indicator" // *Cause: // *Action: 01819, 00000, "signed year precludes use of BC/AD" // *Cause: // *Action: 01820, 00000, "format code cannot appear in date input format" // *Cause: // *Action: 01821, 00000, "date format not recognized" // *Cause: // *Action: 01822, 00000, "era format code is not valid with this calendar" // *Cause: // *Action: / / 1830 - 1899 Failed input conversions / 01830, 00000, "date format picture ends before converting entire input string" // *Cause: // *Action: 01831, 00000, "year conflicts with Julian date" // *Cause: // *Action: 01832, 00000, "day of year conflicts with Julian date" // *Cause: // *Action: 01833, 00000, "month conflicts with Julian date" // *Cause: // *Action: 01834, 00000, "day of month conflicts with Julian date" // *Cause: // *Action: 01835, 00000, "day of week conflicts with Julian date" // *Cause: // *Action: 01836, 00000, "hour conflicts with seconds in day" // *Cause: // *Action: 01837, 00000, "minutes of hour conflicts with seconds in day" // *Cause: // *Action: 01838, 00000, "seconds of minute conflicts with seconds in day" // *Cause: // *Action: 01839, 00000, "date not valid for month specified" // *Cause: // *Action: 01840, 00000, "input value not long enough for date format" // *Cause: // *Action: 01841, 00000, "(full) year must be between -4713 and +9999, and not be 0" // *Cause: Illegal year entered // *Action: Input year in the specified range 01842, 00000, "quarter must be between 1 and 4" // *Cause: // *Action: 01843, 00000, "not a valid month" // *Cause: // *Action: 01844, 00000, "week of year must be between 1 and 52" // *Cause: // *Action: 01845, 00000, "week of month must be between 1 and 5" // *Cause: // *Action: 01846, 00000, "not a valid day of the week" // *Cause: // *Action: 01847, 00000, "day of month must be between 1 and last day of month" // *Cause: // *Action: 01848, 00000, "day of year must be between 1 and 365 (366 for leap year)" // *Cause: // *Action: 01849, 00000, "hour must be between 1 and 12" // *Cause: // *Action: 01850, 00000, "hour must be between 0 and 23" // *Cause: // *Action: 01851, 00000, "minutes must be between 0 and 59" // *Cause: // *Action: 01852, 00000, "seconds must be between 0 and 59" // *Cause: // *Action: 01853, 00000, "seconds in day must be between 0 and 86399" // *Cause: // *Action: 01854, 00000, "julian date must be between 1 and 5373484" // *Cause: An invalid Julian date was entered. // *Action: Enter a valid Julian date between 1 and 5373484. 01855, 00000, "AM/A.M. or PM/P.M. required" // *Cause: // *Action: 01856, 00000, "BC/B.C. or AD/A.D. required" // *Cause: // *Action: 01857, 00000, "not a valid time zone" // *Cause: // *Action: 01858, 00000, "a non-numeric character was found where a numeric was expected" // *Cause: The input data to be converted using a date format model was // incorrect. The input data did not contain a number where a number was // required by the format model. // *Action: Fix the input data or the date format model to make sure the // elements match in number and type. Then retry the operation. 01859, 00000, "a non-alphabetic character was found where an alphabetic was expected" // *Cause: The input data to be converted using a date format model was // incorrect. The input data did not contain a letter where a letter was // required by the format model. // *Action: Fix the input data or the date format model to make sure the // elements match in number and type. Then retry the operation. 01860, 00000, "week of year must be between 1 and 53" // *Cause: // *Action: 01861, 00000, "literal does not match format string" // *Cause: Literals in the input must be the same length as literals in // the format string (with the exception of leading whitespace). If the // "FX" modifier has been toggled on, the literal must match exactly, // with no extra whitespace. // *Action: Correct the format string to match the literal. 01862, 00000, "the numeric value does not match the length of the format item" // *Cause: When the FX and FM format codes are specified for an input date, // then the number of digits must be exactly the number specified by the // format code. For example, 9 will not match the format specifier DD but // 09 will. // *Action: Correct the input date or turn off the FX or FM format specifier // in the format string. 01863, 00000, "the year is not supported for the current calendar" // *Cause: The year is not supported for the current calendar. // *Action: Please check the documentation to find out what years are // supported for the current calendar. 01864, 00000, "the date is out of range for the current calendar" // *Cause: Your calendar doesn't extend to the specified date. // *Action: Specify a date which is legal for this calendar. 01865, 00000, "not a valid era" // *Cause: Era input does not match a known era. // *Action: Provide a valid era on input. 01866, 00000, "the datetime class is invalid" // *Cause: This is an internal error. // *Action: Please contact Oracle Worldwide Support. 01867, 00000, "the interval is invalid" // *Cause: The character string you specified is not a valid interval. // *Action: Please specify a valid interval. 01868, 00000, "the leading precision of the interval is too small" // *Cause: The leading precision of the interval is too small to store the // specified interval. // *Action: Increase the leading precision of the interval or specify an // interval with a smaller leading precision. 01869, 00000, "reserved for future use" // *Cause: // *Action: 01870, 00000, "the intervals or datetimes are not mutually comparable" // *Cause: The intervals or datetimes are not mutually comparable. // *Action: Specify a pair of intervals or datetimes that are mutually // comparable. 01871, 00000, "the number of seconds must be less than 60" // *Cause: The number of seconds specified was greater than 59. // *Action: Specify a value for seconds that is 59 or smaller. 01872, 00000, "reserved for future use" // *Cause: // *Action: 01873, 00000, "the leading precision of the interval is too small" // *Cause: The leading precision of the interval is too small to store the // specified interval. // *Action: Increase the leading precision of the interval or specify an // interval with a smaller leading precision. 01874, 00000, "time zone hour must be between -12 and 14" // *Cause: The time zone hour specified was not in the valid range. // *Action: Specify a time zone hour between -12 and 14. 01875, 00000, "time zone minute must be between -59 and 59" // *Cause: The time zone minute specified was not in the valid range. // *Action: Specify a time zone minute between -59 and 59. 01876, 00000, "year must be at least -4713" // *Cause: The specified year was not in range. // *Action: Specify a year that is greater than or equal to -4713. 01877, 00000, "string is too long for internal buffer" // *Cause: This is an internal error. // *Action: Please contact Oracle Worldwide Support. 01878, 00000, "specified field not found in datetime or interval" // *Cause: The specified field was not found in the datetime or interval. // *Action: Make sure that the specified field is in the datetime or interval. 01879, 00000, "the hh25 field must be between 0 and 24" // *Cause: The specified hh25 field was not in the valid range. // *Action: Specify an hh25 field between 0 and 24. 01880, 00000, "the fractional seconds must be between 0 and 999999999" // *Cause: The specified fractional seconds were not in the valid range. // *Action: Specify a value for fractional seconds between 0 and 999999999. 01881, 00000, "timezone region ID is invalid" // *Cause: The region ID referenced an invalid region. // *Action: Contact Oracle Support Services. 01882, 00000, "timezone region not found" // *Cause: The specified region name was not found. // *Action: Contact Oracle Support Services. 01883, 00000, "overlap was disabled during a region transition" // *Cause: The region was changing state and the overlap flag // was disabled. // *Action: Please contact Oracle Customer Support. 01884, 00000, "divisor is equal to zero" // *Cause: An attempt was made to divide by zero. // *Action: Avoid zero divisor. 01890, 00000, "NLS error detected" // *Cause: An NLS error was detected. // *Action: Look for additional error messages and take appropriate action. // If there are no additional errors, call Oracle Worldwide Support. 01891, 00000, "Datetime/Interval internal error" // *Cause: Internal error. // *Action: Please contact Oracle Worldwide Support. 01898, 00000, "too many precision specifiers" // *Cause: While trying to truncate or round dates, extra data was found in the // date format picture // *Action: Check the syntax of the date format picture and retry. 01899, 00000, "bad precision specifier" // *Cause: // *Action: / / 1900 - 1999 V6 parse errors / 01900, 00000, "LOGFILE keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01901, 00000, "ROLLBACK keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01902, 00000, "SEGMENT keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01903, 00000, "EVENTS keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01904, 00000, "DATAFILE keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01905, 00000, "STORAGE keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01906, 00000, "BACKUP keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01907, 00000, "TABLESPACE keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01908, 00000, "EXISTS keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01909, 00000, "REUSE keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01910, 00000, "TABLES keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01911, 00000, "CONTENTS keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01912, 00000, "ROW keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01913, 00000, "EXCLUSIVE keyword expected" // *Cause: keyword missing // *Action: supply missing keyword 01914, 00000, "invalid auditing option for sequence numbers" // *Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option // that is not legal for sequence numbers. // *Action: The following options may not be used for sequence numbers // and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, // RENAME, UPDATE, REFERENCES, EXECUTE 01915, 00000, "invalid auditing option for views" // *Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is // not legal for views. // *Action: The following options may not be used for views // and should be removed: ALTER, INDEX, REFERENCES, EXECUTE 01916, 00000, "keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected" // *Cause: An expected keyword was not used for datafile/tempfile clause // *Action: Use correct syntax. 01917, 00000, "user or role '%s' does not exist" // *Cause: There is not a user or role by that name. // *Action: Re-specify the name. 01918, 00000, "user '%s' does not exist" // *Cause: User does not exist in the system. // *Action: Verify the user name is correct. 01919, 00000, "role '%s' does not exist" // *Cause: Role by that name does not exist. // *Action: Verify you are using the correct role name. 01920, 00000, "user name '%s' conflicts with another user or role name" // *Cause: There is already a user or role with that name. // *Action: Specify a different user name. 01921, 00000, "role name '%s' conflicts with another user or role name" // *Cause: There is already a user or role with that name. // *Action: Specify a different role name. 01922, 00000, "CASCADE must be specified to drop '%s'" // *Cause: Cascade is required to remove this user from the system. The // user own's object which will need to be dropped. // *Action: Specify cascade. 01923, 00000, "CASCADE aborted, objects locked by another user" // *Cause: Cannot drop the user's objects; someone has them locked. // *Action: Use the lock monitor to determine who has the objects locked. 01924, 00000, "role '%s' not granted or does not exist" // *Cause: Set role can only be performed with roles granted // directly to your account. (e.g. a sub-role cannot be enabled) // *Action: Don't try to set the role. 01925, 00000, "maximum of %s enabled roles exceeded" // *Cause: The INIT.ORA parameter "max_enabled_roles" has been exceeded. // *Action: Increase max_enabled_roles and warm start the database. 01926, 00000, "cannot GRANT to a role WITH GRANT OPTION" // *Cause: Role cannot have a privilege with the grant option. // *Action: Perform the grant without the grant option. 01927, 00000, "cannot REVOKE privileges you did not grant" // *Cause: You can only revoke privileges you granted. // *Action: Don't revoke these privileges. 01928, 00000, "GRANT option not granted for all privileges" // *Cause: In order to grant a privilege, you must first have the privilege // with the grant option. // *Action: Obtain the privilege with the grant option and try again. 01929, 00000, "no privileges to GRANT" // *Cause: "ALL" was specified but the user doesn't have any privileges // with the grant option. // *Action: Don't grant privileges on that object. 01930, 00000, "auditing the object is not supported" // *Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited. // *Action: Don't attempt to AUDIT the object. 01931, 00000, "cannot grant %s to a role" // *Cause: REFERENCES, INDEX, SYSDBA, SYSOPER or SYSASM // privilege could not be granted to a role. // *Action: Grant privilege directly to the user. 01932, 00000, "ADMIN option not granted for role '%s'" // *Cause: The operation requires the admin option on the role. // *Action: Obtain the grant option and re-try. 01933, 00000, "cannot create a stored object using privileges from a role" // *Cause: An attempt was made to create a stored object using privileges // from a role. Stored objects cannot use privileges from roles. // *Action: Grant the privileges required to the user directly. 01934, 00000, "circular role grant detected" // *Cause: Roles cannot be granted circularly. Also, a role cannot be // granted to itself. // *Action: Do not perform the grant. 01935, 00000, "missing user or role name" // *Cause: A user or role name was expected. // *Action: Specify a user or role name. 01936, 00000, "cannot specify owner when creating users or roles" // *Cause: Users and roles do not have owners. // *Action: Don't specify an owner. 01937, 00000, "missing or invalid role name" // *Cause: A valid role name was expected. // *Action: Specify a valid role name. 01938, 00000, "IDENTIFIED BY must be specified for CREATE USER" // *Cause: Cannot create a user without specifying a password or // "IDENTIFIED EXTERNALLY". // *Action: Specify one of the password clauses. 01939, 00000, "only the ADMIN OPTION can be specified" // *Cause: System privileges and Roles can only be granted with the admin // option. The grant option cannot be used with these privileges. // *Action: Specify the admin option. 01940, 00000, "cannot drop a user that is currently connected" // *Cause: Attempt was made to drop a user that is currently logged in. // *Action: Make sure user is logged off, then repeat command. 01941, 00000, "SEQUENCE keyword expected" // MERGE: 1917 RENUMBERED TO 1941 // *Cause: keyword missing // *Action: supply missing keyword 01942, 00000, "IDENTIFIED BY and EXTERNALLY cannot both be specified" // *Cause: A user cannot be specified to have and not have a password. // *Action: Specify only one of the options. 01943, 00000, "IDENTIFIED BY already specified" // *Cause: The identified clause has been given twice. // *Action: Use only one identified by clause. 01944, 00000, "IDENTIFIED EXTERNALLY already specified" // *Cause: The identified externaly clause has been given twice. // *Action: Use only one identified clause. 01945, 00000, "DEFAULT ROLE[S] already specified" // *Cause: The default roles clause has been given twice. // *Action: Use only on default role clause. 01946, 00000, "DEFAULT TABLESPACE already specified" // *Cause: The default tablespace clause has been given twice. // *Action: Use only one default tablespace clause. 01947, 00000, "TEMPORARY TABLESPACE already specified" // *Cause: The temporary tablespace clause has been given twice. // *Action: Use only one temporary tablespace clause. 01948, 00000, "identifier's name length (%s) exceeds maximum (%s)" // *Cause: A name has been specified that is too long. // For example, dbms_session.is_role_enabled() specifies a role name // that is too long. // *Action: Change the application or command to use a correct identifier. 01949, 00000, "ROLE keyword expected" // *Cause: The role keyword is required here. // *Action: Specify the role keyword. 01950, 00000, "no privileges on tablespace '%s'" // *Cause: User does not have privileges to allocate an extent in the // specified tablespace. // *Action: Grant the user the appropriate system privileges or grant the user // space resource on the tablespace. 01951, 00000, "ROLE '%s' not granted to '%s'" // *Cause: The role you tried to revoke was not granted to the user. // *Action: Don't try to revoke a privilege which is not granted. 01952, 00000, "system privileges not granted to '%s'" // *Cause: A system privilege you tried to revoke was not granted to the user. // *Action: Make sure the privileges you are trying to revoke are granted. 01953, 00000, "command no longer valid, see ALTER USER" // *Cause: The syntax for assigning quotas on tablespaces has changed. The // ALTER USER command is now used to perform the functionality // *Action: Use the alter user command instead. 01954, 00000, "DEFAULT ROLE clause not valid for CREATE USER" // *Cause: Default roles cannot be specified for create user. // *Action: Grant and alter the user's default roles after creating the user. 01955, 00000, "DEFAULT ROLE '%s' not granted to user" // *Cause: The user being altered does not have the specified role granted // directly to the user. Note, sub-roles cannot be used in the // default role clause. // *Action: Grant the role to the user. 01956, 00000, "invalid command when OS_ROLES are being used" // *Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES // is TRUE. // *Action: Grant the role to the user in the operating system. 01957, 00000, "Keyword MIN or MAX expected, not found" // *Cause: // *Action: 01958, 00000, "Must supply an integer for the LAYER option" // *Cause: // *Action: 01959, 00000, "Must supply an integer for the OPCODE option" // *Cause: // *Action: 01960, 00000, "Invalid dump logfile option" // *Cause: // *Action: 01961, 00000, "Invalid dump option" // *Cause: // *Action: 01962, 00000, "Must specify a file number or log sequence number" // *Cause: // *Action: 01963, 00000, "Must specify a block number" // *Cause: // *Action: 01964, 00000, "Must specify a time for the TIME option" // *Cause: // *Action: 01965, 00000, "Must specify a PERIOD" // *Cause: // *Action: 01967, 00000, "invalid option for CREATE CONTROLFILE" // *Cause: An invalid CREATE CONTROLFILE option is present. // *Action: Specify only valid CREATE CONTROLFILE options. 01968, 00000, "Only specify RESETLOGS or NORESETLOGS once" // *Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once // *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. 01969, 00000, "You must specify RESETLOGS or NORESETLOGS" // *Cause: Missing a RESETLOGS or a NORESETLOGS // *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. 01970, 00000, "You must specify a database name for CREATE CONTROLFILE" // *Cause: Missing a database name // *Action: Retype CREATE CONTROLFILE command with the DATABASE keyword. 01971, 00000, "Illegal ALTER TRACING option" // *Cause: // *Action: 01972, 00000, "Must specify a string for ALTER TRACING ENABLE or DISABLE" // *Cause: // *Action: 01973, 00000, "Missing change number" // *Cause: Keyword "CHANGE" found but change number not specified. // *Action: Fix command line and resubmit 01974, 00000, "Illegal archive option" // *Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command // *Action: 01975, 00000, "Illegal character in change number %s" // *Cause: // *Action: 01976, 00000, "Missing change number" // *Cause: // *Action: 01977, 00000, "Missing thread number" // *Cause: Keyword "THREAD" found but thread number not specified. // *Action: Fix command line and resubmit 01978, 00000, "Missing sequence number" // *Cause: Keyword "SEQUENCE" found but sequence number not specified. // *Action: Fix command line and resubmit 01979, 00000, "missing or invalid password for role '%s'" // *Cause: An attempt was made to enable a role without giving / the proper password. // *Action: Use the "identified by" clause in set role to specify // the correct password. 01980, 00000, "error during OS ROLE initialization" // *Cause: An OS error occurred while loading a users OS ROLES. // *Action: Check the OS error. 01981, 00000, "CASCADE CONSTRAINTS must be specified to perform this revoke" // *Cause: During this revoke some foreign key contraints will be removed. // In order to perform this automatically, CASCADE CONSTRAINTS must // be specified. // *Action: Remove the constraints or specify CASCADE CONSTRAINTS. 01982, 00000, "invalid auditing option for tables" // *Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is // not legal for tables. // *Action: The following options may not be used for tables // and should be removed: REFERENCES, EXECUTE 01983, 00000, "invalid auditing option for DEFAULT" // *Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is // not legal for DEFAULT. // *Action: The following options may not be used for DEFAULT // and should be removed: REFERENCES 01984, 00000, "invalid auditing option for procedures/packages/functions" // *Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is // not legal for procedures, packages, or functions. // *Action: The following options may not be used for procedures, packages, // and functions and should be removed: all but EXECUTE 01985, 00000, "cannot create user as LICENSE_MAX_USERS parameter exceeded" // *Cause: Maximum users in the database license limit exceeded. // *Action: Increase license limit. 01986, 00000, "OPTIMIZER_GOAL is obsolete" // *Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced. // *Action: Use the OPTIMIZER_MODE parameter. 01987, 00000, "client os username is too long" // *Cause: A client's os username is too long for the os logon to succeed. // *Action: Use a shorter os username. 01988, 00000, "remote os logon is not allowed" // *Cause: Remote os login attempted when not allowed. // *Action: Use a local client, or use the remote_os_authent system parameter // to turn on remote os logon. 01989, 00000, "role '%s' not authorized by operating system" // *Cause: The os role does not exist, is not granted to you, or you did not // provide the correct password. // *Action: Re-attempt the SET ROLE with a valid os role and password, if // necessary. 01990, 00000, "error opening password file '%s'" // *Cause: // *Action: 01991, 00000, "invalid password file '%s'" // *Cause: // *Action: 01992, 00000, "error closing password file '%s'" // *Cause: // *Action: 01993, 00000, "error writing password file '%s'" // *Cause: // *Action: 01994, 00000, "GRANT failed: password file missing or disabled" // *Cause: The operation failed either because the INIT.ORA parameter // REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the // password file was missing. // *Action: Create the password file using the orapwd tool and set the // INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE. 01995, 00000, "error reading password file '%s'" // *Cause: // *Action: 01996, 00000, "GRANT failed: password file '%s' is full" // *Cause: // *Action: 01997, 00000, "GRANT failed: user '%s' is identified externally" // *Cause: // *Action: 01998, 00000, "REVOKE failed: user SYS always has SYSOPER and SYSDBA" // *Cause: // *Action: 01999, 00000, "password file cannot be updated in SHARED mode" // *Cause: The operation failed because the INIT.ORA parameter // REMOTE_LOGIN_PASSWORDFILE was set to SHARED. // *Action: Set the INIT.ORA parameter to EXCLUSIVE. / / 2000 - 2099 Parse errors continued from 1700 - 1799 / 02000, 00000, "missing %s keyword" 02001, 00000, "user SYS is not permitted to create indexes with freelist groups" // *Cause: user tried to create an index while running with sys authorization. // *Action: 02002, 00000, "error while writing to audit trail" // *Cause: // *Action: 02003, 00000, "invalid USERENV parameter" // *Cause: // *Action: 02004, 00000, "security violation" // *Cause: This error code is never returned to a user. It is used // as a value for column, audit_trail.returncode, to signal that a // security violation occurred. // *Action: None. 02005, 00000, "implicit (-1) length not valid for this bind or define datatype" // *Cause: // *Action: 02006, 00000, "invalid packed decimal format string" // *Cause: // *Action: 02007, 00000, "can't use ALLOCATE or DEALLOCATE options with REBUILD" // *Cause: Allocate or deallocate storage and rebuild index are not compatible. // *Action: Choose one or the other. 02008, 00000, "non-zero scale specified for nonnumeric column" // *Cause: // *Action: 02009, 00000, "the size specified for a file must not be zero" // *Cause: A value of zero was specified in a SIZE or RESIZE clause // of a file specification. // *Action: Use correct syntax, or, if allowed, omit the SIZE or // RESIZE clause. 02010, 00000, "missing host connect string" // *Cause: // *Action: 02011, 00000, "duplicate database link name" // *Cause: // *Action: 02012, 00000, "missing USING keyword" // *Cause: // *Action: 02013, 00000, "missing CONNECT keyword" // *Cause: // *Action: 02014, 00000, "cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc." // *Cause: An attempt was made to select FOR UPDATE from a view which // had not been merged because the view used syntax (for example, // DISTINCT or GROUP BY) preventing the merge, or because of // initialization file parameter settings. // *Action: Determine the reason the view will not merge and, if possible, // make changes so that it can. 02015, 00000, "cannot select FOR UPDATE from remote table" // *Cause: // *Action: 02016, 00000, "cannot use a subquery in a START WITH on a remote database" // *Cause: // *Action: 02017, 00000, "integer value required" // *Cause: // *Action: 02018, 00000, "database link of same name has an open connection" // *Cause: // *Action: 02019, 00000, "connection description for remote database not found" // *Cause: // *Action: 02020, 00000, "too many database links in use" // *Cause: The current session has exceeded the INIT.ORA open_links maximum. // *Action: Increase the open_links limit, or free up some open links by // committing or rolling back the transaction and canceling open // cursors that reference remote databases. 02021, 00000, "DDL operations are not allowed on a remote database" // *Cause: An attempt was made to use a DDL operation on a remote database. // For example, "CREATE TABLE tablename@remotedbname ...". // *Action: To alter the remote database structure, you must connect to the // remote database with the appropriate privileges. 02022, 00000, "remote statement has unoptimized view with remote object" // *Cause: The local view is unoptimized and contains references to objects // at the remote database and the statement must be executed at the // remote database. // *Action: Create a similar view on the remote database and modify the // violating view in the SQL statement with the new view@remote. 02023, 00000, "START WITH or CONNECT BY predicate cannot be evaluated by remote data base" // *Cause: // *Action: 02024, 00000, "database link not found" // *Cause: Database link to be dropped is not found in dictionary // *Action: Correct the database link name 02025, 00000, "all tables in the SQL statement must be at the remote database" // *Cause: The user's SQL statement references tables from multiple databases. // The remote database is not Oracle V7 or above, and can perform // updates only if it can reference all tables in the SQL statement. // *Action: 02026, 00000, "missing LINK keyword" // *Cause: keyword missing // *Action: supply missing keyword 02027, 00000, "multi-row UPDATE of LONG column is not supported" // *Cause: A bind variable with length greater than 4000 bytes is being // used to update a column, and the update statement updates // more than one row. // *Action: You may only update a single row with such a bind variable. 02028, 00000, "fetching an exact number of rows is not supported by the server" // *Cause: The server does not support UPIALL, so the fetch of an exact // number of rows cannot be emulated on the user side. // *Action: Connect to a valid server or do not use an exact fetch. 02029, 00000, "missing FILE keyword" // *Cause: keyword missing // *Action: supply missing keyword 02030, 00000, "can only select from fixed tables/views" // *Cause: An attempt is being made to perform an operation other than // a retrieval from a fixed table/view. // *Action: You may only select rows from fixed tables/views. 02031, 00000, "no ROWID for fixed tables or for external-organized tables" // *Cause: An attempt is being made to access rowid from a fixed // table or from a external-organized table. // *Action: Do not access ROWID from a fixed table or from a // external-organized table. 02032, 00000, "clustered tables cannot be used before the cluster index is built" // *Cause: User attempted to perform a DML statement on a clustered table // for which no cluster index has yet been created. // *Action: Create the cluster index. 02033, 00000, "a cluster index for this cluster already exists" // *Cause: A cluster index already exists for the cluster. // *Action: None. 02034, 00000, "speed bind not permitted" // *Cause: Speed bind not allowed with supplied bind variables. Trapped // internally by the system. // *Action: none 02035, 00000, "illegal bundled operation combination" // *Cause: User requested that the UPI bundled execution call perform an // an illegal combination of operations. // *Action: See documentation for legal operation combinations. 02036, 00000, "too many variables to describe with automatic cursor open" // *Cause: User requested that the UPI bundled execution call perform // automatic cursor open and close on a describe operation. There // were too many select-list items or bind variables to do this. // *Action: open and close cursor explicitly 02037, 00000, "uninitialized speed bind storage" // *Cause: User attempted a UPI bundled execution call containing a // standalone execute operation without first performing // a UPI bundled execution call containing a bind operation. // *Action: perform a UPI bundled execution call with bind before performing a // bundled execution call with execute 02038, 00000, "define is not allowed for array type " // *Cause: User attempted to define a select list variable of type "array". // Arrays may only serve as host bind variables. // *Action: 02039, 00000, "bind by value is not allowed for array type " // *Cause: User attempted to bind an array host variable by value. // Arrays may only be bound by reference. // *Action: / / 2040 .. 2099 - Reserved for distributed update / (Message range continued at 160) / 02040, 00000, "remote database %s does not support two-phase commit" // *Cause: the database was potentially updated but does not support prepare // to commit (as determined by its logon transaction traits). The // transaction was rolled back. // *Action: Do not attempt to update the remote database unless it is the // only database updated in one transaction. 02041, 00000, "client database did not begin a transaction" // *Cause: internal error // *Action: contact support 02042, 00000, "too many distributed transactions" // *Cause: the distributed transaction table was full because too many // distributed transactions were active. // *Action: Run fewer transactions. If you are sure you don't have too // many concurrent distributed transactions, this indicates an internal // error and support should be notified. Instance shutdown/restart // would be a work-around. 02043, 00000, "must end current transaction before executing %s" // *Cause: a transaction is in progress and one of the following commands // commands is issued: COMMIT FORCE, ROLLBACK FORCE, or // ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode. // *Action: COMMIT or ROLLBACK the current transaction and resubmit // command. 02044, 00000, "transaction manager login denied: transaction in progress" // *Cause: a remote transaction manager tried to log in while a distributed // transaction is in progress. // *Action: end the current transaction (this is a protocol error from a // remote transaction manager) 02045, 00000, "too many local sessions participating in global transaction" // *Cause: too many sessions at this site for this transaction. // *Action: use an existing link so another session need not be created. 02046, 00000, "distributed transaction already begun" // *Cause: internal error or error in external transaction manager. // A server session received a begin_tran RPC before finishing // with a previous distributed tran. 02047, 00000, "cannot join the distributed transaction in progress" // *Cause: Either a transaction is in progress against a remote database // that does not fully support two phase commit, and an update // is attempted on another database, or updates are pending and // and an attempt is made to update a different database that // does not fully support two phase commit. // *Action: complete the current transaction and then resubmit the // update request. 02048, 00000, "attempt to begin distributed transaction without logging on" // *Cause: client program must issue a distributed transaction login. // *Action: contact support. 02049, 00000, "timeout: distributed transaction waiting for lock" // *Cause: exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock. // *Action: treat as a deadlock 02050, 00000, "transaction %s rolled back, some remote DBs may be in-doubt" // *Cause: network or remote failure in 2PC. // *Action: Notify operations; remote DBs will automatically re-sync when the // failure is repaired. 02051, 00000, "another session or branch in same transaction failed or finalized" // *Cause: A session at the same site with the same global transaction ID failed. // The failure could also be caused by an application error if an attempt // was made to update the database while another tightly coupled transaction // branch with the same global transaction ID was finalized or aborted. // *Action: No action necessary as the transaction will be automatically recovered. // In the case of an application error, make sure there are no more updates // to the database once the transaction manager has started two-phase commit // for tightly coupled distributed transaction. 02052, 00000, "remote transaction failure at %s" // *Cause: error in remote transaction at given DBLINK // *Action: retry 02053, 00000, "transaction %s committed, some remote DBs may be in-doubt" // *Cause: network or remote failure in 2PC. // *Action: Notify operations; remote DBs will automatically re-sync when the // failure is repaired. 02054, 00000, "transaction %s in-doubt" // *Cause: network or remote failure in 2PC. // *Action: Notify operations; DBs will automatically re-sync when the // failure is repaired. Monitor pending_trans$ for final outcome. 02055, 00000, "distributed update operation failed; rollback required" // *Cause: a failure during distributed update operation may not have // rolled back all effects of the operation. Since // some sites may be inconsistent, the transaction must roll back to // a savepoint or entirely // *Action: rollback to a savepoint or rollback transaction and resubmit 02056, 00000, "2PC: %s: bad two-phase command number %s from %s" // *Cause: two-phase commit protocol error. // *Action: recovery of transaction attempted. Monitor pending_trans$ table to // ensure correct resolution. Contact support. 02057, 00000, "2PC: %s: bad two-phase recovery state number %s from %s" // *Cause: internal error in two-phase recovery protocol // *Action: contact support 02058, 00000, "no prepared transaction found with ID %s" // *Cause: no transaction with local_tran_id or global_tran_id found in the // pending_trans$ table in prepared state. // *Action: check the pending_trans$ table. 02059, 00000, "ORA-2PC-CRASH-TEST-%s in commit comment" // *Cause: This is a special comment used to test the two phase commit. // *Action: Don't use this special comment (%s a number 1-10) 02060, 00000, "select for update specified a join of distributed tables" // *Cause: tables in a join with the for update clause must reside at the // same DB. 02061, 00000, "lock table specified list of distributed tables" // *Cause: tables in a lock table statement must reside at the same DB. // *Action: issue multiple lock table commands. 02062, 00000, "distributed recovery received DBID %s, expected %s" // *Cause: a database link at a coordinator no longer points to the expected // database. Link may have been redefined, or a different DB mounted. // *Action: restore link definition or remote database. 02063, 00000, "preceding %s%s from %s%s" // *Cause: an Oracle error was received from a remote database link. // *Action: refer to the preceding error message(s) 02064, 00000, "distributed operation not supported" // *Cause: One of the following unsupported operations was attempted: // 1. array execute of a remote update with a subquery that references // a dblink, or // 2. an update of a long column with bind variable and an update of // a second column with a subquery that both references a dblink // and a bind variable, or // 3. a commit is issued in a coordinated session from an RPC procedure // call with OUT parameters or function call. // *Action: simplify remote update statement 02065, 00000, "illegal option for ALTER SYSTEM" // *Cause: The option specified for ALTER SYSTEM is not supported // *Action: refer to the user manual for option supported 02066, 00000, "missing or invalid DISPATCHERS text" // *Cause: A character string literal was expected, but not found, following // ALTER SYSTEM SET DISPATCHERS // *Action: place the string literal containing the dispatcher's specification // after ALTER SYSTEM SET DISPATCHERS 02067, 00000, "transaction or savepoint rollback required" // *Cause: A failure (typically a trigger or stored procedure with multiple // remote updates) occurred such that the all-or-nothing execution // of a previous Oracle call cannot be guaranteed. // *Action: rollback to a previous savepoint or rollback the transaction // and resubmit. 02068, 00000, "following severe error from %s%s" // *Cause: A severe error (disconnect, fatal Oracle error) received from // the indicated database link. See following error text. // *Action: Contact the remote system administrator. 02069, 00000, "global_names parameter must be set to TRUE for this operation" // *Cause: A remote mapping of the statement is required but cannot be achieved // because global_names should be set to TRUE for it to be achieved // *Action: Issue alter session set global_names = true if possible 02070, 00000, "database %s%s does not support %s in this context" // *Cause: The remote database does not support the named capability in // the context in which it is used. // *Action: Simplify the SQL statement. // 02071, 00000, "error initializing capabilities for remote database %s" // *Cause: Could not load a remote-specified capability table. // *Action: Contact support for the remote SQL*Connect product. // 02072, 00000, "distributed database network protocol mismatch" // *Cause: This should never happen between different PRODUCTION releases of // ORACLE, but may happen between alpha and beta releases, for example. // *Action: Upgrade the older release. // 02073, 00000, "sequence numbers not supported in remote updates" // *Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES // on remote tables. // *Action: 02074, 00000, "cannot %s in a distributed transaction" // *Cause: A commit or rollback was attempted from session other than // the parent of a distributed transaction. // *Action: Only commit or rollback from the parent session. 02075, 00000, "another instance changed state of transaction %s" // *Cause: A commit force or rollback force was issued from a session // in another instance. // *Action: Check if another Oracle instance is performing recovery of pending // transactions. Query DBA_2PC_PENDING to determine the new state // of the transaction. 02076, 00000, "sequence not co-located with updated table or long column" // *Cause: all referenced sequences must be co-located with the table // with the long column. // 02077, 00000, "selects of long columns must be from co-located tables" // *Cause: if a select returns long columns from multiple tables, all the // tables must be co-located // 02078, 00000, "invalid setting for ALTER SYSTEM FIXED_DATE" // *Cause: // *Action: // 02079, 00000, "cannot join a committing distributed transaction" // *Cause: Once a transaction branch is prepared, no more new transaction // branches are allowed to start, nor is the prepared transaction // branch allowed to be joined. // *Action: Check the application code as this is an XA protocol violation. // 02080, 00000, "database link is in use" // *Cause: a transaction is active or a cursor is open on the database link // given in the alter session close database link command. // *Action: commit or rollback, and close all cursors // 02081, 00000, "database link is not open" // *Cause: dblink given is not currently open. // 02082, 00000, "a loopback database link must have a connection qualifier" // *Cause: An attempt was made to create a database link with the same name // as the current database. // *Action: a loopback database link needs a trailing qualifier, for example // MYDB.EXAMPLE.COM@INST1 - the '@INST1' is the qualifier // 02083, 00000, "database name has illegal character '%s'" // *Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' // '.' and '@' characters. // 02084, 00000, "database name is missing a component" // *Cause: supplied database name cannot contain a leading '.', // trailing '.' or '@', or two '.' or '@' in a row. // 02085, 00000, "database link %s connects to %s" // *Cause: a database link connected to a database with a different name. // The connection is rejected. // *Action: create a database link with the same name as the database it // connects to, or set global_names=false. // 02086, 00000, "database (link) name is too long" // *Cause: database/database link name can have at most 128 characters. 02087, 00000, "object locked by another process in same transaction" // *Cause: A database link is being used in the cluster database environment // that loops back to the same instance. One session is trying // to convert a lock that was obtained by the other session. // *Action: Get the more restrictive lock first. For example, if // session 1 gets a share lock and session 2 gets an exclusive lock // on the same object, get the exclusive lock first. Or, simply // use the same session to access the object. 02088, 00000, "distributed database option not installed" // *Cause: Remote and distributed updates and transactions are a separately // priced option in ORACLE V7. // 02089, 00000, "COMMIT is not allowed in a subordinate session" // *Cause: COMMIT was issued in a session that is not the two-phase commit // global coordinator. // *Action: Issue commit at the global coordinator only. // 02090, 00000, "network error: attempted callback+passthru" // *Cause: internal error. // 02091, 00000, "transaction rolled back" // *Cause: Also see error 2092. If the transaction is aborted at a remote // site then you will only see 2091; if aborted at host then you will // see 2092 and 2091. // *Action: Add rollback segment and retry the transaction. 02092, 00000, "out of transaction table slots for distributed transaction" // *Cause: The transaction is assigned to the system rollback segment and is // trying to get into the PREPARED state, but the required number // of non-PREPARED slots are not available, hence the transaction // is rolled back. // *Action: Add a rollback segment and retry the transaction. 02093, 00000, "TRANSACTIONS_PER_ROLLBACK_SEGMENT(%s) more than maximum possible(%s)" // *Cause: Value of parameter specified is greater than allowed on this port. // *Action: Use default or reduce it to less than max. 02094, 00000, "replication option not installed" // *Cause: The replication option was not installed at this site. Updatable // materialized views, deferred RPCs, and other replication features were, // therefore, unavailable. // *Action: Install the replication option. The replication option is not // part of the Oracle Server product and must be purchased // separately. Contact an Oracle Sales representative if the // replication option needs to be purchased. 02095, 00000, "specified initialization parameter cannot be modified" // *Cause: The specified initialization parameter is not modifiable 02096, 00000, "specified initialization parameter is not modifiable with this option" // *Cause: Though the initialization parameter is modifiable, it cannot be // modified using the specified command. // *Action: Check the DBA guide for information about under what scope // the parameter may be modified 02097, 00000, "parameter cannot be modified because specified value is invalid" // *Cause: Though the initialization parameter is modifiable, the modified // value is not acceptable to the parameter. // *Action: Check the DBA guide for range of acceptable values for this // parameter. 02098, 00000, "error parsing index-table reference (:I)" // *Cause: An incorrect index-table (:I) syntax was encountered. // *Action: This syntax is for oracle internal use only. 02099, 00000, "used for internal purposes, should never be printed" / / MODIFIED / shiyer 03/08/11 - Backport shiyer_bug-8498285 from main / jjlee 02/14/11 - Backport jjlee_bug-10398972 from main / skiyer 11/03/08 - 7298722:add error 03223 / jiashi 09/04/08 - add 3176 / shiyer 06/02/08 - Add 3147 / jiashi 04/01/08 - add ORA-3174, 3175 for ADG SLA / jaeblee 10/30/07 - fix bugs 6510941, 4402125 / jiashi 10/18/07 - add ORA-3172, 3173 for ADG SLA / krajaman 06/01/07 - Change 4023 message / mvemulap 06/06/07 - error 4035 / kigoyal 04/04/07 - add 3150, fix typos / shiyer 04/25/07 - add 3146 / avaliani 04/18/07 - fix typo in cause of ORA-02391 / nlee 03/13/07 - Add error message 4024. / rupsingh 01/17/07 - Add error message 3009 / sbodagal 11/16/06 - add 4023 / debanerj 08/09/06 - add 3145 / rpingte 06/08/06 - add messages 3142-3144 / jacao 06/01/06 - add message 3160 / shiyer 04/05/06 - add new error message for TTC proto errors / gtarora 04/19/06 - nt equipartition event / chliang 03/29/06 - add message 3140 and 3141 / avaliani 03/29/06 - incorporate erros_us feedback / sbedarka 11/16/05 - #(4736313) apply 4k limit for xpl pred to txt / mmpandey 11/02/05 - 4708558: make addition of tempfile in error 03284 / cmlim 11/09/05 - update action text for ORA-2352 & 2353 / yuli 10/31/05 - remove unused error numbers / cmlim 06/28/05 - bug 4373139 - cleanup error handling / chliang 04/25/05 - fix error text for 3135 / schandra 01/31/05 - remove error 4018 and friends / cmlim 03/18/05 - fix comment: dpapi msgs end w/ 26099, not 26999 / chliang 02/03/05 - add message 3135, 3136 / nmukherj 09/25/04 - added message 3254 / pbelknap 06/28/04 - plan diff errors / nmukherj 05/12/04 - / desinha 12/07/03 - 2531841: add 04069 / abande 10/14/03 - add error message 3134 / smalathe 08/19/03 - Bug#3051582: Add mesg 3133 / pokumar 07/28/03 - add message 4034 / cmlim 05/22/03 - bug 2885435: update cause/action of ORA-02368 / jstenois 03/04/03 - / jstenois 03/03/03 - 2775869: add message for bad rows during import / cmlim 03/27/03 - add 2368. obsolete 2353. / cmlim 02/17/03 - bug 2769696 / cmlim 02/03/03 - add 2354, 2355... for dpapi stream load/unload error / lilin 12/16/02 - Eliminate Thread Number, add 2188 / aramarao 11/11/02 - Message for disabling modifying of INITRANS for / hashed clusters / cmlim 11/05/02 - add err msgs for dirpath stream load/unload (#2351,...) / nwhyte 10/21/02 - Change "Average" to "average" on message 3222 per / review comments / ilam 08/30/02 - Add 2487, 2488 / porangas 10/17/02 - Fix bug#2607903 / wyang 09/11/02 - change 2142, 2180 / sbedarka 09/16/02 - #(2479110) handle pin deadlock error / nwhyte 08/21/02 - Add object growth trend and create table cost to / dbms_space / cmlim 07/01/02 - remove obsolete direct loader msgs. / reserve this range for 2351-2375 for direct path api. / bemeng 08/02/02 - add 3252 (initial extent size for LOB segment) / phchang 02/11/02 - #1941831: add error 2314 / smuralid 12/22/01 - eliminate 2312, 2313 etc / yuli 10/23/01 - tablespace rename project / smuthuli 08/01/01 - locally managed SYSTEM tablespace / yuli 07/26/01 - change oer 2142 and 2180 / smuthuli 06/07/01 - Change oer 3237 / weili 06/22/01 - bug 1755749 fix - remove 3232 / smuthuli 01/12/01 - add 3249 / vshukla 01/17/01 - Fix error message 2262. / gtarora 01/16/01 - add 2348 / dalpern 11/28/00 - privileges for kga debugger / smukkama 10/11/00 - add 3221 (disallow non-std block size temp segments) / amanikut 10/04/00 - modify 2321 / bhirano 09/03/00 - add out-of-memory error for pool growth / preilly 08/14/00 - Update description to fix bug 1164753 / lsheng 07/27/00 - update error message ORA-02204 / preilly 07/31/00 - Update error message for bug 1164753 / skaluska 06/23/00 - add 3119, 3132. / mjstewar 06/13/00 - OMF / bdagevil 04/18/00 - add error msg for memory management / nireland 03/20/00 - Amend ORA-3219 message. #1152302 / rmurthy 03/31/00 - inheritance related changes / apadmana 01/06/00 - change SNAPSHOT to MATERIALIZED VIEW / skray 12/13/99 - modified alter tracing messages 2480-2489 / smuthuli 04/28/99 - add 3247 / lcprice 07/01/99 - 746805 modify 3211 message / mjungerm 03/23/99 - fix comment in 04044 / weiwang 02/02/99 - add schema name to error 4098 / akruglik 06/30/98 - incorporate Randy's comments / akruglik 06/30/98 - define msgs 3238 and 3239 / ansriniv 04/13/98 - add OER(4047) - dbms_shared_pool / atsukerm 03/03/98 - add subpartition messages to DBMS_SPACE package. / tnbui 12/03/97 - Change error messages for validating a constraint / bgoyal 12/17/97 - error 2327 change column to expression / bhimatsi 03/03/98 - bitmapped ts - add error messages / atsukerm 02/06/98 - add dbms_space_admin errors. / mkcyee 11/03/97 - #(568232): add error 3206 / lcprice 08/19/97 - Merge of bug fix 461293 / jwlee 08/04/97 - Add error 4018 / akruglik 07/29/97 - add msgs 3233-3236 / mluong 06/24/97 - merge from 803 / nireland 06/24/97 - Add error message 2475. (#324089) / anolan 05/21/97 - checkout / mjaganna 06/11/97 - Change message 02160 / mluong 05/27/97 - fix merge problem / anolan 05/14/97 - Demo. / jbellemo 04/11/97 - remove 2343 / jbellemo 04/08/97 - undo 2303, add types to 2344 / thajek 03/24/97 - del 2346, modify 2303, readd 2344 / rjenkins 03/18/97 - changing 2256 / usundara 01/03/97 - add error 2311 for bug 434240 / usundara 12/31/96 - incomplete and mutually-dependent types (add ora-4055) / bcchang 12/20/96 - error.msg split / / 2100 .. 2139 - Reserved for precompiler runtime (SQLLIB) / 02100, 00000, "PCC: out of memory (i.e., could not allocate)" 02101, 00000, "PCC: inconsistent cursor cache (uce/cuc mismatch)" 02102, 00000, "PCC: inconsistent cursor cache (no cuc entry for this uce)" 02103, 00000, "PCC: inconsistent cursor cache (out-of-range cuc ref)" 02104, 00000, "PCC: inconsistent host cache (no cuc available)" 02105, 00000, "PCC: inconsistent cursor cache (no cuc entry in cache)" 02106, 00000, "PCC: inconsistent cursor cache (OraCursor nr is bad)" 02107, 00000, "PCC: this pgm too old for run-time library: please re-PCC it" 02108, 00000, "PCC: invalid descriptor passed to run-time library" 02109, 00000, "PCC: inconsistent host cache (out-of-range sit ref)" 02110, 00000, "PCC: inconsistent host cache (invalid sqi type)" 02111, 00000, "PCC: heap consistency error" 02112, 00000, "PCC: SELECT..INTO returns too many rows" / / 2140 .. 2499 - V6 parser errors continued / parser errors continued at 25000 / 02140, 00000, "invalid tablespace name" // *Cause: An identifier does not follow ALTER TABLESPACE. // *Action: Specify a tablespace name following ALTER TABLESPACE. 02141, 00000, "invalid OFFLINE option" // *Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE. // *Action: The user must either specify no option following OFFLINE or // one of the options NORMAL or IMMEDIATE. 02142, 00000, "missing or invalid ALTER TABLESPACE option" // *Cause: A valid option was not present. // *Action: Use one of the valid options: add, rename, default, online, // offline, read only, read write, begin, end, no, force, // retention guarantee and retention noguarantee. 02143, 00000, "invalid STORAGE option" // *Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or // PCTINCREASE was specified in the STORAGE clause. // *Action: Specify only valid options. 02144, 00000, "no option specified for ALTER CLUSTER" // *Cause: No ALTER CLUSTER options are specified. // *Action: Specify one or more of the following options: pctfree, // pctused, size, storage. 02145, 00000, "missing STORAGE option" // *Cause: No STORAGE options were specified following STORAGE ( // *Action: Specify one or more STORAGE option between the // parentheses. 02146, 00000, "SHARED specified multiple times" // *Cause: The SHARED option was specified in a CREATE DATABASE // statement multiple times. // *Action: Only specify the SHARED option once. 02147, 00000, "conflicting SHARED/EXCLUSIVE options" // *Cause: Both the SHARED and EXCLUSIVE options were specified in a // CREATE DATABASE statement. // *Action: Specify SHARED or EXCLUSIVE, but not both. 02148, 00000, "EXCLUSIVE specified multiple times" // *Cause: The EXCLUSIVE option was specified in a CREATE DATABASE // statement multiple times. // *Action: Only specify the EXCLUSIVE option once. 02149, 00000, "Specified partition does not exist" // *Cause: Partition not found for the object. // *Action: Retry with correct partition name. 02150, 00000, "invalid new tablespace name" // *Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO // statement was invalid. // *Action: Retry with a valid new tablespace name. 02151, 00000, "invalid tablespace name: %s" // *Cause: Oracle cannot create a tablespace whose name starts with // '_$deleted$'. // *Action: Try a different tablespace name. 02152, 00000, "Invalid ALTER TABLESPACE ... RENAME option" // *Cause: An option other than DATAFILE or TO follows by ALTER // TABLESPACE ... RENAME. // *Action: The user must specify either DATAFILE or TO following ALTER // TABLESPACE ... RENAME. 02153, 00000, "invalid VALUES password string" // *Cause: An encoded password string does not follow the VALUES clause. // *Action: Place a proper encoded password string after the VALUES clause. 02154, 00000, "a tablespace with the name '%s' is found" // *Cause: An attempt to rename a tablespace to a new name failed because // the new name is already used by some other tablespace. // *Action: Retry with a different new name. 02155, 00000, "invalid DEFAULT tablespace identifier" // *Cause: An identifier does not follow DEFAULT TABLESPACE. // *Action: Place a tablespace name after DEFAULT TABLESPACE. 02156, 00000, "invalid TEMPORARY tablespace identifier" // *Cause: An identifier does not follow TEMPORARY TABLESPACE. // *Action: Place a tablespace name after TEMPORARY TABLESPACE. 02157, 00000, "no options specified for ALTER USER" // *Cause: No options were specified. // *Action: Specify at least one ALTER USER option. 02158, 00000, "invalid CREATE INDEX option" // *Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, // MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, // UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified. // *Action: Choose one of the valid CREATE INDEX options. 02159, 00000, "installed DLM does not support releasable locking mode" // *Cause: The parameter file specified gc_* parameters that allow locks // to be release by the LCK process when not in use. This mode // requires additional support from the DLM that is not available. // *Action: Specify configuration parameters that do not require the // additional function. 02160, 00000, "index-organized table can not contain columns of type LONG" // *Cause: A column of type LONG defined for index-organized table. // *Action: Do not use columns of type LONG in index-organized tables. 02161, 00000, "invalid value for MAXLOGFILES" // *Cause: A number does not follow MAXLOGFILES. // *Action: Specify a number after MAXLOGFILES. 02162, 00000, "invalid value for MAXDATAFILES" // *Cause: A number does not follow MAXDATAFILES. // *Action: Specify a number after MAXDATAFILES. 02163, 00000, "invalid value for FREELIST GROUPS" // *Cause: A number does not follow FREELIST GROUPS. // *Action: Specify a number after FREELIST GROUPS. 02164, 00000, "DATAFILE clause specified more than once" // *Cause: The CREATE DATABASE command contains more than one DATAFILE clause. // *Action: Specify at most one DATAFILE clause. 02165, 00000, "invalid option for CREATE DATABASE" // *Cause: An invalid CREATE DATABASE option is present. // *Action: Specify only valid CREATE DATABASE options. 02166, 00000, "ARCHIVELOG and NOARCHIVELOG specified" // *Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a // CREATE DATABASE statement. // *Action: Specify at most one of these two options. 02167, 00000, "LOGFILE clause specified more than once" // *Cause: The CREATE DATABASE command contains more than one LOGFILE clause. // *Action: Specify at most one LOGFILE clause. 02168, 00000, "invalid value for FREELISTS" // *Cause: A number does not follow FREELISTS // *Action: Specify a number after FREELISTS 02169, 00000, "FREELISTS storage option not allowed" // *Cause: The user attempted to specify the FREELISTS storage // option. This option may only be specified during // create table or create index. // *Action: Remove these options and retry the statement. 02170, 00000, "FREELIST GROUPS storage option not allowed" // *Cause: The user attempted to specify the FREELIST GROUPS storage // option. This option may only be specified during create // table and when allow_freelist_groups INIT.ORA is specified. // *Action: Remove this option and retry the statement or set the // allow_freelist_groups INIT.ORA parameter. 02171, 00000, "invalid value for MAXLOGHISTORY" // *Cause: A number does not follow MAXLOGHISTORY // *Action: Specify a number after MAXLOGHISTORY 02172, 00000, "The PUBLIC keyword is not appropriate for a disable thread" // *Cause: The PUBLIC keyword was specified for a disable. // *Action: Remove the keyword and resubmit. 02173, 00000, "invalid option for DROP TABLESPACE" // *Cause: Either a token other than INCLUDING was found following the // tablespace name or some text was found following INCLUDING CONTENTS. // *Action: Place nothing or only INCLUDING CONTENTS after the tablespace name. 02174, 00000, "Missing required thread number" // *Cause: Must specify thread number after THREAD keyword // *Action: 02175, 00000, "invalid rollback segment name" // *Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier // was not found following ROLLBACK SEGMENT. // *Action: Place the segment name following ROLLBACK SEGMENT. 02176, 00000, "invalid option for CREATE ROLLBACK SEGMENT" // *Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement. // *Action: Specify one of the valid options: TABLESPACE and STORAGE. 02177, 00000, "Missing required group number" // *Cause: Must specify group number after GROUP keyword // *Action: 02178, 00000, "correct syntax is: SET TRANSACTION READ { ONLY | WRITE }" // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02179, 00000, "valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }" // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02180, 00000, "invalid option for CREATE TABLESPACE" // *Cause: An invalid option appeared. // *Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, // ONLINE, OFFLINE, FORCE, RETENTION. 02181, 00000, "invalid option to ROLLBACK WORK" // *Cause: A token other than TO follows ROLLBACK [WORK]. // *Action: Place nothing or TO SAVEPOINT after ROLLBACK [WORK]. 02182, 00000, "savepoint name expected" // *Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT]. // *Action: Place a savepoint name following TO [SAVEPOINT]. 02183, 00000, "valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }" // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02184, 00000, "resource quotas are not allowed in REVOKE" // *Cause: In a revoke statement, a resource quota was specified. // *Action: Specify resource privilege without the quota. 02185, 00000, "a token other than WORK follows COMMIT" // *Cause: A token other than WORK follows COMMIT. // *Action: Place either nothing or WORK after COMMIT. 02186, 00000, "tablespace resource privilege may not appear with other privileges" // *Cause: An attempt was made to grant or revoke a resource quota in the // same statement in which other privileges are granted or revoked. // *Action: Use a separate grant or revoke statement for the resource // quota privilege. 02187, 00000, "invalid quota specification" // *Cause: In a grant or revoke statement, the user attempted to grant // a tablespace quota above the upper limit. // *Action: Grant a smaller tablespace quota. 02188, 00000, "Cannot enable instance publicly" // *Cause: An attempt was made to publicly enable a thread associated // with an instance. // *Action:Leave out the PUBLIC keyword. 02189, 00000, "ON 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 // type or table dependents. // *Action: For DROP TYPE, drop all type(s) and table(s) depending on the // type and then retry the operation, or use the FORCE option. // For CREATE TYPE, drop all type(s) and table(s) depending on the // type and then retry the operation, or drop all table(s) depending // on the type and retry with the FORCE option. 02304, 00000, "invalid object identifier literal" // *Cause: An attempt was made to enter an object identifier literal for // CREATE TYPE that is either: // - not a string of 32 hexadecimal characters // - an object identifier that already identifies an existing // object // - an object identifier different from the original object // identifier already assigned to the type // *Action: Do not specify the object identifier clause or specify a 32 // hexadecimal-character object identifier literal that is unique // or identical to the originally assigned object identifier. Then // retry the operation. 02305, 00000, "only EXECUTE, DEBUG, and UNDER privileges are valid for types" // *Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not // EXECUTE, DEBUG, or UNDER) on a type. // *Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on // types. 02306, 00000, "cannot create a type that already has valid dependent(s)" // *Cause: An attempt was made to create a type that already has some // valid dependent(s) (these dependents depend on the fact that // the type does not exist). // *Action: Drop the dependents first before creating the type, or do not // create the type. 02307, 00000, "cannot alter with REPLACE option a type that is not valid" // *Cause: An attempt was made to ALTER with REPLACE option a type that // is not valid. // *Action: Use the CREATE OR REPLACE TYPE command to modify the type. 02308, 00000, "invalid option %s for object type column" // *Cause: An attempt was made to specify an invalid option, such as PACKED // or UNPACKED, for the object type column. // *Action: Remove the invalid option from column specification and retry // the operation. 02309, 00000, "atomic NULL violation" // *Cause: An attempt was made to acess the attributes of a NULL object // instance. // *Action: Ensure that the object instance is non-NULL before accessing. 02310, 00000, "exceeded maximum number of allowable columns in table" // *Cause: The attributes in the object type column exceeded the maximum // number of columns allowed in a table. // *Action: Specify fewer attributes for the object type and retry the // operation. 02311, 00000, "cannot alter with COMPILE option a valid type with type or table dependents" // *Cause: An attempt was made to ALTER with COMPILE option a type that is // valid and has type or table dependents. // *Action: No need to perform this operation. // 02313, 00000, "object type contains non-queryable type %s attribute" // *Cause: The specified object type contains a nested attribute whose type // is non-queryable. // *Action: Use an object type with queryable attribute types. 02314, 00000, "illegal use of type constructor" // *Cause: The statement contains an illegal use of a type constructor. // *Action: Refer to the SQL Reference manual for the correct statement syntax. 02315, 00000, "incorrect number of arguments for default constructor" // *Cause: The number of arguments specified for the default constructor // doesn't match the number of attributes of the object type. // *Action: Specify the correct number of arguments for the default // constructor and retry the operation. 02320, 00000, "failure in creating storage table for nested table column %s" // *Cause: An error occurred while creating the storage table for the // specified nested table column. // *Action: See the messages that follow for more details. If the situation // they describe can be corrected, do so; otherwise contact Oracle // Support. 02321, 00000, "event for nested table equipartition" // *Document: NO // *Cause: // *Action: 02322, 00000, "failure in accessing storage table of the nested table column" // *Cause: An error occured while performing DML on the storage table of the // nested table column. // *Action: If the situation described in the following messages can be // corrected, do so; otherwise contact Oracle Support. 02324, 00000, "more than one column in the SELECT list of THE subquery" // *Cause: More than one column was selected in the THE subquery. // *Action: Specify only one column in the SELECT list of the THE subquery and // retry the operation. 02327, 00000, "cannot create index on expression with datatype %s" // *Cause: An attempt was made to create an index on a non-indexable // expression. // *Action: Change the column datatype or do not create the index on an // expression whose datatype is one of VARRAY, nested table, object, // LOB, or REF. 02329, 00000, "column of datatype %s cannot be unique or a primary key" // *Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint // on a column of datatype VARRAY, nested table, object, LOB, FILE // or REF. // *Action: Change the column datatype or remove the constraint. Then retry // the operation. 02330, 00000, "datatype specification not allowed" // *Cause: An attempt was made to specify the data type in the column // constraint specification of an object table. // *Action: Remove data type specification and retry the operation. 02331, 00000, "cannot create constraint on column of datatype %s" // *Cause: An attempt was made to create a constraint on a column // posessing a non-constrainable datatype -- VARRAY, nested table, // object, LOB, FILE, or REF. // *Action: Change the column datatype, or remove the constraint. 02332, 00000, "cannot create index on attributes of this column" // *Cause: An attempt was made to create an index on an attributes of an // object type column. // *Action: Do not specify the index on the attribute. 02333, 00000, "cannot create constraints on attributes of this column" // *Cause: An attempt was made to create a constraint on an attribute of // an object type column. // *Action: Remove the constraint or change the object type. 02334, 00000, "cannot infer type for column" // *Cause: A datatype was not declared for this column (in the CREATE TABLE) // and an attempt was made to create a constraint on an attribute of // this column. // *Action: Declare a datatype for the column. 02335, 00000, "invalid datatype for cluster column" // *Cause: An attempt was made to declare a CLUSTER column of datatype // object, REF, nested table, VARRAY, LOB, or FILE. // *Action: Remove the CLUSTER column or change the datatype of the column. 02336, 00000, "column attribute cannot be accessed" // *Cause: An attempt was made to extract an attribute of an object type // column. // *Action: Change the object type for the column and retry the operation. 02337, 00000, "not an object type column" // *Cause: An attempt was made to use dotted notation on a non-ADT column; // that is, "a.b.c" where "a" is not an object type. // *Action: Either change the column type to an object type or do not // perform this operation. 02338, 00000, "missing or invalid column constraint specification" // *Cause: A column constraint was not specified. // *Action: Remove the column specification or specify a column constraint. // Then retry the operation. 02339, 00000, "invalid column specification" // *Cause: An attempt was made to specify the PACKED or UNPACKED keyword // for a non-object type column. // *Action: Remove the PACKED or UNPACKED keyword in the column // specification and retry the operation. 02340, 00000, "invalid column specification" // *Cause: An attempt was made to specify an UNPACKED column within a // packed table. // *Action: Remove the UNPACKED keyword in the column specification. 02342, 00000, "replacement type has compilation errors" // *Cause: The use of the ALTER...REPLACE statement on a valid type caused // a compilation error. // *Action: Use the ALTER...REPLACE statement to replace the type with a valid // type which does not cause compilation errors. 02344, 00000, "cannot revoke execute on a type with table dependents" // *Cause: An attempt was made to revoke execute on a type that has // dependents. // *Action: Drop all table(s) depending on the type, then retry // the operation, or use the FORCE option. 02345, 00000, "cannot create a view with column based on CURSOR operator" // *Cause: A CURSOR operator was used as one of the SELECT elements in the // subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement. // *Action: Remove the CURSOR operator and replace it with the CAST operator. 02347, 00000, "cannot grant privileges on columns of an object table" // *Cause: An attempt was made to grant privileges on the columns of an // object table. // *Action: 02348, 00000, "cannot create VARRAY column with embedded LOB" // *Cause: An attempt was made to create a column of a VARRAY type which // has an embedded LOB attribute. The LOB could be an attribute of // a subtype of the declared type of VARRAY's element. // *Action: Remove offending attribute from type. If it is a subtype attribute // then declare the VARRAY column NOT SUBSTITUTABLE. 02349, 00000, "invalid user-defined type - type is incomplete" // *Cause: An attempt was made to use an incomplete type definition as a // column or table datatype. // *Action: Complete the type definition and retry the operation. / / / / 2351 - 2375 Directh Path API errors / - 2356, 2366, 2371, & 2373: direct loader errors / - 2351 - 2355, / 2357 - 2365, / 2367 - 2370, / 2372, / 2374 - 2375: / see also range 2476 - 2479 for Parallel Direct Loader errors / and range 26000 - 26099 for additional Direct Path Load errors / 02351, 00000, "internal error: %s\n" // *Cause: An unexpected error condition was detected. // *Action: Make a note of the error number and message and contact // Oracle Support Services. 02352, 00000, "error setting an OCI attribute: %s\n" // *Cause: An OCI error has occurred. // *Action: The table or column referenced may not be accessible. Contact // Oracle Support Services if the problem cannot be resolved. 02353, 00000, "error fetching an OCI attribute: %s\n" // *Cause: An OCI error has occurred. // *Action: The table or column referenced may not be accessible. Contact // Oracle Support Services if the problem cannot be resolved. 02354, 00000, "error in exporting/importing data\n%s" // *Cause: An error has occurred in a stream export or import operation. // This message will be followed by another message giving more // details about this error. // *Action: See export/import documentation for an explanation of the second // error message. 02355, 00000, "error opening file: %s\n" // *Cause: An attempt to open the specified file for data export/import failed. // *Action: Review the error message. Resolve the problem and retry the // the operation. Contact Oracle Support Services if // the problem cannot be resolved. 02356, 00000, "The database is out of space. The load cannot continue" // *Cause: The load was discontinued due to space exhaustion in the database. // *Action: Add space for the specified table. 02357, 00000, "header in file %s may not contain correct information\n" // *Cause: The header may be corrupted. // *Action: Contact Oracle Support Services. 02358, 00000, "error in exporting or importing data\n" // *Cause: An error has occurred in a stream export or import operation. // *Action: Contact Oracle Support Services. 02359, 00000, "database version in file %s is not valid\n" // *Cause: The specified file could not be used for this load because // its database version was not compatible with the database version // in the other files in the DUMPFILE clause. // *Action: Verify all the files in the DUMPFILE clause are from // the same unload operation. 02360, 00000, "fatal error during data export/import initialization\n" // *Cause: An unexpected error occurred during initialization for data // export/import. // *Action: Contact Oracle Support Services. 02361, 00000, "error while attempting to allocate %d bytes of memory\n" // *Cause: An error occurred while trying to allocate memory. This is likely // caused by insufficient memory. // *Action: Reconnect to the instance and retry the operation. 02362, 00000, "error closing file: %s\n" // *Cause: An attempt to close the specified file for data export/import failed. // *Action: Review the error message. Resolve the problem and retry the // the operation. Contact Oracle Support Services if // the problem cannot be resolved. 02363, 00000, "error reading from file: %s\n" // *Cause: An attempt to read from the specified file for data export/import // failed. // *Action: Review the error message. Resolve the problem and retry the // the operation. Contact Oracle Support Services if // the problem cannot be resolved. 02364, 00000, "error writing to file: %s\n" // *Cause: An attempt to write to the specified file for data export/import // failed. // *Action: Review the error message. Resolve the problem and retry the // the operation. Contact Oracle Support Services if / the problem cannot be resolved. 02365, 00000, "error seeking in file: %s\n" // *Cause: An attempt to seek to the specified position in file failed. // *Action: Review the error message. Resolve the problem and retry the // the operation. Contact Oracle Support Services if / the problem cannot be resolved. 02366, 00000, "The following index(es) on table %s were processed:" // *Cause: The table had some indexes which were loaded if there were no errors. // *Action: none. 02367, 00000, "read ended but had expected more data from file %s\n" // *Cause: A truncated or incomplete file was used for the load operation. // *Action: Verify unload operation completed successfully and that the // files had not been accidentally truncated. 02368, 00000, "the following file is not valid for this load operation\n" // *Cause: A file could not be used for this load. // See the following message for more information. // *Action: Verify all the files in the DUMPFILE clause are from // the same unload operation and that the unload was successful. 02369, 00000, "internal number in header in file %s is not valid\n" // *Cause: The specified file could not be used for this load because the // internal number in the header was not valid. // *Action: If the dump files were transferred over, verify the // transfer operation was done correctly. 02370, 00000, "internal metadata in file %s is not valid\n" // *Cause: The specified file could not be used for this load because the // internal metadata stored in this file does not match the metadata // stored in the first file piece set. // *Action: Verify all the files in the DUMPFILE clause are from // the same unload operation. 02371, 00000, "Loader must be at least version %s.%s.%s.%s.%s for direct path" // *Cause: The loader being used is incompatible with this version of the // kernel. // *Action: Upgrade your loader to at least the specified version or use the // conventional path. 02372, 00000, "data for row: %*.*s \n" // *Cause: A conversion error occurred while loading data into a table. The // message shows values for the field in the row that had // the conversion error. // *Action: None. This is only an informational message. 02373, 00000, "Error parsing insert statement for table %s." // *Cause: self-evident. // *Action: Check the error given below this one. 02374, 00000, "conversion error loading table %*.*s.%*.*s" // *Cause: A row could not be loaded into the table because there was a // conversion error for one or more columns in a row. // *Action: See the message that follows for more information about the row // that could not be loaded. To avoid this error, make sure the // definition of the table being imported matches the definition of // the table being exported. 02375, 0, "conversion error loading table %*.*s.%*.*s partition %*.*s" // *Cause: A row could not be loaded into the table because there was a // conversion error for one or more columns in a row. // *Action: See the message that follows for more information about the row // that could not be loaded. To avoid this error, make sure the // definition of the table being imported matches the definition of // the table being exported. / / 2376 - 2399 Resource limit errors / 02376, 00000, "invalid or redundant resource" // *Cause: a create, or alter profile command which names a resource not // yet defined, or try to specify same resource twice. // *Action: define resource first 02377, 00000, "invalid resource limit" // *Cause: specifying limit of 0 // *Action: specify limit > 0 02378, 00000, "duplicate resource name %s" // *Cause: // *Action: 02379, 00000, "profile %s already exists" // *Cause: Try to create a profile which already exist // *Action: 02380, 00000, "profile %s does not exist" // *Cause: Try to assign a user to a non-existant profile // *Action: 02381, 00000, "cannot drop PUBLIC_DEFAULT profile" // *Cause: Try to drop PUBLIC_DEFAULT profile // *Action: 02382, 00000, "profile %s has users assigned, cannot drop without CASCADE" // *Cause: // *Action: 02383, 00000, "illegal cost factor" // *Cause: Negative or UNLIMITED cost for this resourc // *Action: 02390, 00000, "exceeded COMPOSITE_LIMIT, you are being logged off" // *Cause: // *Action: 02391, 00000, "exceeded simultaneous SESSIONS_PER_USER limit" // *Cause: An attempt was made to exceed the maximum number of // concurrent sessions allowed by the SESSION_PER_USER clause // of the user profile. // *Action: End one or more concurrent sessions or ask the database // administrator to increase the SESSION_PER_USER limit of // the user profile. 02392, 00000, "exceeded session limit on CPU usage, you are being logged off" // *Cause: // *Action: 02393, 00000, "exceeded call limit on CPU usage" // *Cause: // *Action: 02394, 00000, "exceeded session limit on IO usage, you are being logged off" // *Cause: // *Action: 02395, 00000, "exceeded call limit on IO usage" // *Cause: // *Action: 02396, 00000, "exceeded maximum idle time, please connect again" // *Cause: as stated // *Action: 02397, 00000, "exceeded PRIVATE_SGA limit, you are being logged off" // *Cause: Only when using TP monitor // *Action: expand limit 02398, 00000, "exceeded procedure space usage" // *Cause: Stored procedured used up too much space in SYSTEM Tablespace // *Action: Use less stored procedure 02399, 00000, "exceeded maximum connect time, you are being logged off" // *Cause: As stated // *Action: / / 2400 - 2479 EXPLAIN facility errors / 02400, 00000, "explain plan output buffer size limit exceeded" // *Cause: Internally this error is raised and caught to handle cases where // the plan output exceeds te buffer size. The output is truncated in // cases. // *Action: This error should never be seen externally. 02401, 00000, "cannot EXPLAIN view owned by another user" // *Cause: The view specified in the SQL statement belongs to another user // and cannot be explained. // *Action: Create a view with the same definition that belongs to // current user. 02402, 00000, "PLAN_TABLE not found" // *Cause: The table used by EXPLAIN to store row source information does // not exist in the current schema. // *Action: Create a plan table in the current schema or use the INTO clause // of the statement to put the results of the explain command in an // existing plan table. 02403, 00000, "plan table does not have correct format" // *Cause: The explicit plan table does not have the appropriate field // definitions. // *Action: Redefine the plan table to have the appropriate field definitions. 02404, 00000, "specified plan table not found" // *Cause: The specified plan table does cannot be found. // *Action: Create the specified plan table or use an existing plan table. 02405, 00000, "invalid sql plan object provided" // *Cause: The user provided a NULL, empty, or malformed object of type // SQL_PLAN_TABLE_TYPE // *Action: Provide a new, properly formed object to the function / / 2420 - 2429 Schema errors / 02420, 00000, "missing schema authorization clause" // *Cause: the AUTHORIZATION clause is missing from a create schema // statement. // *Action: Preceed the schema authorization identifier with the // AUTHORIZATION keyword. 02421, 00000, "missing or invalid schema authorization identifier" // *Cause: the schema name is missing or is incorrect in an authorization // clause of a create schema statement. // *Action: If the name is present, it must be the same as the current // schema. 02422, 00000, "missing or invalid schema element" // *Cause: A statement other than a create table, create view, or grant // privilege appears in a create schema statement. // *Action: Self-evident. 02423, 00000, "schema name does not match schema authorization identifier" // *Cause: a table definition with a schema name prepended to the table // name does not match the schema name provided in the authorization // clause of a create schema statement. // *Action: make sure the schema names match. 02424, 00000, "potential circular view references or unknown referenced tables" // *Cause: the create schema statement contains views that depend on other // views in the containing create schema statement or they contain // references to unknown tables. // *Action: create the dependent views in a separate create schema statement // and make sure all referenced tables are either defined in the // create schema statement or exist outside the statement. 02425, 00000, "create table failed" // *Cause: a create table statement failed in the create schema statement. // *Action: the cause for failure will be presented below this error message. // Follow appropriate action(s) as suggested by the subsequent error // message. 02426, 00000, "privilege grant failed" // *Cause: a grant privilege statement failed inthe create schema statement. // *Action: the cause for failure will be presented below this error message. // Follow appropriate action(s) as suggested by the subsequent error // message. 02427, 00000, "create view failed" // *Cause: a create view statement failed in the create schema statement. // *Action: the cause for failure will be presented below this error message. // Follow appropriate action(s) as suggested by the subsequent error // message. 02428, 00000, "could not add foreign key reference" // *Cause: could not add a foreign key reference because of error in // declaration. Either referenced table does not exist or // table does not have an unique key. // *Action: make sure referenced table exists and/or has unique key 02429, 00000, "cannot drop index used for enforcement of unique/primary key" // *Cause: user attempted to drop an index that is being used as the // enforcement mechanism for unique or primary key. // *Action: drop the constraint instead of the index. / / 2430 - Enable/Disable Constraint Error Messages - continued / 02430, 00000, "cannot enable constraint (%s) - no such constraint" // *Cause: the named constraint does not exist for this table. // *Action: Obvious 02431, 00000, "cannot disable constraint (%s) - no such constraint" // *Cause: the named constraint does not exist for this table. // *Action: Obvious 02432, 00000, "cannot enable primary key - primary key not defined for table" // *Cause: Attempted to enable a primary key that is not defined for the table. // *Action: Need to add a primary key definition for the table. 02433, 00000, "cannot disable primary key - primary key not defined for table" // *Cause: Attempted to disable a primary key tht is not defined for the // table. // *Action: None 02434, 00000, "cannot enable unique(%s) - unique key not defined for table" // *Cause: attempted to enable a unique key that is not defined for the table. // *Action: None 02435, 00000, "cannot disable unique(%s) - unique key not defined for table" // *Cause: attempted to disable a unique key that is not deined for the table. // *Action: None 02436, 00000, "date or system variable wrongly specified in CHECK constraint" // *Cause: An attempt was made to use a date constant or system variable, // such as USER, in a check constraint that was not completely // specified in a CREATE TABLE or ALTER TABLE statement. For // example, a date was specified without the century. // *Action: Completely specify the date constant or system variable. // Setting the event 10149 allows constraints like "a1 > '10-MAY-96'", // which a bug permitted to be created before version 8. 02437, 00000, "cannot validate (%s.%s) - primary key violated" // *Cause: attempted to validate a primary key with duplicate values or null // values. // *Action: remove the duplicates and null values before enabling a primary // key. 02438, 00000, "Column check constraint cannot reference other columns" // *Cause: attempted to define a column check constraint that references // another column. // *Action: define it as a table check constriant. 02439, 00000, "Unique index on a deferrable constraint is not allowed" // *Cause: attempted to enable a deferrable primary key/unique constraint // that has an existing unique index on the constraint columns. // *Action: Drop the index on the constraint columns or make the constraint // not deferrable. 02440, 00000, "Create as select with referential constraints not allowed" // *Cause: create table foo (... ref. con. ...) as select ...; // *Action: Create the table as select, then alter the table to add the // constraints afterwards. 02441, 00000, "Cannot drop nonexistent primary key" // *Cause: alter table drop primary key - primary key does not exist. // *Action: None 02442, 00000, "Cannot drop nonexistent unique key" // *Cause: alter table drop unique () - 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 and INITRANS options cannot be altered for HASH CLUSTERS." // *Cause: An attempt was made to change the SIZE and INITRANS options after // the hash cluster was created. // *Action: Do not specify this option. 02467, 00000, "Column referenced in expression not found in cluster definition" // *Cause: A column in the hash is expression was not present in cluster // definition. // *Action: Recreate the cluster and correct the error in hash expression. 02468, 00000, "Constant or system variable wrongly specified in expression" // *Cause: A constant or system variable was specified in the hash expression. // *Action: Recreate the cluster and correct the error in hash expression. 02469, 00000, "Hash expression does not return an Oracle Number." // *Cause: Result of evaluating hash expression is not an Oracle Number. // *Action: Recreate the cluster and correct the error in hash expression. 02470, 00000, "TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression." // *Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions. // *Action: Recreate the cluster and correct the error in hash expression. 02471, 00000, "SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion." // *Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s. // *Action: Recreate the cluster and remove the offending keywords. 02472, 00000, "PL/SQL functions not allowed in hash expressions" // *Cause: A PL/SQL function was used in the hash expression. // *Action: Recreate the cluster and remove the PL/SQL function. 02473, 00000, "Error while evaluating the cluster's hash expression." // *Cause: An error occurred while evaluating the clusters hash expression. // *Action: Correct the query and retry. 02474, 00000, "Fixed hash area extents used (%s) exceeds maximum allowed (%s)" // *Cause: The number of extents required for creating the fixed hash // area exceeds the maximum number allowed. // *Action: Reduce the number of extents required by increasing the extent // allocation sizes within the STORAGE clause. 02475, 00000, "maximum cluster chain block count of %s has been exceeded" // *Cause: The number of blocks in a cluster chain exceeds the maximum // number allowed. // *Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider // suitability of cluster key. / / 2476 - 2479 Reserved for Parallel Direct Loader Errors 02476, 00000, "can not create index due to parallel direct load on table" // *Cause: A parallel direct load is occurring to the specified table. // *Action: Retry statement after load is complete. 02477, 00000, "can not perform parallel direct load on object %s" // *Cause: A parallel direct load is not possible because an index is // is being created on the table. // *Action: Retry load after index creation is complete. 02478, 00000, "merge into base segment would overflow MAXEXTENTS limit" // *Cause: Merge of temporary segment into base segment failed because // MAXEXTENTS was larger than the total in the temp and base segments // *Action: Use a larger value for MAXEXTENTS on the base segment or make the // extents in the temporary segments larger 02479, 00000, "error while translating file name for parallel load" // *Cause: An invalid file name was specified to load data into. // *Action: Specify a valid database file. / / 2480 - 2489 Trace facility errors / 02481, 00000, "Too many processes specified for events (max %s)" // *Cause: Too many processes specified than allowed per event. // *Action: Enter fewer processes by using ranges or wildcards if possible. 02482, 00000, "Syntax error in event specification (%s)" // *Cause: Illegal event string // *Action: Enter a legal event string 02483, 00000, "Syntax error in process specification (%s)" // *Cause: Illegal process string // *Action: Enter a legal process string 02484, 00000, "Invalid _trace_buffers parameter specification (%s)" // *Cause: Bad process or size in _trace_buffers INIT.ORA parameter. // *Action: 02485, 00000, "Invalid _trace_options parameter specification (%s)" // *Cause: Bad syntax for _trace_options INIT.ORA parameter. // *Action: 02486, 00000, "Error in writing trace file %s" // *Cause: Error occurred in creating/writing the file. // *Action: Check file name and make sure it is constructed properly. // Also, check permissions for directories. 02487, 00000, "Error in converting trace data" // *Cause: Incompatible binary trace data was specified. // *Action: Check the format of the input data. 02488, 00000, "Error encountered when accessing file [%s] for trace conversion" // *Cause: An attempt was made to open or access the trace file during // a trace conversion. // *Action: Check the permissions for both input and output files. // Also, check the file compatibility for the trace conversion. / / 2490 - 2499 Reserved for Resizeable Datafiles / 02490, 00000, "missing required file size in RESIZE clause" // *Cause: No value was specified for the RESIZE clause. // *Action: Use correct syntax. 02491, 00000, "missing required keyword ON or OFF in AUTOEXTEND clause" // *Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause. // *Action: Use correct syntax. 02492, 00000, "missing required file block increment size in NEXT clause" // *Cause: No value was specified for the NEXT clause. // *Action: Use correct syntax. 02493, 00000, "invalid file increment size in NEXT clause" // *Cause: A non-integer value was used for the NEXT clause of the DATAFILE // list. // *Action: Use correct syntax. 02494, 00000, "invalid or missing maximum file size in MAXSIZE clause" // *Cause: UNLIMITED was not specified, or an invalid integer value was // specified, for the MAXSIZE clause in the DATAFILE file list. // The MAXSIZE value cannot be smaller than the SIZE value. // *Action: Use correct syntax. 02495, 00000, "cannot resize file %s, tablespace %s is read only" // *Cause: An attempt was made to resize a data file in a tablespace that // is read only. // *Action: Change the tablespace to read/write and retry the resize operation. / / 2500 - 2699 Reserved for CTOS-specific errors / / 2700 - 2899 Reserved for UNIX two-task errors / 02700, 00000, "osnoraenv: error translating ORACLE_SID" // *Cause: Two-task driver could not find the value of ORACLE_SID in the // environment. // *Action: Make sure that the ORACLE_SID environment variable has been // properly set and exported. 02701, 00000, "osnoraenv: error translating oracle image name" // *Cause: ORACLE_HOME environment variable not set. // *Action: Make sure that the ORACLE_HOME environment variable has been // properly set and exported. 02702, 00000, "osnoraenv: error translating orapop image name" // *Cause: ORACLE_HOME environment variable not set. // *Action: Make sure that the ORACLE_HOME environment variable has been // properly set and exported. 02703, 00000, "osnpopipe: pipe creation failed" // *Cause: The pipe driver failed to create pipes for communications with // the orapop process. // *Action: You have probably exceeded the maximum number of open file // descriptors per user or the system file table is full. Note the // operating system error code and contact your system administrator. 02704, 00000, "osndopop: fork failed" // *Cause: The two-task driver could not fork orapop. // *Action: Verify that there are enough system resources to support another // process. The user or system process limit may have been exceeded, or // the amount of free memory or swap space may be temporarily insufficient. 02705, 00000, "osnpol: polling of communication channel failed" // *Cause: The pipe driver failed while polling the communications channel. // *Action: Contact your customer support representative. 02706, 00000, "osnshs: host name too long" // *Cause: The length of your host-string specified by the TWO_TASK // environment variable exceeds the ORACLE system-imposed limit. // *Action: Contact your customer support representative. 02707, 00000, "osnacx: cannot allocate context area" // *Cause: The invoked Unix two-task driver could not allocate heap space for // the context area. // *Action: Contact your customer support representative. 02708, 00000, "osnrntab: connect to host failed, unknown ORACLE_SID" // *Cause: The invoked Unix two-task driver failed to find an entry in // oratab for the sid you supplied. // *Action: First, check whether you have read access to oratab, and // see if the desired sid is there. Add an entry to oratab // for the desired sid, if necessary. 02709, 00000, "osnpop: pipe creation failed" // *Cause: The pipe driver failed to create pipes for two-task communications // with the oracle shadow process. // *Action: You have probably exceeded the maximum number of open file // descriptors per user or the system file table is full. Note the // operating system error code and contact your system administrator. 02710, 00000, "osnpop: fork failed" // *Cause: The pipe driver could not fork the oracle shadow process. // *Action: Verify that there are enough system resources to support another // process. The user or system process limit may have been exceeded, or // the amount of free memory or swap space may be temporarily insufficient. 02711, 00000, "osnpvalid: write to validation channel failed" // *Cause: The pipe driver failed to write to the orapop process. // *Action: Contact your customer support representative. 02712, 00000, "osnpop: malloc failed" // *Cause: The pipe driver failed to allocate enough heap space for its // context area buffers. // *Action: Contact your customer support representative. 02713, 00000, "osnprd: message receive failure" // *Cause: The pipe driver failed to read a message from the communications // channel. // *Action: Contact your customer support representative. 02714, 00000, "osnpwr: message send failure" // *Cause: The pipe driver failed to write a message to the communications // channel. // *Action: Contact your customer support representative. 02715, 00000, "osnpgetbrkmsg: message from host had incorrect message type" // *Cause: The pipe driver received a message having an unrecognizable // message type. // *Action: Contact your customer support representative. 02716, 00000, "osnpgetdatmsg: message from host had incorrect message type" // *Cause: The Pipe driver received a message having an unrecognizable // message type. // *Action: Contact your customer support representative. 02717, 00000, "osnpfs: incorrect number of bytes written" // *Cause: The Pipe driver sent a message that was apparently successful, // but the number of bytes transmitted did not match the number of // bytes furnished to the driver. // *Action: Contact your customer support representative. 02718, 00000, "osnprs: reset protocol error" // *Cause: The two-task driver could not reset the connection. // *Action: Contact your customer support representative. 02719, 00000, "osnfop: fork failed" // *Cause: The fast driver could not fork the oracle shadow process. // *Action: Verify that there are enough system resources to support another // process. The user or system process limit may have been exceeded, or // the amount of free memory or swap space may be temporarily insufficient. 02720, 00000, "osnfop: shmat failed" // *Cause: When the fast driver was invoked, processes failed to attach to the // shared memory buffer. You probably supplied an illegal shared memory // attach address, or the system ran out of data space to accomodate the buffer. // *Action: Try invoking the Fast driver later, or use the default attach // address. 02721, 00000, "osnseminit: cannot create semaphore set" // *Cause: The Fast driver failed to get a semaphore set. // *Action: The system-imposed limit on semaphores or semaphore identifiers // may have been exceeded. Read the returned operating system // error code and check with your system administrator. 02722, 00000, "osnpui: cannot send break message to orapop" // *Cause: The Pipe driver could not send a break message to orapop. // *Action: Contact your customer support representative. 02723, 00000, "osnpui: cannot send break signal" // *Cause: The Pipe driver could not send a break message to the ORACLE // shadow process. // *Action: Contact your customer support representative. 02724, 00000, "osnpbr: cannot send break message to orapop" // *Cause: The Pipe driver could not send a break message to orapop. // *Action: Contact your customer support representative. 02725, 00000, "osnpbr: cannot send break signal" // *Cause: The Pipe driver could not send a break message to the ORACLE // shadow process. // *Action: Kill system call failed. Check errno and contact customer support. 02726, 00000, "osnpop: access error on oracle executable" // *Cause: The Pipe driver could not access the oracle executable. // *Action: Check the permissions on the ORACLE executable and each // component of the ORACLE_HOME/bin path. 02727, 00000, "osnpop: access error on orapop executable" // *Cause: The Pipe driver could not access the orapop executable. // *Action: Check the permissions on the orapop executable and each // component of the ORACLE_HOME/bin path. 02728, 00000, "osnfop: access error on oracle executable" // *Cause: The Fast driver could not access the oracle executable. // *Action: Check the permissions on the ORACLE executable and each // component of the ORACLE_HOME/bin path. 02729, 00000, "osncon: driver not in osntab" // *Cause: The driver you have specified is not supported. // *Action: Check with your database administrator which drivers are supported. 02730, 00000, "osnrnf: cannot find user logon directory" // *Cause: The driver you have specified could not find your logon directory // while searching for your local .sqlnet file. // *Action: Set and export the HOME environment variable to identify your // home directory. Check with your system administrator to make sure // that your uid and home directory are correct in the /etc/passwd file. 02731, 00000, "osnrnf: malloc of buffer failed" // *Cause: The specified driver could not find enough heap space to malloc // a buffer. // *Action: Contact your customer support representative. 02732, 00000, "osnrnf: cannot find a matching database alias" // *Cause: Database alias specified was not identified in either // $HOME/.sqlnet or /etc/sqlnet. // *Action: Create the alias in a file called .sqlnet in your home directory // for personal use or ask your system administrator to create the // alias in /etc/sqlnet for system-wide use. 02733, 00000, "osnsnf: database string too long" // *Cause: While converting a database alias to a database ID, the resulting // database ID string exceeded the ORACLE system-imposed limit. // *Action: Contact your customer support representative. 02734, 00000, "osnftt: cannot reset shared memory permission" // *Cause: The Fast driver was unable to reset shared memory permissions. // *Action: Contact your customer support representative. 02735, 00000, "osnfpm: cannot create shared memory segment" // *Cause: The Fast driver failed to create a shared memory segment for // two-task communication. // *Action: Check whether the system-imposed limit on shared memory // identifiers has already been reached for your system. 02736, 00000, "osnfpm: illegal default shared memory address" // *Cause: The Fast driver failed to establish a default shared memory // address. // *Action: Contact your customer support representative. 02737, 00000, "osnpcl: cannot tell orapop to exit" // *Cause: The Pipe driver failed to send orapop the command to exit. // *Action: Contact your customer support representative. 02738, 00000, "osnpwrtbrkmsg: incorrect number of bytes written" // *Cause: The pipe driver apparently sent an imcomplete break message. // *Action: Contact your customer support representative. 02739, 00000, "osncon: host alias is too long" // *Cause: The alias used for a sqlnet host is longer than 161 characters. // *Action: Use a shorter alias. 02750, 00000, "osnfsmmap: cannot open shared memory file ?/dbs/ftt_.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. 03009, 00000, "Incompatible OCI function call" // *Cause: An incompatible OCI function call was issued for new functionality. // *Action: Do not use V7 OCI calls for this functionality. / / 3100-3199 two task interface errors / some of these can eventually convert to internal ercs / 03100, 00000, "communication area cannot be allocated; insufficient memory" // *Cause: // *Action: 03105, 00000, "internal protocol error" // *Cause: // *Action: 03106, 00000, "fatal two-task communication protocol error" // *Cause: // *Action: 03107, 00000, "oranet buffer underflow" // *Cause: // *Action: 03108, 00000, "oranet: ORACLE does not support this interface version" // *Cause: // *Action: 03109, 00000, "oranet buffer overflow" // *Cause: // *Action: 03110, 00000, "oranet: ORACLE does not support this SQL version" // *Cause: // *Action: 03111, 00000, "break received on communication channel" // *Cause: // *Action: 03112, 00000, "a server linked as single-task cannot use SQL*Net" // Cause: A statement containing a SQL*Net connect string was issued to the // single-task server. For example, a database link was used in a // SQL statement. // Action: Do not use SQL*Net connect strings in a single-task environment. 03113, 00000, "end-of-file on communication channel" // *Cause: The connection between Client and Server process was broken. // *Action: There was a communication error that requires further investigation. // First, check for network problems and review the SQL*Net setup. // Also, look in the alert.log file for any errors. Finally, test to // see whether the server process is dead and whether a trace file // was generated at failure time. 03114, 00000, "not connected to ORACLE" // *Cause: // *Action: 03115, 00000, "unsupported network datatype or representation" // *Cause: // *Action: 03116, 00000, "invalid buffer length passed to a conversion routine" // *Cause: // *Action: 03117, 00000, "two-task save area overflow" // *Cause: // *Action: 03118, 00000, "two-task coroutine has invalid state" // *Cause: // *Action: 03119, 00000, "two-task detected inconsistent datatype specification" // *Cause: There was both a datatype, and an anonymous datatype declaration // found. // *Action:Correct the specification. 03120, 00000, "two-task conversion routine: integer overflow" // *Cause: // *Action: 03121, 00000, "no interface driver connected - function not performed" // *Cause: // *Action: 03122, 00000, "attempt to close ORACLE-side window on user side" // *Cause: This is an internal error. // *Action: Contact your customer support representative. 03123, 00000, "operation would block" // *Cause: This is a status code that indicates that the operation // cannot complete now. // *Action: None; this is not an error. The operation should be retried // again for completion. 03124, 00000, "two-task internal error" // *Cause: Internal error. // *Action: Contact your customer support representative. 03125, 00000, "client-server protocol violation" // *Cause: The application received a bad escape sequence from the server and // may indicate a problem with the client application user code. // *Action: Contact your customer support representative. 03126, 00000, "network driver does not support non-blocking operations" // *Cause: A non-blocking operation was attempted and the network driver // does not support non-blocking operations. // *Action: Use default blocking operations or use a driver supporting // non-blocking operations. 03127, 00000, "no new operations allowed until the active operation ends" // *Cause: An attempt was made to execute a new operation before the active // non-blocking operation completed or a new operation was attempted // before all the pieces of a column were inserted or fetched. // *Action: Execute the new operation after the non-blocking operation // completes. If piecewise binds/defines were done, execute the new // operation after all the pieces have been inserted or fetched. 03128, 00000, "connection is in blocking mode" // *Cause: The OCI test for non-blocking mode on a connection indicates that // the connection is in blocking mode. // *Action: If non-blocking mode is required use appropriate OCI calls to // change the mode. 03129, 00000, "the next piece to be inserted is required" // *Cause: The application performed a piecewise bind on a column. // *Action: Provide the next piece of this bind variable. 03130, 00000, "the buffer for the next piece to be fetched is required" // *Cause: The application performed a piecewise define on the column. // *Action: Provide the next buffer for the next piece to be retrieved. 03131, 00000, "an invalid buffer was provided for the next piece" // *Cause: The application either provided the length of the buffer for the // next piece to be zero or provided a null pointer. // *Action: Verify if the buffer pointer for the next piece is null or if the // length is zero. 03132, 00000, "two-task default value overflow" // *Cause: The default value specified for a record field was too large. // *Action: Change the default value to fit the field size. 03133, 00000, "piggyback function error" // *Document: NO // *Cause: Piggyback function has returned an error. This is an internal // error. // *Action: 03134, 00000, "Connections to this server version are no longer supported." // *Cause: An attempt was made to connect to an Oracle server of older // version. // *Action: Please refer to documentation for more details. 03135, 00000, "connection lost contact" // *Cause: 1) Server unexpectedly terminated or was forced to terminate. // 2) Server timed out the connection. // *Action: 1) Check if the server session was terminated. // 2) Check if the timeout parameters are set properly in sqlnet.ora. 03136, 00000, "inbound connection timed out" // *Cause: Inbound connection was timed out by the server because // user authentication was not completed within the given time // specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value // *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. // 2) Configure SQL*NET with a proper inbound connect timeout value // if necessary. 03137, 00000, "TTC protocol internal error : [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]" // *Cause: TTC protocol internal error. // *Action: Contact Oracle Support Services. 03138, 00000, "Connection terminated due to security policy violation" // *Cause: Connection was terminated due to a security policy violation. // *Action: Contact the Database Administrator 03139, 00000, "This OCI call has been disabled by the DBA" // *Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled. // *Action: Contact the Database Administrator / / 3140 - 3159 Reserved for TTC/NET vector IO / 03140, 00000, "I/O operation in progress" // *Cause: The current I/O operation was not complete. The error is // typically returned from vectored and/or asynchronous I/O calls. // *Action: Perform the necessary operation to complete or abort the current I/O. 03141, 00000, "I/O request queue full" // *Cause: The I/O request queue was full and no more requests could be queued. // *Action: Perform the proper operations to complete part or all of the current // in-progress I/O requests. 03142, 00000, "Session ID: %ld Serial number: %ld" // *Cause: Connection was lost for the specified session and serial number. // This is either due to session being killed or network problems. // *Action: Reconnect and if error persists, contact Oracle Support Services. 03143, 00000, "Process ID: %s Thread ID: %s" // *Cause: Connection was lost for the specified process ID and thread ID. // This is either due to session being killed or network problems. // *Action: Reconnect and if error persists, contact Oracle Support Services. 03144, 00000, "Process ID: %s" // *Cause: Connection was lost for the specified process ID. // This is either due to session being killed or network problems. // *Action: Reconnect and if error persists, contact Oracle Support Services. 03145, 00000, "I/O streaming direction error" // *Cause: Attempted to PUT data when GET streaming was in progress or // attempted to GET data when PUT streaming was in progress. // *Action: Complete current stream read or write I/O before attempting // I/O in reverse direction. 03146, 00000, "Invalid buffer length for TTC field" // *Cause: A corrupt Two-Task Common (TTC) packet was received. // *Action: This is a internal protocol error. Contact Oracle Support Services. 03147, 00000, "Missing mandatory TTC field" // *Cause: A corrupt Two-Task Common (TTC) packet was received. // *Action: This is an internal protocol error. Contact Oracle Support // Services. 03149, 00000, "Invalid Oracle error code" // *Cause: An invalid Oracle error code was received by the server. // *Action: This is an internal protocol error. Contact Oracle Support // Services. 03160, 00000, "An invalid client operation was requested by the server" // *Cause: You are using an Oracle client application linked with // libraries with lower version than the current server version. // *Action: Upgrade client libraries to be same as // or higher than the server version. / 3170 to 3180 reserved for readable physical standby 03170, 00000, "deadlocked on readable physical standby (undo segment %s)" // *Cause: A new undo segment was added. A query can occasionally // deadlock when issued around the time an undo segment is added // and used immediately on the primary. // *Action: Retry the query. Avoid creating new undo segments when using // standby as a regular part of operation. 03171, 00000, "Recovery was terminated during query execution" // *Cause: Recovery was terminated. A query can ocassionally // deadlock when recovery is terminated because it needs a block // with changes that are made after the point at which recovery // was terminated. // *Action: Retry the query. Avoid cancelling recovery on standby. 03172, 00000, "STANDBY_MAX_DATA_DELAY of %s seconds exceeded" // *Cause: Standby recovery fell behind the STANDBY_MAX_DATA_DELAY // requirement. // *Action: Tune recovery and retry the query later, or switch to another // standby database within the data delay requirement. 03173, 00000, "Standby may not be synced with primary" // *Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the // standby was not synchronous or in a data-loss mode with regard // to the primary, or the standby recovery was terminated. // *Action: Make the standby synchronous and no-data-loss with regard // to the primary. Make the standby recovery active. 03174, 00000, "STANDBY_MAX_DATA_DELAY does not apply to SYS users" // *Cause: ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS // users. // *Action: Issue ALTER SESSION SET STANDBY_MAX_DATA_DELAY for non-SYS users. 03175, 00000, "parameter %s mismatch" // *Cause: The value of the %s parameter was not the same in all instances. // *Action: Check %s in all instances. 03176, 00000, "%s only works on an open physical standby database" // *Cause: The database was not an open physical standby database. // *Action: Issue the command on an open physical standby database. 03177, 00000, "enable read-only violation logging" // *Cause: // *Action: // *Comment: Used for testing only / / 3200 - 3289 Allocate Extent and other Space Management errors / 03200, 00000, "the segment type specification is invalid" // *Cause: segment type is not TABLE, INDEX, or CLUSTER // *Action: use a correct segment type / 03201, 00000, "the group number specification is invalid" // *Cause: the freelist group number was either negative or larger than the // the number of freelist groups in the segment // *Action: use a correct group number / 03202, 00000, "the scan limit specification is invalid" // *Cause: the scan limit did not have a positive integer value // the number of freelist groups in the segment // *Action: use a correct scan limit / 03203, 00000, "concurrent update activity makes space analysis impossible" // *Cause: high volume of user updates interfere with the space analysis // *Action: retry the command or lock the underlying objects / 03204, 00000, "the segment type specification should indicate partitioning" // *Cause: partition name is specified for the space analysis, but the object // type does not indicate parttitioning // *Action: specify PARTITION in the segment type, if the object is // partitioned, otherwise, omit the partition name / 03205, 00000, "partition name is required when partitioned type is specified" // *Cause: partition name is not specified for the space analysis, but the // object type indicates parttitioning // *Action: specify partition name, if the object is partitioned, otherwise, // specify a non-partitioned type / 03206, 00000, "maximum file size of (%s) blocks in AUTOEXTEND clause is out of range" // *Cause: The maximum file size for an autoextendable file has // exceeded the maximum number of blocks allowed. // *Action: Reduce the size and retry. / 03207, 00000, "subpartitioned type must be specified for composite object" // *Cause: partition type is specified for the space analysis, but the // object type indicates composite partitioning // *Action: specify subpartition name and subpartition type / 03208, 00000, "partitioned type must be specified for a non-composite object" // *Cause: subpartition type is specified for the space analysis, but the // object type indicates non-composite partitioning // *Action: specify partition name and partition type / 03209, 00000, "DBMS_ADMIN_PACKAGE invalid file/block specification" // *Cause: The value of file number or block number is outside of limits or // inconsistent // *Action: Fix the file number/block number value / 03210, 00000, "DBMS_ADMIN_PACKAGE invalid option specification" // *Cause: The value of one of the option parameters is incorrect // *Action: Fix the option value / 03211, 00000, "The segment does not exist or is not in a valid state" // *Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation // does not exist or is not in a state appropriate for this operation // *Action: Fix the segment specification, or put the segment in the // appropriate state. / 03212, 00000, "Temporary Segment cannot be created in locally-managed tablespace" // *Cause: Attempt to create a temporary segment for sort/hash/lobs in // in permanent tablespace of kind locally-managed // *Action: Alter temporary tablespace of user to a temporary tablespace // or a dictionary-managed permanent tablespace / 03213, 00000, "Invalid Lob Segment Name for DBMS_SPACE package" // *Cause: The Lob Segment specified in the DBMS_SPACE operation does not // exist. // *Action: Fix the Segment Specification / 03214, 00000, "File Size specified is smaller than minimum required" // *Cause: File Size specified for add/resize datafile/tempfile does not // allow for the minimum required of one allocation unit. // *Action: Increase the specification for file size / 03215, 00000, "File Size specified for resize is too small " // *Cause: File Size specified for resize datafile/tempfile causes // bitmap control structures to overlap // *Action: Increase the specification for file size / 03216, 00000, "Tablespace/Segment Verification cannot proceed" // *Cause: Corruptions detected during verification whch cannot be dealt with // *Action: Do manual verification / 03217, 00000, "invalid option for alter of TEMPORARY TABLESPACE" // *Cause: invalid option for alter of temporary tablespace was specified // *Action: Specify one of the valid options: ADD TEMPFILE, // TEMPFILE ONLINE, TEMPFILE OFFLINE / 03218, 00000, "invalid option for CREATE/ALTER TABLESPACE" // *Cause: invalid option for create/alter tablespace of type locally-managed // *Action: Specify one of the valid options. / 03219, 00000, "Tablespace '%s' is dictionary-managed, offline or temporary" // *Cause: Operation which is only applicable to permanent, online, // locally-managed tablespaces is specified for a tablespace which // is either dictionary-managed, offline or temporary // *Action: Reissue operation for a different tablespace, mount the // tablespace or do not issue it at all, since it does not apply // for the given tablespace / 03220, 00000, "DBMS_ADMIN_PACKAGE required parameter is NULL or missing" // *Cause: Some of the procedures was called with missing or NULL parameters // *Action: Specify the missing parameter / 03221, 00000, "Temporary tablespaces and temporary segments must have standard block size" // *Cause: An attempt was made to do one of the following : // (1) create a temporary tablespace with a non-standard block // size or, // (2) alter an existing permanent tablespace of non-standard // block size to a temporary tablespace or, // (3) issue a DDL statement that would result in the creation // of a temporary segment in a tablespace of non-standard // block size. // *Action: (1) If creating a temporary tablespace, do not specify a block // size different from the standard block size. // (2) If altering an existing permanent tablespace to a // temporary tablespace, ensure that it is of standard block size. // (3) Ensure that the user's temporary tablespace is a // tablespace having the standard block size. / 03222, 00000, "average row size and row count must be greater than zero" // *Cause: Either a bad value passed to dbms_space.create_table_cost() // or explain plan did not pass through size information. // *Action: Check the row size parameter in dbms_space.create_table_cost(). // For explain plan, make sure statistics have been computed // for all source tables in the CREATE TABLE AS SELECT statement. / 03223, 00000, "Bitmap index block addressable limitation reached" // *Cause: The limitation of addressability of BMIB (Bitmap Index Block) was // reached for the current blocksize. // *Action: If the segment size has grown greater than addressability of BMIB // (Bitmap Index Block), do the following: // (1) Partition the table. // (2) Move the segment to a tablespace having bigger blocksize. / 03230, 00000, "segment only contains %s blocks of unused space above high water mark" // *Cause: Attempt to preserve too many blocks. // *Action: reduce the KEEP amount. / 03231, 00000, "the INITIAL extent may not be deallocated" // *Cause: Attempt to deallocate space from the segment which was truncated // prior to the 7.3 release. // *Action: increase the KEEP amount, or truncate the segment, and reissue // the command. / 03233, 00000, "unable to extend table %s.%s subpartition %s by %s in tablespace %s" // *Cause: Failed to allocate an extent for table subpartition segment // in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 03234, 00000, "unable to extend index %s.%s subpartition %s by %s in tablespace %s" // *Cause: Failed to allocate an extent for index subpartition // segment in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 03235, 00000, "max # extents (%s) reached in table %s.%s subpartition %s" // *Cause: A table subpartition tried to extend past maxextents // *Action: If maxextents is less than the system maximum, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params 03236, 00000, "max # extents (%s) reached in index %s.%s subpartition %s" // *Cause: An index subpartition tried to extend past maxextents // *Action: If maxextents is less than the system max, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params. 03237, 00000, "Initial Extent of specified size cannot be allocated in tablespace (%s)" // *Cause: Too large a size for an initial extent due to freelist // group specification // *Action: Reduce number of freelist groups specified for segment 03238, 00000, "unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s" // *Cause: An attempt was made to allocate an extent for LOB subpartition // segment in tablespace, but the extent could not be allocated // because there is not enough space in the tablespace indicated. // *Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or // more files to the tablespace indicated. 03239, 00000, "maxextents (%s) reached in LOB segment %s.%s subpartition %s" // *Cause: A LOB subpartition segment tried to extend past maxextents. // *Action: If maxextents is less than the system maximum, raise it. // Otherwise, recreate the subpartition with larger INITIAL, NEXT, // or PCTINCREASE parameters. / / Errors 3240 - 3250 reserved for tablespace migration and bitmaps relocation / 03240, 00000, "User's temporary tablespace same as tablespace being migrated" // *Cause: Users default temporary tablespace must be different from the // tablespace being migrated. // *Action: alter users default temporary tablespace to be different. 03241, 00000, "Invalid unit size" // *Cause: User specified an invalid unit size for the tablespace // *Action: Specify the correct unit size. To estimate unit size please // refer to Oracle Server Administrator's Guide. 03242, 00000, "Tablespace migration retried 500 times" // *Cause: For migration to complete, temporary segments should not be present // in the tablespace at the time of migration. // *Action: Avoid migrating the tablespace when there is heavy temporary // segment creation going on as with object drops. 03243, 00000, "destination dba overlaps with existing control information" // *Cause: Cannot overlap control information during relocation // *Action: Please chose another destination address 03244, 00000, "No free space found to place the control information" // *Cause: During migration of tablespace found no place to put the control // information. If during bitmaps relocation, found no space at the // specified destination. // *Action: If during migration, add more space to the tablespace and retry // migration. If during bitmaps relocation, specify a destination // address where there is enough free space. 03245, 00000, "Tablespace has to be dictionary managed, online and permanent to be able to migrate" // *Cause: Tablespace was not dictionary managed or online or permanent. // *Action: Make sure the tablespace is online, permanent and dictionary managed 03246, 00000, "Invalid block number specified" // *Cause: Control information cannot be placed at the specified dba either // because the block number specified is beyond the file end or // the file is not large enough to accomodate the control information // at that location // *Action: specify a correct block number 03247, 00000, "Invalid block number specified" // *Cause: Relocation of bitmaps to the said destination will make // the tablespace self descriptive // *Action: Choose another destination dba. 03248, 00000, "Too much of segment creation activity during migration" // *Cause: Temporary segments were attempted to be created during migration // *Action: The error is signalled after retrying migration for 500 times. // Run migration when there is less of segment creation activity is // going on. 03249, 00000, "Uniform size for auto segment space managed tablespace should have atleast %s blocks" // *Cause: For the given blocksize, uniform size specified is insufficient // *Action: Specify larger extent size and retry 03250, 00000, "Cannot mark this segment corrupt" // *Cause: This segment cannot be marked corrupt because it contains // data dictionary objects // *Action: Check the segment information and reissue the command. 03251, 00000, "Cannot issue this command on SYSTEM tablespace " // *Cause: It is not permitted to migrate SYSTEM tablespace from locally // managed format to dictionary managed format or relocate bitmaps. // *Action: Check the tablespace name and procedure name 03252, 00000, "initial extent size not enough for LOB segment" // *Cause: Fatblock size of LOB segment is too big to fit into the initial // extent. // *Action: Specify a smaller fatblock size or create the LOB segment in // other tablespaces with bigger initial extent size. 03254, 00000, "unable to execute the sql in read only database" // *Cause: Unable to create a consistent snapshot of the object in a read // only database. Transaction recovery must be performed before opening the // database read only. // *Action: Open the database read write, allow dead transaction recovery // to complete and then open the database read only. 03261, 00000, "the tablespace %s has only one file" // *Cause: Dropping file from ts which has a single file // extent. // *Action: Cannot make a tablespace fileless 03262, 00000, "the file is non-empty" // *Cause: Trying to drop a non-empty datafile // *Action: Cannot drop a non empty datafile 03263, 00000, "cannot drop the first file of tablespace %s" // *Cause: Trying to drop the first datafile with which ts is created // *Action: Cannot drop the first datafile with which ts is created 03264, 00000, "cannot drop offline datafile of locally managed tablespace" // *Cause: Trying to drop offline datafile in lmts // *Action: Try to drop file afetr making it online 03274, 00000, "both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified" // *Cause: The DEALLOCATE option and the ALLOCATE option are specified in // the same command. // *Action: Choose one of the options or issue two separate commands. 03275, 00000, "duplicate DEALLOCATE option specification" // *Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX // is specified more than once. // *Action: Specify the option at most once. 03276, 00000, "duplicate ALLOCATE EXTENT option specification" // MERGE: 2376 RENUMBERED TO 3276 // *Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX // is specified more than once. // *Action: Specify the option at most once. 03277, 00000, "invalid SIZE specified" // MERGE: 2377 RENUMBERED TO 3277 // *Cause: The specified value must be an integer. // *Action: Choose an appropriate integer value. 03278, 00000, "duplicate ALLOCATE EXTENT option specification" // MERGE: 2378 RENUMBERED TO 3278 // *Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more // than once. // *Action: Specify each option at most once. 03279, 00000, "invalid INSTANCE specified" // MERGE: 2379 RENUMBERED TO 3279 // *Cause: The specified value is not recognized as a valid instance name. // *Action: Use a valid name. 03280, 00000, "invalid DATAFILE filename specified" // MERGE: 2380 RENUMBERED TO 3280 // *Cause: A character string literal is expected, but not found. // *Action: Specify filenames using character string literals. 03281, 00000, "invalid ALLOCATE EXTENT option" // MERGE: 2381 RENUMBERED TO 3281 // *Cause: An option other than DATAFILE, SIZE or INSTANCE was specified. // *Action: Remove invalid option and retry the command. 03282, 00000, "missing ALLOCATE EXTENT option" // MERGE: 2382 RENUMBERED TO 3282 // *Cause: No ALLOCATE EXTENT options were specified. // *Action: Specified one or more of the following options: // DATAFILE, SIZE or INSTANCE. 03283, 00000, "specified datafile %s does not exist" // MERGE: 2383 RENUMBERED TO 3283 // *Cause: The datafile does not exist // *Action: Retry the option with the correct datafile 03284, 00000, "datafile or tempfile %s is not a member of tablespace %s" // MERGE: 2384 RENUMBERED TO 3284 // *Cause: The specified datafile or tempfile did not belong to the // tablespace that the object resides in. // *Action: Retry the option with the correct datafile or tempfile. 03286, 00000, "ALLOCATE EXTENT not valid for HASH CLUSTERS" // *Cause: The cluster is a hash cluster, and can not use the // allcoate extent option. // Action: 03287, 00000, "invalid FREELIST GROUP specified" // *Cause: The specified FREELIST GROUP number is invalid // *Action: Choose a number between 1 and # freelist groups for this object 03288, 00000, "both FREELIST GROUP and INSTANCE parameters may not be specified" // *Cause: Both FREELIST GROUP and INSTANCE were specified in clause // *Action: Remove one of the two parameters 03289, 00000, "partition name and segment type do not match" // *Cause: Partition name and segment type specified for space analysis do // not match // *Action: Specify type PARTITION if the object is partitioned, specify // SUBPARTITION if the object is composite / / 3290 - 3295 Truncate Parse and Execution Errors / 03290, 00000, "Invalid truncate command - missing CLUSTER or TABLE keyword" // *Cause: Invalid object specification given. // *Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE 03291, 00000, "Invalid truncate option - missing STORAGE keyword" // *Cause: Expected STORAGE keyword // *Action: Either specify DROP STORAGE or REUSE STORAGE 03292, 00000, "Table to be truncated is part of a cluster" // *Cause: The table being truncated is a member of a cluster. // *Action: Either use TRUNCATE CLUSTER or DROP TABLE 03293, 00000, "Cluster to be truncated is a HASH CLUSTER" // *Cause: Only INDEX CLUSTERS can be truncated. // *Action: Drop and recreate the HASH CLUSTER instead of using truncate. / / 3296 - 3299 Reserved for Resizeable Datafiles / 03296, 00000, "cannot resize datafile - file %s not found" // *Cause: The specified datafile is not available for resizing. // *Action: Ensure that the datafile name is valid, and if so, ensure the // file is accessible. 03297, 00000, "file contains used data beyond requested RESIZE value" // *Cause: Some portion of the file in the region to be trimmed is // currently in use by a database object // *Action: Drop or move segments containing extents in this region prior to // resizing the file, or choose a resize value such that only free // space is in the trimmed. 03298, 00000, "cannot shrink datafile - file %s is under hot backup" // *Cause: Attempt to shrink a datafile while it is under hot backup. // This is not allowed. // *Action: Retry shrinking the file after the hot backup completes. 03299, 00000, "cannot create dictionary table %s" // *Cause: A dictionary table is created upon the first execution of the // command 'alter database datafile autoextend on' for a database. // This operation did not succeed. The most probable cause for this // is insufficient space in the system tablespace. // *Action: See action for next error message in error stack. / / 3300 - 3499 Reserved for Meiko / / 3500 - 3699 Reserved for Native Macintosh OS-specific errors / / 3700 - 3999 Reserved for DG AOS/VS specific errors / / 4000-4099 invalid parameter errors / 04000, 00000, "the sum of PCTUSED and PCTFREE cannot exceed 100" // *Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100 // *Action: create the table/cluster specifying values whose sum is <= 100 04001, 00000, "sequence parameter %s must be an integer" // *Cause: %s (a sequence parameter) specified was not an integer // *Action: create the sequence, giving the specified parameter an integer value 04002, 00000, "INCREMENT must be a non-zero integer" // *Cause: a sequence increment was specified to be zero // *Action: specify the increment to be a non-zero value 04003, 00000, "sequence parameter %s exceeds maximum size allowed (%s digits)" // *Cause: %s (a sequencer parameter) had too many digits // *Action: specify the parameter with the allowed number of digits 04004, 00000, "MINVALUE must be less than MAXVALUE" // *Cause: MINVALUE was specified to be greater than or equal to MAXVALUE // *Action: specify a MINVALUE that is less than MAXVALUE 04005, 00000, "INCREMENT must be less than MAXVALUE minus MINVALUE" // *Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE // *Action: specify an INCREMENT that is < MAXVALUE-MINVALUE 04006, 00000, "START WITH cannot be less than MINVALUE" // *Cause: the given starting value is less than MINVALUE // *Action: make sure that the starting value is >= MINVALUE 04007, 00000, "MINVALUE cannot be made to exceed the current value" // *Cause: the given MINVALUE would be greater than the current value // *Action: always make sure that MINVALUE is <= the current value 04008, 00000, "START WITH cannot be more than MAXVALUE" // *Cause: the starting value would be larger than MAXVALUE // *Action: make sure that the starting value is less than MAXVALUE 04009, 00000, "MAXVALUE cannot be made to be less than the current value" // *Cause: the current value exceeds the given MAXVALUE // *Action: make sure that the new MAXVALUE is larger than the current value 04010, 00000, "the number of values to CACHE must be greater than 1" // *Cause: the value in the CACHE clause was one // *Action: specify NOCACHE, or a value larger than one 04011, 00000, "sequence %s must range between %s and %s" // *Cause: the value specified for one of the sequence parameters exceeds limits // *Action: specify parameter within these limits 04012, 00000, "object is not a sequence" // *Cause: the object specified cannot have sequence ddl's performed on it // *Action: re-enter the statement being careful with the spelling of the name 04013, 00000, "number to CACHE must be less than one cycle" // *Cause: number to CACHE given is larger than values in a cycle // *Action: enlarge the cycle, or cache fewer values 04014, 00000, "descending sequences that CYCLE must specify MINVALUE" // *Cause: sequences that cycle must have their wrap-wrap specified // *Action: re-create the sequence, specifying its wrap-value 04015, 00000, "ascending sequences that CYCLE must specify MAXVALUE" // *Cause: sequences that cycle must have their wrap-wrap specified // *Action: re-create the sequence, specifying its wrap-value 04016, 00000, "sequence %s no longer exists" // *Cause: sequence was dropped while processing its next value. // *Action: re-create the sequence 04017, 00000, "invalid value %s (length = %s) for parameter max_dump_file_size" // *Cause: neither did the string supplied for max_dump_file_size parameter // match the "UNLIMITED" string value nor did it represent a base 10 // integer. // *Action: reassign a proper value to this parameter. / / 4020-4029 Reserved for Library Cache errors / 04020, 00000, "deadlock detected while trying to lock object %s%s%s%s%s" // *Cause: While trying to lock a library object, a deadlock is detected. // *Action: Retry the operation later. 04021, 00000, "timeout occurred while waiting to lock object %s%s%s%s%s" // *Cause: While waiting to lock a library object, a timeout occurred. // *Action: Retry the operation later. 04022, 00000, "nowait requested, but had to wait to lock dictionary object" // *Cause: Had to wait to lock a library object during a nowait request. // *Action: Retry the operation later. 04023, 00000, "Object %s%s%s%s%s could not be validated or authorized" // *Cause: A number of attempts were made to validate or authorize an // object but failed. // *Action: Please report this error to Oracle Support Services. 04024, 00000, "self-deadlock detected while trying to mutex pin cursor %s" // *Cause: While trying to mutex pin a cursor, a self-deadlock is detected. // *Action: Retry the operation later. 04025, 00000, "maximum allowed library object lock allocated for %s%s%s%s%s" // *Cause: Too many active locks for the object has been allocated. This error // can be a result of too many cursors kept open per session. // *Action: Close cursors, reduce session_cached_cursors value. 04027, 00000, "self-deadlock during automatic validation for object %s.%s" // *Cause: An attempt was made to validate an invalidated object but it failed // because of a self-deadlock. // *Action: Identify the root cause of the self-deadlock and take corrective // action, e.g. compile the invalidated object separately. 04028, 00000, "cannot generate diana for object %s%s%s%s%s" // *Cause: Cannot generate diana for an object because of lock conflict. // *Action: Please report this error to your support representative. 04029, 00000, "error ORA-%s occurred when querying %s%s%s" // *Cause: The table or view being queried might be missing. The error // number indicates the error. // *Action: Fix the error. / / 4030-4039 Reserved for Memory Manager errors / 04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)" // *Cause: Operating system process private memory was exhausted. // *Action: 04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")" // *Cause: More shared memory is needed than was allocated in the shared // pool or Streams pool. // *Action: If the shared pool is out of memory, either use the // DBMS_SHARED_POOL package to pin large packages, // reduce your use of shared memory, or increase the amount of // available shared memory by increasing the value of the // initialization parameters SHARED_POOL_RESERVED_SIZE and // SHARED_POOL_SIZE. // If the large pool is out of memory, increase the initialization // parameter LARGE_POOL_SIZE. // If the error is issued from an Oracle Streams or XStream process, // increase the initialization parameter STREAMS_POOL_SIZE or increase // the capture or apply parameter MAX_SGA_SIZE. 04032, 00000, "pga_aggregate_target must be set before switching to auto mode" // *Cause: attempt to set workarea_size_policy to AUTO while // pga_aggregate_target is not specified // *Action: before setting workarea_size_policy, set pga_aggregate_target // to a value representing the total private memory available to // the instance. This total is generally the total physical memory // available in the system minus what is needed for the SGA minus // what is needed for the operating system (e.g. 500MB) 04033, 00000, "Insufficient memory to grow pool" // *Cause: The system had insufficient memory to grow the pool to the // specified size. // *Action: Specify a smaller value to grow the pool. 04034, 00000, "unable to shrink pool to specified size" // *Cause: The pool could not shrink to the specified size as it could not // free memory. // *Action: Specify a larger value to which to shrink the pool to. 04035, 00000, "unable to allocate %s bytes of shared memory in shared object cache \"%s\" of size \"%s\"" // *Cause: More shared memory is needed than was allocated in the shared // object cache. // *Action: / / 4040-4059 Reserved for Stored Procedure errors / 04041, 00000, "package specification must be created first before creating package body" // *Cause: Attempt to create a package body before creating its package // specification. // *Action: Create the package specification first before creating the // package body. 04042, 00000, "procedure, function, package, or package body does not exist" // *Cause: Attempt to access a procedure, function, package, or package body // that does not exist. // *Action: Make sure the name is correct. 04043, 00000, "object %s does not exist" // *Cause: An object name was specified that was not recognized by the system. // There are several possible causes: // - An invalid name for a table, view, sequence, procedure, function, // package, or package body was entered. Since the system could not // recognize the invalid name, it responded with the message that the // named object does not exist. // - An attempt was made to rename an index or a cluster, or some // other object that cannot be renamed. // *Action: Check the spelling of the named object and rerun the code. (Valid // names of tables, views, functions, etc. can be listed by querying // the data dictionary.) 04044, 00000, "procedure, function, package, or type is not allowed here" // *Cause: A procedure, function, or package was specified in an // inappropriate place in a statement. // *Action: Make sure the name is correct or remove it. 04045, 00000, "errors during recompilation/revalidation of %s.%s" // *Cause: This message indicates the object to which the following // errors apply. The errors occurred during implicit // recompilation/revalidation of the object. // *Action: Check the following errors for more information, and // make the necessary corrections to the object. 04046, 00000, "results of compilation are too large to support" // *Cause: Attempt to compile and store a large stored procedure that results // in compilation data that is too large for the system to support // or store. // *Action: Reduce the size of the store procedure by splitting it into // smaller stored procedures. 04047, 00000, "object specified is incompatible with the flag specified" // *Cause: The object type implied by the flag does not match the type // of object specified. // *Action: Specify the correct object, or use the appropriate flag 04050, 00000, "invalid or missing procedure, function, or package name" // *Cause: The required procedure, function, or package name is invalid // or missing. // *Action: Specify a valid name. 04051, 00000, "user %s cannot use database link %s.%s" // *Cause: During forwarding of a remote object access, an attempt was // made to use a non-existent database link or one owned by // a user other than the logon user or PUBLIC. // *Action: Change your database link structure so that all indirect remote // accesses are done from the same userid that originates the // request. 04052, 00000, "error occurred when looking up remote object %s%s%s%s%s" // *Cause: An error occurred when trying to look up a remote object. // *Action: Fix the error. Make sure the remote database system has run // CATRPC.SQL to create necessary views used for querying or looking up // objects stored in the database. 04053, 00000, "error occurred when validating remote object %s%s%s%s%s" // *Cause: An error occurred when trying to validate a remote object. // *Action: Fix the error. Make sure the remote database system has run // CATRPC.SQL to create necessary views used for querying or looking up // objects stored in the database. 04054, 00000, "database link %s does not exist" // *Cause: During compilation of a PL/SQL block, an attempt was made to use // a non-existent database link. // *Action: Either use a different database link or create the database link. 04055, 00000, "Aborted: \"%s\" formed a non-REF mutually-dependent cycle with \"%s\"." // *Cause: This compilation was aborted because the library unit that was // compiled would have formed a non-REF mutually-dependent cycle with // some other library units. This happens when an attempt is made to // compile types that have attributes of other types that may // participate in a cycle with this type. // Example: // create type t1; // create type t2 (a t1); // create type t1 (a t2); // *Action: Break the cycle (possibly by adding a REF or by using another // type). / / 4060-4069 Reserved for Stored Procedure Execution errors / 04060, 00000, "insufficient privileges to execute %s" // *Cause: Attempt to execute a stored procedure without // sufficient privileges. // *Action: Get necessary privileges. 04061, 00000, "existing state of %s has been invalidated" // *Cause: Attempt to resume the execution of a stored procedure using the // existing state which has become invalid or inconsistent // with the stored procedure because the procedure has been altered // or dropped. // *Action: Try again; this error should have caused the existing state of // all packages to be re-initialized. 04062, 00000, "%s of %s has been changed" // *Cause: Attempt to execute a stored procedure to serve // an RPC stub which specifies a timestamp or signature that is // different from the current timestamp/signature of the procedure. // *Action: Recompile the caller in order to pick up the new timestamp. 04063, 00000, "%s has errors" // *Cause: Attempt to execute a stored procedure or use a view that has // errors. For stored procedures, the problem could be syntax errors // or references to other, non-existent procedures. For views, // the problem could be a reference in the view's defining query to // a non-existent table. // Can also be a table which has references to non-existent or // inaccessible types. // *Action: Fix the errors and/or create referenced objects as necessary. 04064, 00000, "not executed, invalidated %s" // *Cause: Attempt to execute a stored procedure that has // been invalidated. // *Action: Recompile it. 04065, 00000, "not executed, altered or dropped %s" // *Cause: Attempt to execute a stored procedure that has // been altered or dropped thus making it not callable from the // calling procedure. // *Action: Recompile its dependents. 04066, 00000, "non-executable object, %s" // *Cause: Attempt to execute a non-procedure. // *Action: Make sure that a correct name is given. 04067, 00000, "not executed, %s does not exist" // *Cause: Attempt to execute a non-existent stored procedure. // *Action: Make sure that a correct name is given. 04068, 00000, "existing state of packages%s%s%s has been discarded" // *Cause: One of errors 4060 - 4067 when attempt to execute a stored // procedure. // *Action: Try again after proper re-initialization of any application's // state. 04069, 00000, "cannot drop or replace a library with table dependents" // *Cause: An attempt was made to drop or replace a library that has // dependents. There could be a table which depends on type which // depends on the library being dropped. // *Action: Drop all table(s) depending on the type, then retry. / / 4070-4099 Reserved for Trigger errors / 04070, 00000, "invalid trigger name" // *Cause: An invalid trigger name was specified. // *Action: Verify that trigger name is not a reserved keyword. 04071, 00000, "missing BEFORE, AFTER or INSTEAD OF keyword" // *Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause. // *Action: Specify either BEFORE, AFTER or INSTEAD OF. 04072, 00000, "invalid trigger type" // *Cause: An invalid trigger type was given. // *Action: Specify either INSERT, UPDATE or DELETE. 04073, 00000, "column list not valid for this trigger type" // *Cause: A column list was specified for a non-update trigger type. // *Action: Remove the column list. 04074, 00000, "invalid REFERENCING name" // *Cause: An invalid name was given in the referencing clause. // *Action: Verify the referencing name is not a reserved word. 04075, 00000, "invalid trigger action" // *Cause: An statement was given for the trigger action. // *Action: Re-specify the trigger action. 04076, 00000, "invalid NEW or OLD specification" // *Cause: An invalid NEW or OLD specification was given for a column. // *Action: Re-specify the column using the correct NEW or OLD specification. 04077, 00000, "WHEN clause cannot be used with table level triggers" // *Cause: The when clause can only be specified for row level triggers. // *Action: Remove the when clause or specify for each row. 04078, 00000, "OLD and NEW values cannot be identical" // *Cause: The referencing clause specifies identical values for NEW and OLD. // *Action: Re-specify either the OLD or NEW referencing value. 04079, 00000, "invalid trigger specification" // *Cause: The create TRIGGER statement is invalid. // *Action: Check the statement for correct syntax. 04080, 00000, "trigger '%s' does not exist" // *Cause: The TRIGGER name is invalid. // *Action: Check the trigger name. 04081, 00000, "trigger '%s' already exists" // *Cause: The TRIGGER name or type already exists. // *Action: Use a different trigger name or drop the trigger which is of the // same name. 04082, 00000, "NEW or OLD references not allowed in table level triggers" // *Cause: The trigger is accessing "new" or "old" values in a table trigger. // *Action: Remove any new or old references. 04083, 00000, "invalid trigger variable '%*.s'" // *Cause: The variable referenced in the trigger body is invalid. // *Action: See the manual for valid trigger variable types. 04084, 00000, "cannot change NEW values for this trigger type" // *Cause: New trigger variables can only be changed in before row // insert or update triggers. // *Action: Change the trigger type or remove the variable reference. 04085, 00000, "cannot change the value of an OLD reference variable" // *Cause: Old values can only be read and not changed. // *Action: Do not attempt to change an old variable. 04086, 00000, "trigger description too long, move comments into triggering code" // *Cause: The trigger description is limited to 2000 characters (for // dictionary storage reasons). The description does not include // the text of the "when" clause or the text of the pl/sql code // executed for the trigger. // *Action: If the trigger description contains a large comment, move that // comment into the pl/sql code for the trigger. 04087, 00000, "cannot change the value of ROWID reference variable" // *Cause: Rowid's can only be read and not changed. // *Action: Do not attempt to change an rowid value. 04088, 00000, "error during execution of trigger '%s.%s'" // *Cause: A runtime error occurred during execution of a trigger. // *Action: Check the triggers which were involved in the operation. 04089, 00000, "cannot create triggers on objects owned by SYS" // *Cause: An attempt was made to create a trigger on an object owned by SYS. // *Action: Do not create triggers on objects owned by SYS. 04090, 00000, "'%s' specifies same table, event and trigger time as '%s'" // *Cause: Trigger is of duplicate event and trigger time. // *Action: Combine the triggering information into one trigger which is // fired at the given time. 04091, 00000, "table %s.%s is mutating, trigger/function may not see it" // *Cause: A trigger (or a user defined plsql function that is referenced in // this statement) attempted to look at (or modify) a table that was // in the middle of being modified by the statement which fired it. // *Action: Rewrite the trigger (or function) so it does not read that table. 04092, 00000, "cannot %s in a trigger" // *Cause: A trigger attempted to commit or rollback. // *Action: Rewrite the trigger so it does not commit or rollback. 04093, 00000, "references to columns of type LONG are not allowed in triggers" // *Cause: A trigger attempted to reference a long column in the triggering // table. // *Action: Do not reference the long column. 04094, 00000, "table %s.%s is constraining, trigger may not modify it" // *Cause: A trigger attempted to modify a table that was constraining for // some referential constraint of a parent SQL statement. 04095, 00000, "trigger '%s' already exists on another table, cannot replace it" // *Cause: Cannot replace a trigger which already exists on a different table // than the one being replaced. // *Action: Drop the trigger with the same name and re-create it. 04096, 00000, "trigger '%s' has a WHEN clause which is too large, limit 2K" // *Cause: A trigger's 'when' clause is limited to 2K for dictionary storage // reasons. The trigger being created exceeded that size. // *Action: Use a smaller 'when' clause. Note, the trigger body could be used // to perform the same limiting action as the 'when' clause. 04097, 00000, "DDL conflict while trying to drop or alter a trigger" // *Cause: An attempt was made to concurrently perform two DDL operations on // a trigger or trigger table. // *Action: Investigate the new state of the trigger and retry the DDL // operation, if still appropriate. 04098, 00000, "trigger '%s.%s' is invalid and failed re-validation" // *Cause: A trigger was attempted to be retrieved for execution and was // found to be invalid. This also means that compilation/authorization // failed for the trigger. // *Action: Options are to resolve the compilation/authorization errors, // disable the trigger, or drop the trigger. 04099, 00000, "trigger '%s' is valid but not stored in compiled form" // *Cause: A trigger was attempted to be retrieved for execution and was // found to be valid, but not stored. This may mean the an // upgrade was done improperly from a non-stored trigger release. // *Action: Alter compile the trigger to create the trigger in stored form. // Also, you may want to review that a proper upgrade was done. / / MODIFIED / mmpandey 05/20/10 - 9714832: modify ADRCI Note detail, per new requirement / mmpandey 05/14/10 - 9714832: modify ORA-07445 Cause/Action text / sagrawal 11/16/09 - bug 9096821: change action for message 6548 / jmuller 05/05/08 - XbranchMerge jmuller_bug-6805832 from st_rdbms_10.2 / jmuller 02/08/08 - Fix bug 6805832: plsql_max_stack_size / dalpern 03/25/08 - 6907300: dbms_utility.name_resolve context 0 / mvemulap 01/10/07 - bug 5727887 fix / desinha 08/30/06 - edit 6570 to add purge / jmuller 05/10/06 - Fix bug 5206360: document ORA-6501/6502 / ssubrama 11/07/05 - bug 4292100 remove 6596 as its no longer in use / jmuller 04/07/05 - Fix bug 4236303: disallow deep copy of LOBs during / RPC / jmuller 03/16/05 - Fix bug 4185606: flag ref cursor parameters in / forwarded RPC case / jmuller 02/28/05 - Fix bug 4200773: handle NULL results in sped-up / STANDARD function calls more cleanly / swhitman 12/22/04 - 3841541:patched Tru64 kernels get proc starttime / wojeil 11/09/04 - add 7405 / jmuller 07/02/04 - Fix bug 3711648: parameterize ORA-6500 / jmuller 12/09/03 - Fix bug 1284461: name missing unit in / ORA-6508/BAD_DYN_LINK / avaliani 11/14/03 - add 07458-07460 (remove 07457 in 10gr2) / sdizdar 10/31/02 - add 7346 / avaliani 06/19/02 - add 07457 / mjaeger 06/10/02 - bug 2238718: chg 7247 from sfrfb to Veritas / shbose 04/29/02 - 2255071: change message for ora-6534 / ssubrama 04/09/02 - bug 2200057 add 6579 / hbergh 11/05/01 - 1980225: trace file cannot be symlink / kmuthukk 07/03/01 - 1720409: rope of debugger/profiler with plsql ncomp / mvemulap 03/08/01 - bug 1554027 fix / mxyang 02/28/01 - update 6514 / kumamage 02/15/01 - / kumamage 02/08/01 - add message for sftdel / arhee 10/26/00 - add new error message for resmgr / mxyang 08/11/00 - 6592: CASE not found / mvemulap 07/19/00 - native compiler messages / asethi 06/23/00 - 6540: pipelined execution of PL/SQL functions / arhee 06/19/00 - add mesg for exceeded max est exec time / arhee 06/07/00 - fix error mesg 7454 / arhee 03/28/00 - add error msg 7454 / hbergh 03/28/00 - 993307: merge Compaq Tru64 message / nle 07/22/99 - swap error message number / nle 06/29/99 - dynamic returning clause / varora 07/06/99 - change 6576 error message / nle 06/01/99 - reserve message for runtime / nle 05/28/99 - bug 890206 / astocks 05/25/99 - PL/SQL profiler errors / kmuthukk 10/12/98 - raise err for OPEN on non-queries / rdecker 09/22/98 - add substitute character to 6502 for sub msgs / alui 08/28/98 - Reserved error range 04930-04999 for Digital Unix. / arhee 07/23/98 - fix resmgr error msgs / arhee 04/13/98 - add dbscheduling messages / nikeda 04/07/98 - Add plsql error message for Pro* external procedures / kmuthukk 04/07/98 - update purity error / rtaranto 04/07/98 - Add 6538 for purity violations / rtaranto 04/07/98 - Add errors 6536/6537 for in/out binds / kmuthukk 02/24/98 - null dynamic statement / mluong 03/20/98 - fix comp error / kmuthukk 03/30/98 - pending autonmous transaction rolled back / varora 03/28/98 - add duplicate bind error for CALL / arhee 03/17/98 - add message for database scheduling / kquinn 03/18/98 - Add message 7345 / jsarma 03/10/98 - Add OER 7451-55 / varora 02/01/98 - add errors for call method statement / agreenbl 10/30/97 - Rename 7302 --> 7305 to match 8.0.x / agreenbl 06/27/97 - Remove obsolete sm errors / mluong 06/24/97 - merge from 803 / anolan 05/21/97 - checkout / anolan 05/14/97 - Demo. / kmuthukk 04/14/97 - restrict access of SR pkgs in triggers (b496997) / usundara 12/31/96 - incomplete and mutually-dependent types / o add ora-6545 for pl/sql error handling) / bcchang 12/20/96 - error.msg split / / / Trigger errors continued at 25000-25099 / / 4100-4499 Reserved for MVS OSD errors / / 4500-4899 Reserved for CMS OSD errors / / 4900-4929 Reserved for ICL DRS6000 / / 4930-4999 Reserved for Digital Unix / / 5000-5899 Reserved for OEM OSD errors / / 5900-5999 Reserved for Wang OSD errors (OEM: GABA) / / 6000-6499 Reserved for SQL*Net errors / / NETASY: 6000-6029 SQL*Net ASYNC Driver errors / / / Digital Unix specific errors (04930 - 04999). / This error range is used, starting from release 8.0.6, and 8.1.5. / The DEC specific errors 08324-08329 in e7500.msg are now listed here / as 04930 - 04935,04940. / 04930, 00000, "open sequence number failed or initial state is valid" // *Cause: Either Shared Sequence Number OS component was not installed // properly, or an MC hardware failure may have occurred or a // previous instance was not shut down properly. // *Action: Verify that there are no background or foreground Oracle // processes from a previous instance on this node using the OS // command ps -ef|grep . Verify that there are no // shared memory segments belonging to the user which owns the // Oracle installation by isuing the ipcs -b OS command. If there // are shared memory segments or processes still on the system, // use svrmgrl to shutdown the instance with the abort option. If // the instance is not up, verify that the cluster software and/or // the hardware is installed and working. Log in as superuser and // issue the cnxshow command. Are all of the nodes in the cluster // listed? Are they members of the cluster? Is the communications // between nodes okay? If the answer to any of these questions is // false, contact Digital's customer support organization. 04931, 00000, "unable to set initial sequence number value" // *Cause: A call to the SSN failed to set the sequence number to its initial // value, possibly caused by an MC hardware problem. // *Action: Verify that the MC hardware is functioning properly. If it is // not, contact Digital's customer support organization. If it is, // contact Oracle support. 04932, 00000, "increment or adjust of sequence number failed" // *Cause: A call to the SSN failed to increment the sequence number. // *Action: Verify that the MC hardware is functioning properly. If it is // not, contact Digital's customer support organization. If it is, // contact Oracle support. 04933, 00000, "initial service identifier is non-zero" // *Cause: A valid service identifier existed before the sequence number // service was opened. // *Action: Verify that the instance is completely shut down. 04934, 00000, "unable to obtain the current sequence number" // *Cause: A call to the SSN failed to return its current value. // Either there are many errors occurring on the MC hardware, // or the sequence number has become invalid and cannot be // validated. // *Action: Verify that the MC hardware is functioning properly. If it // is, contact Oracle Support. 04935, 00000, "unable to get/convert SCN recovery lock" // *Cause: A process has timed out trying to get or convert the SCN // recovery lock. Another process probably has the lock in // EX or SHR mode, but is not releasing it. // *Action: Contact Oracle Support. 04940, 00000, "unsupported optimization of Oracle binary, check alert log for more info" // *Cause: ORACLE binary has been optimized with unsupported options or // a required option has not been used. // *Action: Check the documentation for a list of supported and required flags // for the optimizing utility that you used to optimize ORACLE. // Shutdown the instance, optimize ORACLE again with supported // combination of options and restart the instance. 04941, 00000, "required operating system patch needs to be applied" // *Cause: The operating system could not return the start time of a // process. // *Action: Check that the operating system kernel has been patched // to return process start time. Apply the required operating // system patch and restart the instance. 06000, 00000, "NETASY: port open failure" // *Cause: Autologin unable to open port // *Action: Check log file for OS-specific error code 06001, 00000, "NETASY: port set-up failure" // *Cause: Autologin unable to change port attributes // *Action: Check log file for OS-specific error code 06002, 00000, "NETASY: port read failure" // *Cause: Autologin unable to read from port // *Action: Check log file for OS-specific error code 06003, 00000, "NETASY: port write failure" // *Cause: Autologin unable to write to port // *Action: Check log file for OS-specific error code 06004, 00000, "NETASY: dialogue file open failure" // *Cause: Autologin unable to open dialogue file // *Action: Check connect string for accuracy/typos 06005, 00000, "NETASY: dialogue file read failure" // *Cause: Autologin unable to read dialogue file // *Action: Check log file for OS-specific error code 06006, 00000, "NETASY: dialogue execute failure" // *Cause: Expected response never received // *Action: None 06007, 00000, "NETASY: bad dialogue format" // *Cause: Dialogue file contains syntax error // *Action: Correct the dialogue file 06009, 00000, "NETASY: dialogue filename too long" // *Cause: Full file spec for dialogue file exceeds 64 bytes // *Action: Amend connect string accordingly 06010, 00000, "NETASY: dialogue file too long" // *Cause: Dialogue file exceeds 768 bytes in length // *Action: Simplify dialogue (e.g. remove comments, redundant white space), // or split into two and link with "more" command 06011, 00000, "NETASY: dialogue too long" // *Cause: One of two: // 1. Dialogue contains more than 24 exchange blocks // 2. Dialogue send string exceeds 84 bytes in length // *Action: Simplify dialogue or split into two and link with "more" command 06017, 00000, "NETASY: message receive failure" // *Cause: Async driver gets I/O error while doing network read operation // *Action: Check log file for OS-specific error code and // contact your customer support representative. 06018, 00000, "NETASY: message send failure" // *Cause: Async driver gets I/O error while doing network write operation // *Action: Check log file for OS-specific error code and // contact your customer support representative. 06019, 00000, "NETASY: invalid login (connect) string" // *Cause: Syntax error in login string. // *Action: Resubmit with correct string. 06020, 00000, "NETASY: initialisation failure" // *Cause: Async driver unable to complete initialisation // *Action: Check log file for OS-specific error code 06021, 00000, "NETASY: connect failed" // *Cause: Async driver unable to establish connection with partner // *Action: Check log file for OS-specific error code 06022, 00000, "NETASY: channel open failure" // *Cause: no free channel [should never happen] // *Action: Contact your customer support representative. 06023, 00000, "NETASY: port open failure" // *Cause: Async driver unable to open port // *Action: Check log file for OS-specific error code 06024, 00000, "NETASY: VTM error" // *Cause: Virtual Terminal Manager unable to read/write to port // *Action: Check log file for OS-specific error code 06025, 00000, "NETASY: Configuration error" // *Cause: Async driver genned for server-only, but client service requested // *Action: Contact your customer support representative. 06026, 00000, "NETASY: port close failure" // *Cause: Async driver unable to close port // *Action: Check log file for OS-specific error code 06027, 00000, "NETASY: channel close failure" // *Cause: Async driver unable to close channel // *Action: Check log file for OS-specific error code 06028, 00000, "NETASY: unable to intialise for logging" // *Cause: Async driver unable to initialise for logging I/O // *Action: Contact your customer support representative. 06029, 00000, "NETASY: port assignment failure" // *Cause: Async driver unable to assign port to channel [should never happen] // *Action: Contact your customer support representative. / / NETDNT: 6030-6049 SQL*Net DECnet Driver errors / 06030, 00000, "NETDNT: connect failed, unrecognized node name" // *Cause: Node name specified in host string is unknown (probably misspelled) // *Action: Retry with correct node name 06031, 00000, "NETDNT: connect failed, unrecognized object name" // *Cause: Host string contains reference to object (which doesn't exist): // @d:- => 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: PL/SQL was unable to allocate additional storage. This message // normally appears with an ORA-4030 or ORA-4031 error which gives // additional information. Sometimes this error can be caused by // runaway programs. // *Action: 1) Ensure there are no issues or bugs in your PL/SQL program which // are causing excessive amounts of memory to be used. // 2) Programmatically cause unused objects to be freed (e.g. by // setting them to NULL). // 3) Increase the amount of shared or process memory (as appropriate) // available to you. 06501, 00000, "PL/SQL: program error" // *Cause: This is an internal error message. An error has been detected in a // PL/SQL program. // *Action: Contact Oracle Support Services. 06502, 00000, "PL/SQL: numeric or value error%s" // *Cause: An arithmetic, numeric, string, conversion, or constraint error // occurred. For example, this error occurs if an attempt is made to // assign the value NULL to a variable declared NOT NULL, or if an // attempt is made to assign an integer larger than 99 to a variable // declared NUMBER(2). // *Action: Change the data, how it is manipulated, or how it is declared so // that values do not violate constraints. 06503, 00000, "PL/SQL: Function returned without value" // *Cause: A call to PL/SQL function completed, but no RETURN statement was // executed. // *Action: Rewrite PL/SQL function, making sure that it always returns // a value of a proper type. 06504, 00000, "PL/SQL: Return types of Result Set variables or query do not match" // *Cause: Number and/or types of columns in a query does not match declared // return type of a result set variable, or declared types of two Result // Set variables do not match. // *Action: Change the program statement or declaration. Verify what query the variable // actually refers to during execution. 06505, 00000, "PL/SQL: variable requires more than 32767 bytes of contiguous memory" // *Cause: A PL/SQL variable was declared with a constraint which required more // than 32767 bytes of memory. // PL/SQL does not currently support allocations of contiguous memory // greater than 32767 bytes. // *Action: Consider reducing the constraint in the variable declaration. // If that is not possible, try changing the database or national // character set to such, that requires less memory for the same // constraint. Note: changing the character set will impact execution // of all PL/SQL code. 06508, 00000, "PL/SQL: could not find program unit being called%s" // *Cause: // *Action: 06509, 00000, "PL/SQL: ICD vector missing for this package" // *Cause: // *Action: 06510, 00000, "PL/SQL: unhandled user-defined exception" // *Cause: A user-defined exception was raised by PL/SQL code, but // not handled. // *Action: Fix the problem causing the exception or write an exception // handler for this condition. Or you may need to contact your // application administrator or DBA. 06511, 00000, "PL/SQL: cursor already open" // *Cause: An attempt was made to open a cursor that was already open. // *Action: Close cursor first before reopening. 06512, 00000, "at %sline %s" // *Cause: Backtrace message as the stack is unwound by unhandled // exceptions. // *Action: Fix the problem causing the exception or write an exception // handler for this condition. Or you may need to contact your // application administrator or DBA. 06513, 00000, "PL/SQL: index for PL/SQL table out of range for host language array" // *Cause: An attempt is being made to copy a PL/SQL table to a host language // array. But an index in the table is either less than one or // greater than the maximum size of the host language array. // When copying PL/SQL tables to host language arrays, the table // entry at index 1 is placed in the first element of the array, the // entry at index 2 is placed in the second element of the array, etc. // If an table entry has not been assigned then the corresponding // element in the host language array is set to null. // *Action: Increase size of host language array, or decrease size of PL/SQL // table. Also make sure that you don't use index values less than 1. // 06514, 00000, "PL/SQL: The remote call cannot be handled by the server" // *Cause: The remote call has parameters that are cursor variables or // lob variables. This cannot be handled by stored procedures on // your server. // *Action: Avoid using cursor variables or lob variables as parameters for // stored procedures on this server or upgrade your server to a // version that supports this. 06515, 00000, "PL/SQL: unhandled exception %s" // *Cause: An exception was raised by PL/SQL code, but not handled. // The exception number is outside the legal range of Oracle // errors. // *Action: Fix the problem causing the exception or write an exception // handler for this condition. Or you may need to contact your // application administrator or DBA. // *Comment: The exception was created via a pragma exception_init with a // value larger than MAX_OEN. This capability exists for backward // compatibility with V1 PL/SQL. 06516, 00000, "PL/SQL: the Probe packages do not exist or are invalid" // *Cause: A Probe operation, probably an attempt to initialize the ORACLE // server to debug PL/SQL, could not be completed because the // Probe packages were not loaded or have become invalid. // *Action: DBA should load the Probe packages. This can be done by running // the pbload.sql script supplied with the RDBMS. // *Comment: catproc.sql should load Probe by default, but it did not do so // in releases prior to 7.3.3. // 06517, 00000, "PL/SQL: Probe error - %s" // *Cause: An error occurred while passing a Probe operation to the server // for execution. // *Action: Refer to the entry for the embedded error message. // *Comment: The error is most likely a UPI or network problem. The Probe // error is just to let the user know how the error arose. 06518, 00000, "PL/SQL: Probe version %s incompatible with version %s" // *Cause: The current version of Probe is incompatible with the version on // the ORACLE server. // *Action: Refer to the documentation to ensure that this degree of // compatibility is supported. // *Comment: This error is not currently expected. It will only occur at a // later time if incompatible Probe changes are introduced. 06519, 00000, "active autonomous transaction detected and rolled back" // *Cause: Before returning from an autonomous PL/SQL block, all autonomous // transactions started within the block must be completed (either // committed or rolled back). If not, the active autonomous // transaction is implicitly rolled back and this error is raised. // *Action: Ensure that before returning from an autonomous PL/SQL block, // any active autonomous transactions are explicitly committed // or rolled back. //----------------------------------------------------------------------- // // 06520 through 06529 reserved for Foreign function errors // // 06520, 00000, "PL/SQL: Error loading external library" // *Cause: An error was detected by PL/SQL trying to load the external // library dynamically. // *Action: Check the stacked error (if any) for more details. // 06521, 00000, "PL/SQL: Error mapping function" // *Cause: An error was detected by PL/SQL trying to map the mentioned // function dynamically. // *Action: Check the stacked error (if any) for more details. // 06522, 00000, "%s" // *Cause: ORA-06520 or ORA-065211 could stack this error with // a system specific error string. // *Action: This error string should give the cause for errors // ORA-06520 or ORA-065211 // 06523, 00000, "Maximum number of arguments exceeded" // *Cause: There is an upper limit on the number of arguments that one // can pass to the external function. // *Action: Check the port specific documentation on how to calculate the // upper limit. // 06524, 00000, "Unsupported option : %s" // *Cause: The option specified is an unsupported feature for external procedures. // // *Action: Correct the syntax in the external specification // 06525, 00000, "Length Mismatch for CHAR or RAW data" // *Cause: The length specified in the length variable has an illegal // value. This can happen if you have requested requested a PL/SQL // INOUT, OUT or RETURN raw variable to be passed as a RAW with // no corresponding length variable. This error can also happen // if there is a mismatch in the length value set in the length // variable and the length in the orlvstr or orlraw. // // *Action: Correct the external procedure code and set the length variable // correctly. // 06526, 00000, "Unable to load PL/SQL library" // *Cause: PL/SQL was unable to instantiate the library referenced by this // referenced in the EXTERNAL syntax. This is a serious error and // should normally not happen. // // *Action: Report this problem to customer support. // 06527, 00000, "External procedure SQLLIB error: %s" // *Cause: An error occurred in sqllib during execution of a Pro* external // procedure. // // *Action: The message text indicates the actual SQLLIB error that // occurred. Consult the Oracle Error Messages and Codes manual // for a complete description of the error message and follow // the appropriate action. // 06528, 00000, "Error executing PL/SQL profiler" // *Cause: An error occurred in during execution of a PL/SQL profiler // procedure. // // *Action: Check the stacked errors for more details. // 06529, 00000, "Version mismatch - PL/SQL profiler" // *Cause: The PL/SQL profiler package (dbmspb.sql, prvtpbp.plb) does not // match the version of the code in the server implementing the // profiler. // // *Action: Run the package profload.sql in $ORACLE_HOME/rdbms/admin to load // the correct version of the PL/SQL profiler packages // 06530, 00000, "Reference to uninitialized composite" // *Cause: An object, LOB, or other composite was referenced as a // left hand side without having been initialized. // *Action: Initialize the composite with an appropriate constructor // or whole-object assignment. // 06531, 00000, "Reference to uninitialized collection" // *Cause: An element or member function of a nested table or varray // was referenced (where an initialized collection is needed) // without the collection having been initialized. // *Action: Initialize the collection with an appropriate constructor // or whole-object assignment. // 06532, 00000, "Subscript outside of limit" // *Cause: A subscript was greater than the limit of a varray // or non-positive for a varray or nested table. // *Action: Check the program logic and increase the varray limit // if necessary. // 06533, 00000, "Subscript beyond count" // *Cause: An in-limit subscript was greater than the count of a varray // or too large for a nested table. // *Action: Check the program logic and explicitly extend if necessary. // 06534, 00000, "Cannot access Serially Reusable package %s" // *Cause: The program attempted to access a Serially Reusable package in // PL/SQL called from SQL context (trigger or otherwise). Such an // access is currently unsupported. // *Action: Check the program logic and remove any references to Serially Reusable // packages (procedure, function or variable references) which might happen // in PL/SQL called from sql context (trigger or otherwise). // 06535, 00000, "statement string in %s is NULL or 0 length" // *Cause: The program attempted to use a dynamic statement string that // was either NULL or 0 length. // *Action: Check the program logic and ensure that the dynamic statement // string is properly initialized. // 06536, 00000, "IN bind variable bound to an OUT position" // *Cause: The program attempted to bind an IN bind variable to a // statement that was expecting an OUT bind variable at // that position. // *Action: Make sure that an OUT or IN OUT bind mode is specified // for the bind argument. // 06537, 00000, "OUT bind variable bound to an IN position" // *Cause: The program attempted to bind an OUT bind variable to a // statement that was expecting an IN bind variable at // that position. // *Action: Make sure that an IN or IN OUT bind mode is specified // for the bind argument. // 06538, 00000, "statement violates %s RESTRICT_REFERENCES pragma" // *Cause: The program attempted to execute a dynamic statement which // does not meet the purity level specified (in the pragma // RESTRICT_REFERENCES directive) for the module executing the // statement. // *Action: Ensure that the dynamic statement meets the purity level // specified for the module executing the statement. // 06539, 00000, "target of OPEN must be a query" // *Cause: The program attempted to perform an OPEN cursor operation // on a dynamic statement that was not a query. // *Action: Ensure that the OPEN cursor operation is done on a // dynamic query statement. // //-------------------------------------------------------- // 06540 through 06549 reserved for pl/sql error handling // 06540, 00000, "PL/SQL: compilation error" // *Cause: A pl/sql compilation error occurred. // However, the user generally will not see this error message. // Instead, there will be accompanying PLS-nnnnn error messages. // *Action:See accompanying PLS-nnnnn error messages. // 06541, 00000, "PL/SQL: compilation error - compilation aborted" // *Cause: A pl/sql compilation error occurred and the compilation was aborted; // but the compilation unit was written out to the backing store. // However, unlike ora-06545, the user generally will not see this error // message. Instead, there will be accompanying PLS-nnnnn error messages. // *Action:See accompanying PLS-nnnnn error messages. // 06542, 00000, "PL/SQL: execution error" // Currently unused. Reserved for future use. // 06543, 00000, "PL/SQL: execution error - execution aborted" // // 06544, 00000, "PL/SQL: internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" // *Cause: A pl/sql internal error occurred. // *Action:Report as a bug; the first argument is the internal error nuber. // 06545, 00000, "PL/SQL: compilation error - compilation aborted" // *Cause: A pl/sql compilation error occurred and the compilation was // aborted completely without the compilation unit being written // out to the backing store. Unlike ora-06541, the user will always // see this error along with the accompaning PLS-nnnnn error messages. // *Action:See accompanying PLS-nnnnn error messages. // 06546, 00000, "DDL statement is executed in an illegal context" // *Cause: DDL statement is executed dynamically in illegal PL/SQL context. // - Dynamic OPEN cursor for a DDL in PL/SQL // - Bind variable's used in USING clause to EXECUTE IMMEDIATE a DDL // - Define variable's used in INTO clause to EXECUTE IMMEDIATE a DDL // *Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute // the DDL statement. 06547, 00000, "RETURNING clause must be used with INSERT, UPDATE, or DELETE statements" // *Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute // dynamic UPDATE, INSERT, or DELETE statements only. // *Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, // or DELETE statements only. For other statements, use USING clause // instead. 06548, 00000, "no more rows needed" // *Cause: The caller of a pipelined function did not need more rows // to be produced by the pipelined function. // *Action: Do not catch the NO_DATA_NEEDED exception in an exception handling // block. // 06549, 00000, "PL/SQL: failed to dynamically open shared object (DLL): %s:%s" // *Cause: One possible cause might be there are too many DLLs open at the // same time. // *Action: // //-------------------------------------------------------- // 06550, 00000, "line %s, column %s:\n%s" // *Cause: Usually a PL/SQL compilation error. // *Action: 06551, 00000, "PL/SQL: Unhandled exception" // *Cause: // *Action: 06552, 00000, "PL/SQL: %s" // *Cause: // *Action: 06553, 00000, "PLS-%s: %s" // *Cause: // *Action: 06554, 00000, "package DBMS_STANDARD must be created before using PL/SQL" // *Cause: The DBMS specific extensions to PL/SQL's package "STANDARD" // are in package "DBMS_STANDARD". This package must be // created before using PL/SQL. // *Action: Create package "DBMS_STANDARD". The source for this // PL/SQL stored package is provided with the distribution. 06555, 00000, "this name is currently reserved for use by user SYS" // *Cause: You tried to create a package named "STANDARD", // "DBMS_STANDARD" or "DEBUG_IO". These are currently // reserved for use by user SYS. // *Action: Choose another name for your package. 06556, 00000, "the pipe is empty, cannot fulfill the unpack_message request" // *Cause: There are no more items in the pipe. // *Action: Check that the sender and receiver agree on the number and types // of items placed on the pipe. 06557, 00000, "null values are not allowed for any parameters to pipe icd's" // *Cause: Internal error from the dbms_pipe package. // *Action: 06558, 00000, "buffer in dbms_pipe package is full. No more items allowed" // *Cause: The pipe buffer size has been exceeded. // *Action: 06559, 00000, "wrong datatype requested, %s, actual datatype is %s" // *Cause: The sender put different datatype on the pipe than that being // requested (package 'dbms_pipe'). The numbers are: 6 - number, // 9 - char, 12 - date. // *Action: Check that the sender and receiver agree on the number and types // of items placed on the pipe. 06560, 00000, "pos, %s, is negative or larger than the buffer size, %s" // *Cause: Internal error from the dbms_pipe package. // *Action: 06561, 00000, "given statement is not supported by package DBMS_SQL" // *Cause: Attempting to parse an unsupported statement using procedure // PARSE provided by package DBMS_SQL. // *Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, // LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported. 06562, 00000, "type of out argument must match type of column or bind variable" // *Cause: Attempting to get the value of a column or // a bind variable by calling procedure COLUMN_VALUE or // VARIABLE_VALUE of package DBMS_SQL but the type of // the given out argument where to place the value is different // from the type of the column or bind variable that was previously // defined by calling procedure DEFINE_COLUMN (for defining a column) // or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL. // *Action: Pass in an out argument of the correct type when calling // procedure COLUMN_VALUE or VARIABLE_VALUE. The right // type is the type that was provided when defining the column or // binding the bind variable. 06563, 00000, "name has too many parts" // *Cause: The name to be resolved was specified as one of the following: // - With three parts (A.B.C) but the A.B parts resolved to an object // that did not expose visible nested procedures; the C part could // not be resolved. // - With two parts (A.B) and the A part resolved to an object that // did not expose visible nested procedures; the B part could not be // resolved. // *Action: Specify the valid name of an object or of a packaged procedure // or function without specifying any additional trailing parts. 06564, 00000, "object %s does not exist" // *Cause: The named object could not be found. Either it does not exist // or you do not have permission to access it. // *Action: Create the object or get permission to access it. 06565, 00000, "cannot execute %s from within stored procedure" // *Cause: The named procedure cannot be executed from within a stored // procedure, function or package. This function can only be // used from pl/sql anonymous blocks. // *Action: Remove the procedure from the calling stored procedure. 06566, 00000, "invalid number of rows specified" // *Cause: An invalid number of rows was specified in a call to the // procedure DEFINE_COLUMN in the package DBMS_SQL. For a given // parsed statement in a given cursor, all columns must be // defined to have the same number of rows, so all the calls // to DEFINE_COLUMN must specify the same number of rows. // *Action: Specify a number that matches that for previously defined // columns. 06567, 00000, "invalid number of values specified" // *Cause: An invalid number of values to be bound was specified in a // call to the procedure BIND_VARIABLE in the package DBMS_SQL. // In order to execute a given parsed statement in a given cursor, // the same number of values must have been bound for all bind // variables, so when EXECUTE is called, the latest calls to // BIND_VARIABLE must must have specified the same number of values // to be bound for all bind variables. // *Action: Make sure that the same number of values have been bound for all // of the bind variables. 06568, 00000, "obsolete ICD procedure called" // *Cause: An obsolete ICD procedure was called by a PL/SQL program. // The PL/SQL program was probably written for an eralier release of // RDBMS. // *Action: Make sure that all PL/SQL programs have been upgraded to the latest // release of the RDBMS. This can be accomplished by following // upgrade instructions in the README file, or by running // the catproc.sql script supplied with the RDBMS. 06569, 00000, "Collection bound by bind_array contains no elements" // *Cause: A collection with zero elements was bound to a bind variable // in a call to procedure BIND_ARRAY in the package DBMS_SQL. // In order to execute a bind of a collection, the collection must // contain at least one element. If no elements are present then // at execute time there will be no value for this bind and the // statement is meaningless. // *Action: Fill the collection with the elements you want to bind and // try the bind call again. / / 06570, 00000, "shared pool object does not exist, cannot be pinned/purged" // *Cause: The specified shared pool shared cursor could not be found, // therefore it cannot be pinned/purged. // *Action: Make sure that a correct shared cursor name is given. Names // are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's // are an 8 digit hex number from the 'address' column of v$sqlarea, // and the D's are a 1 to 10 digit decimal number with an optional // leading sign (from the 'hash_value' column) // *Action: Remove the procedure from the calling stored procedure. / / 6571-6579 Reserved for Plsql functions called from Sql / 06571, 00000, "Function %s does not guarantee not to update database" // *Cause: There are two possible causes for this message: // * A SQL statement references a packaged, PL/SQL function // that does not contain a pragma that prevents the database // from being updated. // * A SQL statement references a stand-alone, PL/SQL function // that contains an instruction to update the database. // *Action: If the referenced function is a packaged, PL/SQL function: // Recreate the PL/SQL function with the required pragma; be // certain to include the 'Write No Database State' (WNDS) // argument in the argument list of the pragma. // If the referenced function is a stand-alone, PL/SQL function: // Do not use the function. 06572, 00000, "Function %s has out arguments" // *Cause: A SQL statement references either a packaged, or a stand-alone, // PL/SQL function that contains an OUT parameter in its argument // list. PL/SQL functions referenced by SQL statements must not // contain the OUT parameter. // *Action: Recreate the PL/SQL function without the OUT parameter in the // argument list. 06573, 00000, "Function %s modifies package state, cannot be used here" // *Cause: There are two possible causes for this message: // * A SQL statement references a packaged, PL/SQL function that // does not contain a pragma containing the 'Write no Package // State' (WNPS). // * A SQL statement references a stand-alone, PL/SQL function // that modifies a package state. A stand-alone, PL/SQL function // referenced by a SQL statement cannot modify a package state. // *Action: If the function is a packaged, PL/SQL function: Recreate // the function and include a pragma containing the 'Write no // Package State' (WNPS). // If the function is a stand-alone, PL/SQL function: Delete // the function from the SQL statement. 06574, 00000, "Function %s references package state, cannot execute remotely" // *Cause: There are two possible causes for this message: // * A remote, packaged function or a remote-mapped, local, // packaged function that does not contain a pragma with the // 'Write no Package State' (WNPS) and 'Read no Package State' // (RNPS) arguments references a package state. // * A remote, stand-alone function or a remote-mapped, local, // stand-alone function contains a reference to a package // state (reads or writes a package variable). // Only local functions that are referenced in a SELECT list, VALUES // clause of an INSERT statement, or SET clause of an UPDATE // statement can modify a package state. // *Action: If the function is a packaged function: Recreate the function // and include a pragma containing the 'Write no Package State' // (WNPS) and 'Read no Package State' (RNPS) arguments. // If the function is a stand-alone function: Do not call the // function. 06575, 00000, "Package or function %s is in an invalid state" // *Cause: A SQL statement references a PL/SQL function that is in an // invalid state. Oracle attempted to compile the function, but // detected errors. // *Action: Check the SQL statement and the PL/SQL function for syntax // errors or incorrectly assigned, or missing, privileges for a // referenced object. 06576, 00000, "not a valid function or procedure name" // *Cause: Could not find a function (if an INTO clause was present) or // a procedure (if the statement did not have an INTO clause) to // call. // *Action: Change the statement to invoke a function or procedure 06577, 00000, "output parameter not a bind variable" // *Cause: The argument corresponding to an IN/OUT or OUT parameter // for a function or a procedure or a function return value in // a CALL statement must be a bind variable. // *Action: Change the argument to a bind variable 06578, 00000, "output parameter cannot be a duplicate bind" // *Cause: The bind variable corresponding to an IN/OUT or OUT parameter // for a function or a procedure or a function return value in a // CALL statement cannot be a duplicate bind variable. // *Action: Change the bind variable to be unique / 06579, 00000, " Bind variable not big enough to hold the output value" // *Cause: The bind variable specified by the user is not large enough to // hold the output returned by the function or a procedure. // *Action: Specify a bind variable of larger size. / 06580, 00000, "Hash Join ran out of memory while keeping large rows in memory" // *Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * // HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than // that, this error will be raised. // *Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row // fits in a slot. HASH_AREA_SIZE may also need to be increaed. / / 6581-6591 Reserved for European OEM Ports (contact: egroenen.nl) / 06592, 00000, "CASE not found while executing CASE statement" // *Cause: A CASE statement must either list all possible cases or have an // else clause. // *Action: Add all missing cases or an else clause. / 06593, 00000, "%s is not supported with natively compiled PL/SQL modules" // *Cause: Specified feature is not yet supported for natively compiled // PL/SQL modules yet. // *Action: Recompile the relevant PL/SQL modules in non-native mode by // setting the parameter plsql_compiler_flags to INTERPRETED. / 06594, 00000, "ICD is unable to compute a result" // *Document: NO // *Cause: This exception is internal to PL/SQL, and should not be seen by // customers. // *Action: Contact Oracle Support Services. / 06595, 00000, "REF CURSOR parameters are not supported in forwarded RPC calls" // *Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR // parameter. // *Action: Either call the remote function directly (i.e., not by way of // forwarding), or move the remote function to a database where it can // be called directly. / 06596, 00000, "object cannot be purged, object is permanently kept in shared pool" // *Cause: The specified object was permanently kept, therefore, cannot be // purged. // *Action: Use DBMS_SHARED_POOL.UNKEEP procedure to unkeep the object and then // purge it. / 06597, 00000, "Failed to increase the session's call stack memory to %s bytes at a depth of %s calls. (The current maximum is %s bytes.)" // *Cause: PL/SQL program execution used more call stack memory than permitted. // *Action: * Ask your DBA to increase the maximum allowed call stack memory. // * Decrease the amount of call stack used by the program. This may // be accomplished by using fewer, smaller local variables, or by // limiting the depth of function call nesting. / / 6600-6699 Reserved for more SQL*Net errors / / 6700-6899 Reserved for TLI SQL*NET driver errors / / 6900-6999 Reserved for more SQL*Net errors / / / 6600 - 6622: SQL*Net LU6.2 driver errors / 06600, 00000, "LU6.2 Driver: SNA software is not loaded" // *Cause: The SNA software is not running. // *Action: Start the SNA software and try again. 06601, 00000, "LU6.2 Driver: Invalid database ID string" // *Cause: The database string in the connect was invalid. // *Action: Provide a valid database string, as defined in documentation. 06602, 00000, "LU6.2 Driver: Error allocating context area" // *Cause: Context area failure. // *Action: Contact your local service representative. 06603, 00000, "LU6.2 Driver: Error allocating memory" // *Cause: Operating system refused request for memory. // *Action: Contact you local service representative. 06604, 00000, "LU6.2 Driver: Unable to allocate session with remote LU" // *Cause: Allocate system call failed. // *Action: Ensure that the SNA software is running and that sessions are free. // If this is the case, then check your SNA configuration data for // errors. You may have entered an incorrect parameter. 06605, 00000, "LU6.2 Driver: Unexpected line turnaround" // *Cause: SNA software switched from send to receive unexpectedly. // *Action: Check the SNA configuration data, particularly parameters // associated with a session. 06606, 00000, "LU6.2 Driver: Unexpected response from SNA" // *Cause: A parameter in an SNA call returned an unexpected value. // *Action: Attempt to reproduce problem, debug and record the value of the // 'what' data parameter at the time of error. Then contact your // service representative. 06607, 00000, "LU6.2 Driver: Reset occurred in send state" // *Cause: A reset was issued whilst in send state. // *Action: Check the SNA LOG data, if relevent, for further information. 06608, 00000, "LU6.2 Driver: Reset occurred in receive state" // *Cause: A reset was received from the partner whilst in receive // state. This may be because the partner deallocated. // *Action: Check the SNA LOG data, if relevent, for further information. / / 06609 is not used by the LU6.2 Driver. / 06610, 00000, "LU6.2 Driver: Failed during deallocation" // *Cause: LU6.2 driver was unable to deallocate gracefully. // *Action: Check the reason for deallocation. Consult the SNA // LOG data. 06611, 00000, "LU6.2 Driver: Request to send error" // *Cause: // *Action: 06612, 00000, "LU6.2 Driver: Send data error" // *Cause: // *Action: 06613, 00000, "LU6.2 Driver: Receive and wait error" // *Cause: // *Action: 06614, 00000, "LU6.2 Driver: Receive Immediate error" // *Cause: // *Action: 06615, 00000, "LU6.2 Driver: Send error" // *Cause: // *Action: 06616, 00000, "LU6.2 Driver: Attach to LU failed" // *Cause: The SQL*Net LU6.2 driver was unable to attach to the // LU specified in the connect string, or was unable to // attach to the default LU. // *Action: Check that the LU name specified in the connect string, // or the default LU name if no LU was specified, is // correctly configured and operational. 06617, 00000, "LU6.2 Driver: Attach to PU failed" // *Cause: // *Action: 06618, 00000, "LU6.2 Driver: Activation of subnetwork failed" // *Cause: // *Action: 06619, 00000, "LU6.2 Driver: Unable to activate remote partner" // *Cause: // *Action: 06620, 00000, "LU6.2 Driver: Invalid remote partner" // *Cause: // *Action: 06621, 00000, "LU6.2 Driver: Allocation error" // *Cause: // *Action: 06622, 00000, "LU6.2 Driver: Unable to attach to SNA" // *Cause: The SQL*Net LU6.2 driver could not attach to the SNA // software on your machine. The most likely cause is that the SNA // software is not operational. // *Action: Check the status of the SNA software, ensure that it is // operational and then try again. / / 6700-6899 Reserved for TLI SQL*NET driver errors / 06700, 00000, "TLI Driver: incorrect message type from host" // *Cause: TLI received a message with an unrecognizable message type. // *Action: Contact your customer support representative. 06701, 00000, "TLI Driver: incorrect number of bytes written" // *Cause: TLI sent a message that was apparently successful, but the // number of bytes transmitted did not match the number // of bytes supplied to the driver. // *Action: Contact your customer support representative. 06702, 00000, "TLI Driver: cannot allocate context area" // *Cause: TLI could not allocate heap space for the context area. // *Action: Contact your customer support representative. 06703, 00000, "TLI Driver: send break message failed" // *Cause: TLI failed to send a break message across the connection. // *Action: Contact your customer support representative. 06704, 00000, "TLI Driver: receive break message failed" // *Cause: TLI failed to receive an expected break message. // *Action: Contact your customer support representative. 06705, 00000, "TLI Driver: remote node is unknown" // *Cause: TLI could not find your remote host information. // *Action: Make sure you specified the hostname correctly on the command // line. (Also, check your capitalization and spelling.) 06706, 00000, "TLI Driver: service not found" // *Cause: TLI could not find service information for the specified service // name. // *Action: If you specified the service name on the command line or with the // environment variable TLI_SERVER, make sure you specified it // correctly. If the service name is not in the SERVICES file for // your protocol, ask your system adminstrator to add it. 06707, 00000, "TLI Driver: connection failed" // *Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server // due to an error encountered by the remote server, which has // supplied a string describing the remote error. // *Action: See the SQL*Net TCP/IP User's Guide section "orasrv Messages" for // the specific cause and action. 06708, 00000, "TLI Driver: message receive failure" // *Cause: TLI encountered an error receiving a message from the communication // channel. // *Action: Contact your customer support representative. 06709, 00000, "TLI Driver: message send failure" // *Cause: TLI encountered an error sending a message across the communication // channel. // *Action: Contact your customer support representative. 06710, 00000, "TLI Driver: send interrupt break message failed" // *Cause: TLI failed to send a break message while handling an interrupt // signal from the user. // *Action: Contact your customer support representative. 06711, 00000, "TLI Driver: error on bind" // *Cause: TLI failed to assign a network address to the communication channel. // *Action: Contact your customer support representative. 06712, 00000, "TLI Driver: error on accept" // *Cause: TLI failed to accept a connection request from the client. // *Action: Contact your customer support representative. 06713, 00000, "TLI Driver: error on connect" // *Cause: TLI failed to connect the client to the remote server. The network // line to the remote host may be down. // *Action: Use other network login programs to make sure that the remote // host is accessible. 06720, 00000, "TLI Driver: SID lookup failure" // *Cause: The database SID supplied in the database login string was not // recognized by the remote host. // *Action: Ask your system administrator to add the appropriate SID entry // to oratab on the remote host. 06721, 00000, "TLI Driver: spurious client req" // *Cause: The remote TLI server received an undefined request. // *Action: Contact your customer support representative. 06722, 00000, "TLI Driver: connection setup failure" // *Cause: The remote TLI server rejected the connection request, and the // client was unable to retrieve an error code or message. // *Action: Contact your customer support representative. 06730, 00000, "TLI Driver: unable to open clone device" // *Cause: TLI failed to open the Streams clone device associated with the // transport provider. // *Action: Contact your customer support representative. 06731, 00000, "TLI Driver: cannot alloc t_call" // *Cause: TLI cannot allocate space for the client's connection information. // *Action: Contact your customer support representative. 06732, 00000, "TLI Driver: cannot alloc t_discon" // *Cause: TLI cannot allocate space for the client's disconnection // information. // *Action: Contact your customer support representative. 06733, 00000, "TLI Driver: failed to receive disconnect" // *Cause: TLI failed to receive an expected disconnection message during // connection release. // *Action: Contact your customer support representative. 06734, 00000, "TLI Driver: cannot connect" // *Cause: TLI failed to connect the client to the remote server. // *Action: Check that the remote TLI server is running. 06735, 00000, "TLI Driver: client failed to close error conn" // *Cause: TLI failed to properly close a connection after an error was // received. // *Action: Contact your customer support representative. 06736, 00000, "TLI Driver: server not running" // *Cause: TLI timed out while attempting to connect to the remote TLI server. // *Action: Check that the remote TLI server is running with the status utility // for the transport provider you are using. If it is not, ask // your system adminstrator to start it. 06737, 00000, "TLI Driver: connection failed" // *Cause: TLI could not establish a connection to the remote TLI server. // *Action: Check that the remote TLI server is running with the status // utility for the transport provider you are using. 06741, 00000, "TLI Driver: unable to open protocol device" // *Cause: The TLI server failed to open the Streams device associated with // the transport provider. // *Action: Contact your customer support representative. 06742, 00000, "TLI Driver: cannot alloc t_bind" // *Cause: The TLI server cannot allocate space for its requested network // address. // *Action: Contact your customer support representative. 06743, 00000, "TLI Driver: cannot alloc t_bind" // *Cause: The TLI server cannot allocate space for its actual network // address. // *Action: Contact your customer support representative. 06744, 00000, "TLI Driver: listener cannot bind" // *Cause: The TLI server failed to assign the correct network address on // which to listen for connections. // *Action: Contact your customer support representative. 06745, 00000, "TLI Driver: listener already running" // *Cause: The network address on which the TLI server awaits connection // requests is in use, possibly because the server is already running. // *Action: Ensure that the TLI server is not already running. If it is // not running and this error message recurs, contact your customer // support representative. 06746, 00000, "TLI Driver: cannot alloc t_call" // *Cause: TLI cannot allocate space for the TLI server's connection // information. // *Action: Contact your customer support representative. 06747, 00000, "TLI Driver: error in listen" // *Cause: The TLI server encountered an error while listening for // connection requests. // *Action: Contact your customer support representative. 06748, 00000, "TLI Driver: cannot allocate t_discon" // *Cause: TLI cannot allocate space for the TLI server's disconnection // information. // *Action: Contact your customer support representative. 06749, 00000, "TLI Driver: option not allowed across network" // *Cause: The requested TLI server command must be issued from the same // host on which the server is running. // *Action: Log in to the remote host and try again. 06750, 00000, "TLI Driver: sync failed" // *Cause: The ORACLE process started by the TLI server was unable to // synchronize its inherited connection. // *Action: Contact your customer support representative. 06751, 00000, "TLI Driver: bound addresses unequal" // *Cause: The osn check server address failed. The bound server address was // not the same as the requested binding address. // *Action: Contact your customer support representative. 06752, 00000, "TLI: error in signal setup" // *Cause: A call to sigaction() returned with a system error. // *Action: Contact your customer support representative. 06753, 00000, "TLI Driver: name-to-address mapping failed" // *Cause: For SVR4, the netdir_getbyname() call failed for some // unknown reason. // *Action: Contact your custumer service representative. 06754, 00000, "TLI Driver: unable to get local host address" // *Cause: The name of the remote host to connect to was not specified, and // the name of the local host cannot be retrieved from the HOSTS file. // *Action: Contact your system administrator. 06755, 00000, "TLI Driver: cannot close transport endpoint" // *Cause: The TLI server was unable to close a connection after passing it // to an ORACLE process. // *Action: Contact your customer support representative. 06756, 00000, "TLI Driver: cannot open oratab" // *Cause: The TLI server could not open the file used to define the locations // of remotely accessible databases. // *Action: Ask your system administrator to check that the file exists and // has the correct permissions. 06757, 00000, "TLI Driver: server got bad command" // *Cause: The TLI server received an invalid command. // *Action: Contact your customer support representative. 06760, 00000, "TLI Driver: timeout reading orderly release" // *Cause: TLI was not able to retreive an expected disconnect message while // closing the communication channel. // *Action: Contact your customer support representative. 06761, 00000, "TLI Driver: error sending orderly release" // *Cause: TLI encountered an error sending a disconnect message closing the // communication channel. // *Action: Contact your customer support representative. 06762, 00000, "TLI Driver: error reading orderly release" // *Cause: TLI encountered an error receiving an expected disconnect message // while closing the communication channel. // *Action: Contact your customer support representative. 06763, 00000, "TLI Driver: error sending disconnect" // *Cause: TLI encountered an error sending a disconnect message closing the // communication channel. // *Action: Contact your customer support representative. 06764, 00000, "TLI Driver: error reading disconnect" // *Cause: TLI was not able to retreive an expected disconnect message while // closing the communication channel. // *Action: Contact your customer support representative. 06765, 00000, "TLI Driver: error awaiting orderly release" // *Cause: TLI encountered an error awaiting a disconnect message while // closing the communication channel. // *Action: Contact your customer support representative. 06766, 00000, "TLI Driver: close failed during release" // *Cause: TLI failed to close the communication channel after receiving // a disconnect message. // *Action: Contact your customer support representative. 06767, 00000, "TLI Driver: alloc failed during release" // *Cause: TLI cannot allocate space for disconnection information while // closing the communication channel. // *Action: Contact your customer support representative. 06770, 00000, "TLI Driver: error sending version" // *Cause: TLI encountered an error while sending its version information // during connection establishment. // *Action: Contact your customer support representative. 06771, 00000, "TLI Driver: error reading version" // *Cause: TLI encountered an error while awaiting the expected version // information during connection establishment. // *Action: Contact your customer support representative. 06772, 00000, "TLI Driver: error sending command" // *Cause: TLI encountered an error while sending a command message during // connection establishment. // *Action: Contact your customer support representative. 06773, 00000, "TLI Driver: error reading command" // *Cause: TLI encountered an error while awaiting the expected command // message during connection establishment. // *Action: Contact your customer support representative. 06774, 00000, "TLI Driver: error sending break mode" // *Cause: TLI encountered an error while sending break-mode message during // connection establishment. // *Action: Contact your customer support representative. 06775, 00000, "TLI Driver: error reading break mode" // *Cause: TLI encountered an error while awaiting the expected break-mode // message during connection establishment. // *Action: Contact your customer support representative. 06776, 00000, "TLI Driver: error sending parms" // *Cause: TLI encountered an error while sending the connection parameters // during connection establishment. // *Action: Contact your customer support representative. 06777, 00000, "TLI Driver: error reading parms" // *Cause: TLI encountered an error while awaiting the expected connection // parameter message during connection establishment. // *Action: Contact your customer support representative. 06778, 00000, "TLI Driver: error sending ccode" // *Cause: TLI encountered an error while sending the completion status message // during connection establishment. // *Action: Contact your customer support representative. 06779, 00000, "TLI Driver: error reading ccode" // *Cause: TLI encountered an error while awaiting the expected completion // status message during connection establishment. // *Action: Contact your customer support representative. 06780, 00000, "TLI Driver: recv error code failed" // *Cause: TLI encountered an error while awaiting an expected error message // during connection establishment. // *Action: Contact your customer support representative. 06781, 00000, "TLI Driver: error reading negotation string" // *Cause: TLI encountered an error while awaiting the expected negotiation // message during connection establishment. // *Action: Contact your customer support representative. 06790, 00000, "TLI Driver: poll failed" // *Cause: TLI was unable to poll the communication channel for possible // incoming messages. // *Action: Contact your customer support representative. 06791, 00000, "TLI Driver: poll returned error event" // *Cause: TLI received an unexpected event while polling the communication // channel for possible incoming messages. // *Action: Contact your customer support representative. 06792, 00000, "TLI Driver: server cannot exec oracle" // *Cause: The remote TLI server was unable to start an ORACLE process on // behalf of the client. // *Action: Note the operating system error message or number and contact // your system adminstrator. The permissions on the remote ORACLE // program may be set incorrectly. 06793, 00000, "TLI Driver: server cannot create new process" // *Cause: The remote TLI server was unable to start an ORACLE process on // behalf of the client. // *Action: Note the operating system error message or number and contact // your system adminstrator. The remote host may be unable to create // any new processes due to a full process table. 06794, 00000, "TLI Driver: shadow process could not retrieve protocol info" // *Cause: The ORACLE process either failed to allocate memory to store // the protocol information record, or the protocol rejected the // request for some unknown reason. // *Action: Contact your customer support representative. 06800, 00000, "TLI Driver: SQL*Net SPX client went away during reconnect" // *Cause: The client process was aborted by the system or the user, and // was unable to complete the connection establishment with the // server listener process. // *Action: Determine cause of client exit, and reattempt connection. 06801, 00000, "TLI Driver: listen for SPX server reconnect failed" // *Cause: An unknown event occurred on the client's listening socket. // *Action: Contact your customer support representative. 06802, 00000, "TLI Driver: could not open the /etc/netware/yellowpages file" // *Cause: The /etc/netware/yellowpages file does not exist, or is not // readable by the TLI listener process. // *Action: Insure the file exists and is readable. Make sure that the // 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, "skgfrfms, skgfrnms: read error, unable to read block from database file" // *Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS. // *Action: Check errno. 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: The open() system call returned 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. 07346, 00000, "slnrm: normalized file name is too long" // *Cause: After normalizing the specified file name, the resulting file name // was too long. // *Action: Specify the shorter file 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. 07405, 00000, "sptrap: cannot setup alternate signal stack." // *Cause: The system failed to setup an alternate signal stack. // *Action: Check errno and sercose[0] for the location where it failed. 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 operating system exception occurred which should result in the // creation of a core file. This is an internal error. // *Action: Visit My Oracle Support to access the ORA-07445 Lookup tool // (reference Note 7445.1) for more information regarding the specific // ORA-07445 error encountered. // // An Incident has been created for this error in the Automatic // Diagnostic Repository (ADR). When logging a service request, use // the Incident Packaging Service (IPS) from the Support Workbench // or the ADR Command Interpreter (ADRCI) to automatically package the // relevant trace information (reference My Oracle Support Note 411.1). // // The following information should also be gathered to help determine // the root cause: // - changes leading up to the error // - events or unusual circumstances leading up to the error // - operations attempted prior to the error // - conditions of the operating system and databases at the time // of the error // // Note: The cause of this message may manifest itself as different // errors at different times. Be aware of the history of errors that // occurred before this internal error. 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. 07457, 00000, "cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE" // *Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN // parameter, however this failed because the current // RESOURCE_MANAGER_PLAN has the FORCE prefix. // *Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter. 07458, 00000, "cannot set the RESOURCE_MANAGER_PLAN parameter" // *Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN // parameter, however, this failed because the database was // quiesced. // *Action: Unquiesce the database. 07459, 00000, "cannot restore the RESOURCE_MANAGER_PLAN parameter" // *Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN // parameter to the value before it was internally set. This // failed because the current plan was set by the user and therefore // did not need to be restored. // *Action: No action needed. 07460, 00000, "cannot set the RESOURCE_MANAGER_PLAN parameter" // *Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN // parameter, however, this failed because the current // RESOURCE_MANAGER_PLAN has the FORCE prefix. // *Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter. 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: 1. The trace file could not be created for writing. // 2. The trace file is a symbolic link. // *Action: 1. Check if the dump directory exists and whether it is writable. // 2. Remove the symbolic link. 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 Support Services, 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, "Deprecated" // *Document: NO // *Cause: This bug has been deprecated. Do not use it. // *Action: N/A 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 08007, 00000, "Further changes to this block by this transaction not allowed" // *Cause: Max locks have been reached for this transaction in this block // *Action: Commit changes 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 file %s: (root %s, node %s) blocks (%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, file %s, block %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, or a prior incomplete recovery restored the database to // a point in time during the deletion of the object. // *Action: Delete the object if this is the result of an incomplete // recovery. 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, "cannot create journal table %s.%s" // *Cause: The online index builder could not create its journal table // *Action: Rename the conflicting table or rerun the SQL statement. There // * may be a concurrent online index rebuild on the same object. // *Action: rename your table in conflict or rerun the SQL statement // * there may be a concurrent online index rebuild on the same object. 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 08118, 00000, "Deferred FK constraints cannot be enforced, index too big (%s)" // *Cause: Deferred Foreign Key constraints cannot be enforced due to the // index key being too big and built on a non-default DB_BLOCK_SIZE. // *Action: First try to drop the Foreign Key and then the primary key. 08119, 00000, "The new initrans will make the index too big" // *Cause: Specifying the initrans need additional space to hold the index // key which might make the index too big // *Action: Try giving a smaller initrans value 08120, 00000, "Need to create SYS.IND_ONLINE$ table in order to (re)build index" // *Cause: Alter index Build/Rebuild online require existing of // SYS.IND_ONLINE$ table. // *Action: User/DBA needs to create sys.ind_online$ before alter the index // /rdbms/admin/catcio.sql contains script to create ind_online$. 08121, 00000, "Number of indexes need to be maintained offline exceeds limit for DML" // *Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes // for each DML statement // *Action: Make sure the index maintainance is online. // If indexes need to be maintained offline, drop some indexes. 08122, 00000, "Online (re)build of index rolled back due to DML conflict" // *Cause: The online (re)build journal is inconsistent with ongoing DML and // cannot be used successfully to complete the online index (re)build. // *Action: Reissue the online (re)build operation, after performing any // cleanup, if needed. / / 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 08187, 00000, "snapshot expression not allowed here" // *Cause: A snapshot expression using AS OF was specified when not allowed. // *Action: Do not use the AS OF clause 08189, 00000, "cannot flashback the table because row movement is not enabled" // *Cause: An attempt was made to perform Flashback Table operation on a table for // which row movement has not been enabled. Because the Flashback Table // does not preserve the rowids, it is necessary that row // movement be enabled on the table. // *Action: Enable row movement on the table 08190, 00000, "restore point %s is from a different incarnation of the database" // *Cause: An attempt was made to perform Flashback Table operation using a // restore point from a different incarnation of the database // *Action: Provide a restore point from the current database incarnation 08191, 00000, "Flashback Table operation is not supported on remote tables" // *Cause: An attempt was made to perform Flashback Table operation on a // remote table. This is not permitted. // *Action: Do not perform a Flashback Table operation on remote tables. 08192, 00000, "Flashback Table operation is not allowed on fixed tables" // *Cause: An attempt was made to perform Flashback Table operation on a // fixed table. This is not permitted. // *Action: Do not perform a Flashback Table operation on fixed tables. 08193, 00000, "Flashback Table operation is not allowed on temporary tables" // *Cause: An attempt was made to perform Flashback Table operation on // a temporary table. This is not permitted. // *Action: Do not perform a Flashback Table operation on temporary tables. 08194, 00000, "Flashback Table operation is not allowed on materialized views" // *Cause: An attempt was made to perform Flashback Table operation on a // materialized view. This is not permitted. // *Action: Do not perform a Flashback Table operation on materialized views // or snapshot logs. 08195, 00000, "Flashback Table operation is not supported on partitions" // *Cause: An attempt was made to perform Flashback Table operation on a // partition. This is not permitted. // *Action: Do not perform a Flashback Table operation on partitions. 08196, 00000, "Flashback Table operation is not allowed on AQ tables" // *Cause: An attempt was made to perform Flashback Table operation on AQ tables. // This is not permitted. // *Action: Do not perform a Flashback Table operation on AQ tables. 08197, 00000, "Flashback Table operation is not supported on clustered tables" // *Cause: An attempt was made to perform Flashback Table operation on a // clustered table. This is not permitted. // *Action: Do not perform a Flashback Table operation on clustered tables. 08198, 00000, "Flashback Table is not supported on object tables, nested tables" // *Cause: An attempt was made to perform Flashback Table operation on a // object table or a nested table or a table with nested table column. // This is not permitted. // *Action: Do not perform a Flashback Table operation on such tables. 08199, 00000, "Flashback Table operation is not supported on this object" // *Cause: An attempt was made to perform Flashback Table operation on an // object on which the operation is not supported. // *Action: Do not perform a Flashback Table operation on such objects. / 8200 - 8399 Reserved for NCUBE OSD errors / 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 / 08243, 00000, "recursive audit operation attempted" // *Cause: A recursive operation requiring audit was attempted in the // middle of an auditing operation. The most likely reason // is space management operations needed to free up space // in the audit tablespace. // *Action: Check space in the tablespace for SYS.AUD$ and correct the problem. /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. / / 8362 - 8399 Reserved for nCUBE sosd errors (unassigned) / / 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. // *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. / 08469, 00000, "must use the SIGN IS SEPARATE clause in mask options" // *Cause: A signed numeric entry with DISPLAY usage was converted using a // non-defaulted character set and its PICTURE character-string // contains an S. In these circumstances, a SIGN IS SEPARATE clause // must be specified in the mask options. // *Action: Either specify a valid SIGN IS SEPARATE clause in the mask options, // use the defaulted character set, or don't specify an S in the // PICTURE character-string. / 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. // 09276, 00000, "All bequeath database links must be loopback database links" // *Cause: A non-loopback bequeath connect string was supplied for a database // link. // *Action: Please use a connect string with a different transport protocol, // or specify a loopback connect string (one that points to // the instance for the current session) using // "(PROGRAM=/bin/oracle)" and, // optionally, "(ENVS=''ORACLE_SID='')". / // 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. 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 Support Services. 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 Support Services. 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 Services. 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 Services. 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 Services. 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 Services. 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 Services. 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 Services. 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 Services. // 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 Services. 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 Services. 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 Services. // 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 Services. 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 Services. 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 Support Services. 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 Services. 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 Support Services. 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 Support Services. 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 Support Services. 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 Support Services. 09816, 00000, "Unable to set effective privileges" // *Cause: // *Action: This is an internal error. Contact Oracle Support Services. 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 Support Services. 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_FILE_DEST initialization parameter. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact Oracle Support Services. 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 Services. 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 Services. 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 Services. 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, 00000, "sfngat: the input file name is not in the OMF format" // *Cause: The function sfngat() received a filename which is not // an OMF file name. // *Action: Further diagnostic information should be in the error stack. 09859, 00000, "sfngat: the input file name is not in the autobackup OMF format" // *Cause: The function sfngat() received a filename which is not // an autobackup OMF file name. // *Action: Further diagnostic information should be in the error stack. / / 10630-10639 Reserved for Online Segment Shrink / / 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, "falure in translation while expanding ?/dbs/lk for lock file" // *Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for // the database mount lock or the instance startup/shutdown lock. // *Action: Check additional return errors for more information. 09967, 00000, "unable to create or open lock file" // *Cause: Oracle failed, when making an open system call, inorder to acquire // a file lock used by the database mount lock or the instance // startup/shutdown lock. // *Action: Check errno for more information. 09968, 00000, "unable to lock file" // *Cause: The system call for locking a file returned an error when trying // to acquire a database mount lock or the instance startup/shutdown // lock. // *Action: Check errno for more information. 09969, 00000, "unable to close or remove lock file" // *Cause: The close system call or unlink system call returned an error. // *Action: Check errno for more information. 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, "control file debug event, name 'control_file'" // *Document: NO // *Cause: // *Action: 10001, 00000, "control file crash event1" // *Document: NO // *Cause: // *Action: 10002, 00000, "control file crash event2" // *Document: NO // *Cause: // *Action: 10003, 00000, "control file crash event3" // *Document: NO // *Cause: // *Action: 10004, 00000, "block recovery testing - internal error" // *Document: NO // *Cause: // *Action: 10005, 00000, "trace latch operations for debugging" // *Document: NO // *Cause: // *Action: Enable tracing for various latch operations // *Comment: // level 1 - trace latch gets and frees // level 2 - protect/unprotect latch recovery areas // level 4 - trace multiple posts by processes when latch is freed // level 8 - signal error on bad latch waits // 10006, 00000, "block recovery testing - external error" // *Document: NO // *Cause: // *Action: 10007, 00000, "log switch debug crash after new log select, thread %s" // *Document: NO // *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" // *Document: NO // *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" // *Document: NO // *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, "Turn off data/space search cache" // *Cause: // *Action: 10020, 00000, "partial link restored to linked list (KSG)" // *Cause: // *Action: 10021, 00000, "KST event to trace control file header writes and reads" // *Cause: // *Action: Not set by default. 10022, 00000, "trace ktsgsp" // *Cause: // *Action: 10023, 00000, "Create Save Undo Segment" // *Cause: // *Action: 10024, 00000, "Write to Save Undo" // *Cause: // *Action: 10025, 00000, "Simulate block recovery errors" // *Cause: // *Document: NO // *Action: The level is a bitmask that can be used as follows: // 0x0001 -- Corruption on first attempt to get previous block version 10026, 00000, "Apply Save Undo" // *Cause: // *Action: 10027, 00000, "Specify Deadlock Trace Information to be Dumped" // *Cause: // *Action: The level is a bitmask that can be used as follows: // 0x01 - Do NOT produce a processstate (default is to dump this) // 0x02 - Dump a systemstate // 0x04 - Dump short stacks of all processes // 10028, 00000, "Dump trace information during lock / resource latch cleanup" // *Cause: // *Action: The level is a bitmask that can be used as follows: // 0x01 - Dump information during resource cleanup // 0x02 - Dump information during lock cleanup // 10029, 00000, "session logon (KSU)" // *Cause: // *Action: 10030, 00000, "session logoff (KSU)" // *Cause: // *Action: 10031, 00000, "sort debug event (S*)" // *Cause: // *Document: NO // *Action: Set this event only under the supervision of Oracle development. // Trace level is a bitfield. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 Trace sort auto memory management requirements // 0x0002 Dump sort subheaps before freeing or resetting // 0x0004 Trace use of new vs old sort // 0x0008 Reserved for sort IO tracing // 0x0010 Disable storing duplicates in linked list (also disables // part of top n rank optimization) // 10032, 00000, "sort statistics (SOR*)" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development. // Trace level is a bitfield. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x01 Output sort statistics in the trace file at the end of sort. // 0x02 Level 1 plus print more information as the sort progresses. // 0x04 Level 2 plus dump extra information (track IOs). // 10033, 00000, "sort run information (SRD*/SRS*)" // *Cause: // *Action: 10034, 00000, "access path analysis (APA*)" // *Cause: // *Action: 10035, 00000, "Write parse failures to alert log file" // *Cause: 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, "disable result-cache" // *Cause: // *Action: 10041, 00000, "dump undo records skipped" // *Cause: // *Action: 10042, 00000, "file header reads return youngest mirror" // *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, "CBO Enable optimizer trace for recursive statement (RPI)" // *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" // *Document: NO // *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" // *Document: NO // *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" // *Document: NO // *Cause: // *Action: level is file number to fail verification 10067, 00000, "force redo log checksum errors - block number" // *Document: NO // *Cause: // *Action: level is block number to corrupt 10068, 00000, "force redo log checksum errors - file number" // *Document: NO // *Cause: // *Action: level is file number to corrupt 10070, 00000, "force datafile checksum errors - block number" // *Document: NO // *Cause: // *Action: level is block number to corrupt 10071, 00000, "force datafile checksum errors - file number" // *Document: NO // *Cause: // *Action: level is file number to corrupt / 10072 is available. 10073, 00000, "latch cleanup tracing" // *Document: NO // *Cause: // *Action: Enable latch cleanup tracing. // *Comment: // level 1 - PMON cleanup, in-flux latches only // level 2 - PMON cleanup, all latches // level 3 - all cleanup // 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 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" // *Document: NO // *Cause: // *Action: 10088, 00000, "CBO Disable new NOT IN optimization" // *Document: NO // *Cause: // *Action: 10089, 00000, "CBO Disable index sorting" // *Document: NO // *Cause: // *Action: 10090, 00000, "invoke other events before crash recovery" // *Document: NO // *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" // *Document: NO // *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, "DBWR refresh fails on cross instance resize call" // *Document: NO // *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: 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, "CONNECT BY debug event" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development. // Trace level is a bit field. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 Enable use of CONNECT BY cost-based transformation for // queries with subqueries in the START WITH clause // 0x0002 Enable use of CONNECT BY cost-based transformation for // queries with subqueries in the CONNECT BY clause // 0x0004 Do filtering only (print rows produced by filtering stage) // 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 turn off advanced OR-expansion checks" // *Cause: // *Action: 10143, 00000, "CBO turn off hints" // *Cause: // *Action: 10144, 00000, "CBO turn off cost based selection of bji over bsj subquery" // *Cause: // *Action: 10145, 00000, "test auditing network errors" // *Cause: // *Action: 10146, 00000, "enable Oracle TRACE collection" // *Cause: // *Action: // *Comment: This event is obsoleted, and can be reused for some other purpose // although some customer applications which used to rely on // Oracle Trace may still have it enabled by mistake 10147, 00000, "enable join push through UNION view" // *Cause: // *Action: 10149, 00000, "allow the creation of constraints with illegal date constants" // *Cause: // *Action: 10150, 00000, "import exceptions" // *Document: NO // *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. 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 for special handling during instance administration" // *Document: NO // *Cause: // *Action: Turn on this event in a session to mark the session as special // so that it can be either killed or ignored during instance // administration operations such as shutdown normal and standby // role transitions. // // It is provided for the Oracle Enterprise Manager an other similar // tools. // // The level is interpreted as follows // // LEVEL ACTION //--------------------------------------------------------------------------- // 0 Treat this session as a normal session. This clears the // special bits which may have been set by other levels of this // event. // 1 Kill this session during shutdown normal // 2 Ignore this session during database close // 3 Ignore this session during standby role transitions // >= 4 Reserved for future use 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, "Dynamic Sampling time-out error" // *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: 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 control file" // *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 control file multiplexing / factor will signal error for all files. 10210, 00000, "check data block integrity" // *Cause: // *Action: 10212, 00000, "check cluster integrity" // *Cause: // *Action: 10213, 00000, "crash after control file write" // *Cause: // *Action: 10214, 00000, "simulate write errors on control file" // *Cause: // *Action: / A level of 1-9 simulates write errors on physical blocks 1-9. / If level >= 10 every control file write will force an error. 10215, 00000, "simulate read errors on control file" // *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 control file 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, "KSFD block repair test event" // *Cause: // *Action: Each level is dedicated to a particular ksfd client. When this // event is set, clients corresponding to the level simulate block // verification failure. 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" // *Document: NO // *Cause: // *Action: creates a file named 'crash' 10235, 00000, "check memory manager internal structures" // *Cause: // *Action: 10236, 00000, "dump redo on object no. or block type mismatch errors 1410/8103" // *Document: NO // *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, "Testing event used by server I/O ksfd/ksfq module" // *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, "shared IO pool error simulation" // *Cause: // *Action: level specifies number of IOs after which an error will be simulated 10253, 00000, "limit SQL text returned from X$KGLNA[1]" // *Cause: // *Action: level specifies the maximum SQL string length to be returned 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, "shared server debug event" // *Document: NO // *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: 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: 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: 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 control file header corruption" // *Cause: // *Action: If set, will cause control file header verification to fail 10286, 00000, "Simulate control file open error" // *Cause: // *Action: If set, will cause the next control file 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, "Internal sequence tracing event" // *Cause: // *Action: Internal Event - Should not be set unless directed by RDBMS DEV 10291, 00000, "die in tbsdrv to test control file undo" // *Cause: // *Action: If this event is set, error OERI(10291) is signalled when // issueing tablespace commands. The control file undo should be // applied returning the control file to its previous state. 10292, 00000, "hang analysis trace event" // *Document: NO // *Cause: // *Action: Enable validation of hang analysis callbacks // *Comment: The following levels may be combined: // 0x1 - dump errors to trace file through ksdwrf // 0x2 - dump errors to trace file as ORA-600 + 0x1 // 0x4 - check for involuntary events without callbacks 10293, 0000, "trace log switch media recovery checkpoints" // *Document: NO // *Cause: // *Action: Print alert log timestamps for the start and end of each log // switch checkpoint during media recovery. This timing may prove // useful in debugging recovery performance problems. 10294, 00000, "ksrpc tracing" // *Cause: // *Action: If this event is set then ksrpc module generates tracing on each // remote transfer 10295, 00000, "die after file header update durning cf xact" // *Document: NO // *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 control file 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, "shared I/O pool tracing" // *Document: NO // *Cause: // *Action: If this event is set, then kcbi tracing is enabled. Internal use. 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" 10300, 00000, "Distributed transaction tracing" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: This event will trace the history of KTD actions // level: 0 = always / / // *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. 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: 10314, 00000, "Enable extra stats gathering for CR" // *Document: NO // *Cause: // *Action: 10316, 00000, "Events for extensible txn header, non zero ext header size" // *Document: NO // *Cause: // *Action: 10317, 00000, "Events for extensible txn header, zero ext header size" // *Document: NO // *Cause: // *Action: 10318, 00000, "Trace extensible txn header movements" // *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 // / 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. / 10322, 00000, "CBO don't simplify inlist predicates" // *Cause: // *Action: 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 out-of-memory error during first pass of 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. // 10333, 00000, "dump MTTR statistics each time it is updated" // *Document: NO // *Cause: // *Action: dump MTTR statistics in this thread each time it is updated // 10334, 00000, "force FG to wait to be killed during MTTR advisory simulation" // *Document: NO // *Cause: // *Action: for testing only. // 10335, 00000, "trace database open status" // *Document: NO // *Cause: // *Action: for debugging purpose // 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) / 10338, 00000, "CBO don't use inlist iterator with function-based indexes" // *Cause: // *Action: 10339, 00000, "CBO disable DECODE simplification" // *Cause: // *Action: 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, "reserved for simulating object hash reorganization" // *Document: NO // *Cause: // *Action: Set this to trigger obj hash table reorg to simulate large number // of objects per hash buckets. Done by DBWR interrupt action. / 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" // *Document: NO // *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 / 10358, 00000, "Simulate out of PGA memory in cache advisory reset" // *Cause: // *Action: checks that CKPT can set the simulation to OFF // *Comment: only used during testing / 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-10362 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 / 10361, 00000, "check buffer change vector count consistency" // *Document: No // *Cause: internal use only // *Action: invoke buffer change vector count consistency every 5 minutes / 10362, 00000, "simulate a write error to take a file offline" // *Document: No // *Cause: internal use only // *Action: Enables testing of DBWR taking a file offline because of a // write error. The level is the absolute file number of the // file to be taken offline when DBWR attemts to write to it. / 10363, 00000, "Simulate messaging error for fast object reuse/checkpoint" // *Document: No // *Cause: internal use only // *Action: Enables testing of fast object reuse/checkpoint fallback // mechanism due to ksr message publishing issues. / 10364, 00000, "Do not clear GIMH_STC_SHUT_BEGIN state during shutdown" // *Document: No // *Cause: internal use only // *Action: Enables testing of shutdown begin event by not // clearing GIMH_STC_SHUT_BEGIN state before shutdown completes. / / reserve events 10365-10367 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 10366-10367 for KGNFS/KGODM 10366, 00000, "kgnfs tracing" // *Cause: // *Action: If this event is set then kgnfs module generates debug tracing. / 10367, 00000, "kgodm tracing" // *Cause: // *Action: If this event is set then kgodm module generates debug tracing. // / reserve events 10368-10368 for KSE 10368, 00000, "maximum number of internal errors a process will tolerate" // *Cause: // *Action: determines the maximum number of ORA-600s after which a // process will commit suicide. / 10369, 00000, "test SQL monitoring feature" // *Cause: // *Action: crash tests / / reserve events for parallel query option. Available range 10370-10399 / 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 / 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, "enable archive compression loads" // *Cause: // *Action: Enables archive compression // *Comment: Temporary event / 10377, 00000, "force slave allocation" // *Document: No // *Cause: // *Action: Set this event only under the supervision of Oracle development. // *Comment: for testing only--force the allocation of slaves in certain nodes / 10378, 00000, "force hard process/range affinity" // *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 // 0x4000 Force compilation by slave 0 / 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 / 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. / 10409, 00000, "enable granule memset and block invalidation at startup" // *Cause: // *Action: set this event to enable the memset and invalidation // *Comment: This event is created to be the safe valve for // startup speedup transaction / / 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 10412, 00000, "dump the call stack if an error is signaled" // *Document: NO // *Cause: For testing only. // *Action: None. For testing only. Should never be set by customers. / 10413, 00000, "force simulated error for testing purposes" // *Document: NO // *Cause: For testing only. // *Action: None. For testing only. Should never be set by customers. // *Comment: // level 1: ALTER TABLESPACE...READ ONLY before kcftro // level 2: ALTER TABLESPACE...READ ONLY after kcftro // level 3: ALTER TABLESPACE...READ ONLY before kcfrdo, after waiting // level 4: ALTER TABLESPACE...READ ONLY after kcfrdo // level 5: ALTER TABLESPACE...READ ONLY after krcrtro // level 6: ALTER TABLESPACE...READ ONLY after kqrpre to get lock on TS$ // level 7: ALTER TABLESPACE...READ ONLY after kqrpup to update TS$ // level 8: ALTER TABLESPACE...READ ONLY after ktucat to check other tx's // level 9: ALTER TABLESPACE...READ ONLY after ktccrb to commit // level 10: ALTER TABLESPACE...READ ONLY in kcfrdo, before checkpoint // 10414, 00000, "simulated error from event %s level %s" // *Document: NO // *Cause: For testing only. // *Action: None. For testing only. Should never be set by customers. // *Comment: // 10415, 00000, "parallel degree specified is too large, max value allowed %s" // *Document: NO // *Cause: User specified parallel degree is greater than DEG_INST_MAXVAL // *Action: // *Comment: // 10416, 00000, "disable fix for 2736734" // *Document: NO // *Cause: // *Action: Disable the fix for bug 2736734 // 10417, 00000, "limit 1 file per sbtinfo2() validation call" // *Document: NO // *Cause: // *Action: Prevent Oracle from passing multiple file handles to sbtinfo2(), // in case the Media Management Software cannot properly support // calls with multiple file names. 10418, 00000, "disable re-creating tempfile" // *Document: NO // *Cause: // *Action: Prevent Oracle from automatically re-creating tempfile 10419, 00000, "create tempfile without create_scn and time" // *Document: NO // *Cause: For testing only. // *Action: None. For testing only. Should never be set by customers. 10420, 00000, "trace KSO OS-process operations" // *Document: NO // *Cause: // *Action: Trace KSO operations. 10421, 00000, "enable dump from ksbwco if there is no reply" // *Document: NO // *Cause: // *Action: creates an error stack dump if ksbwco does not hear back. 10422, 00000, "KSU debugging" // *Document: NO // *Cause: // *Action: Helps debug KSU issues (see ksu.h). 10423, 00000, "dump the call stack if the specified error is cleared" // *Document: NO // *Cause: If an unknown module is clearing an error that you expected to // be resignalled, you can use this event to aid your debugging. // Whenever that error is cleared the call stack will be dumped to the // trace file. This only works for non-OS Oracle errors. // Usage: event="10423 trace name context forever, level " // Example: // event="10423 trace name context forever, level 28" // Each time ORA-28 is cleared the stack will be dumped. // *Action: Creates a stack dump each time the specified error is cleared. 10424, 00000, "KGE debugging" // *Document: NO // *Cause: // *Action: Helps debug KGE issues (see kge.c). / Events 10425-10450 reserved for global enqueue service tracing and debugging 10425, 00000, "enable global enqueue operations event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue operations. 10426, 00000, "enable ges/gcs reconfiguration event trace" // *Document: NO // *Cause: // *Action: Dump trace for ges/gcs reconfiguration. 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 cached resource" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service cached resource activities. 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 ges/gcs dynamic remastering event trace" // *Document: NO // *Cause: // *Action: Dump trace for ges/gcs dynamic remastering. 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 multiple 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. 10436, 00000, "enable global cache service duplicate ping checking" // *Document: NO // *Cause: // *Action: Enable global cache service duplicate ping checking 10437, 00000, "enable trace of global enqueue service S optimized resources" // *Document: NO // *Cause: // *Action: Dump global cache service S optimized resources 10438, 00000, "force lowest node to be master of all gcs resources" // *Document: NO // *Cause: // *Action: enable affinity locks by forcing lowest node to be master 10439, 00000, "enable tracing of global cache service fusion calls - part 2" // *Document: NO // *Cause: // *Action: enable tracing of global cache service fusion calls - part 2 10440, 00000, "enable global enqueue service inquire resource modes trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service resource inquiry messages. 10441, 00000, "enable diagnosibility daemon (DIAG) trace" // *Document: NO // *Cause: // *Action: Dump traces for DIAG. 10442, 00000, "enable trace of kst for ORA-01555 diagnostics" // *Document: NO // *Cause: // *Action: Dump trace for ORA-01555 diagnostics 10444, 00000, "enable DLM timeout testing" // *Document: NO // *Cause: // *Action: Simulate various scenarios for DLM/CGS timeouts testing 10445, 00000, "enable tracing of LMS priority management" // *Document: NO // *Cause: // *Action: Dump trace for LMS priority management 10449, 00000, "enable trace of kst for undo manageability features diagnostics" // *Document: NO // *Cause: // *Action: Dump trace for undo manageability features diagnostics 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) 10451, 00000, "Force heap segment compression bypassing compatibility checks" // *Cause: // *Action: set this event only under the supervision of Oracle development // 10452, 00000, "Cannot do block media recovery; media recovery session may be in progress" // *Cause: A media recovery, RMAN, or flashback database session may have // been in progress when an attempt was made to perform block media // recovery on the standby database. // *Action: Check for and cancel any conflicting recovery session and perform // block media recovery on the standby database. // 10453, 00000, "Dump compression statistics to trace file" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // 10454, 00000, "Disable column reordering during compression" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // 10455, 00000, "Do Compression Block Checking" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // 10456, 00000, "cannot open standby database; media recovery session may be in progress" // *Cause: A media recovery, RMAN, or flashback database session may have // been in progress on a mounted instance of a standby database // when an attempt was made to open the standby database. // *Action: Check for and cancel any conflicting recovery session and open // the standby database. // 10457, 00000, "cannot close standby database due to active media recovery" // *Cause: A media recovery session was in progress on a standby database // when an attempt was made to close the standby database. // *Action: Cancel the media recovery session and close the standby database. // 10458, 00000, "standby database requires recovery" // *Cause: A standby database was in a state requiring media recovery // when an attempt was made to open the standby database. // *Action: Perform the necessary recovery and open the standby database. // 10459, 00000, "cannot start media recovery on standby database; conflicting state detected" // *Cause: An attempt was made to perform media recovery on a standby // database while another instance was performing recovery on // the standby database, had the standby database open, or a data file // move operation was in progress. // *Action: Close the standby on all other instances, cancel any conflicting // recovery session or data file move operation, and perform manual // recovery. // 10460, 00000, "Perform backward tablescans for consistent read reduction" // *Cause: // *Action: // // Events 10461 - 10489 reserved for recovery, incl debugging and tracing // 10461, 00000, "Simulate control file corruption during write operation" // *Cause: // *Action: If set, will cause control file header verification to fail // 10462, 00000, "enable recovery debug module" // *Cause: // *Action: Set this event to enable recovery debug module. // Recovery debug module does extra sanity checks on redo // generation and dumps interesting information to trace // if certain errors occur. // 10463, 00000, "enable controlfile test" // *Document: NO // *Cause: // *Action: Set this event to enable controlfile sequence number dump // at instance shutdown (level 1), future version controlfile // compatibility test (level 2), or cf backup creation (level 3) // 10464, 00000, "enable incremental checkpoint debug for split brain check" // *Document: NO // *Cause: // *Action: Set this event to enable checkpoint heartbeat tracing // 10465, 00000, "force slave death during parallel crash recovery" // *Document: NO // *Cause: // *Action: // 10466, 00000, "enable HARD check for block write" // *Document: NO // *Cause: // *Action: Set this event to enable HARD check for every block write. // 10467, 00000, "amplify control file record expansion for testing" // *Document: NO // *Cause: // *Action: Set this event to amplify control file record expansion for testing // 10468, 00000, "log writer debug module" // *Document: NO // *Cause: // *Action: Set this event to the appropriate level for log writer debugging. // 10469, 00000, "error creating control file backup, no checkpoint" // *Cause: The control file being backed up did not // contain a valid control file checkpoint. // Therefore the control file could not be backed up, // as such a backup would not be usable later for recovery. // A common cause for this situation is that you executed // CREATE CONTROLFILE, which mounts the database, // but not ALTER DATABASE OPEN, to open the database. // The latter operation generates a valid control file checkpoint. // *Action: Open the database with ALTER DATABASE OPEN ..., // which results in a valid control file checkpoint. // Run the backup operation again. / 10470, 00000, "disable compatibility check for lost write detection" // *Document: NO // *Cause: // *Action: Set this event to run database with lost write detection // enabled in compatibility mode below 11.0. // Level 1: equivalent of "typical" setting // Level 2: equivalent of "full" setting // for the parameter db_lost_write_protect // 10471, 00000, "PQ slave allocation timeout test" // *Document: NO // *Cause: // *Action: Set this event to enable the delay in PQ slave allocation. // If the delay is longer than the preset threshold (currently // 1 minute), parallel recovery should switch to serial recovery. // 10472, 00000, "dump reading log buffer hit ratio histogram to lgwr trace file" // *Document: NO // *Cause: // *Action: Set this event to dump reading log buffer hit rate histogram // to lgwr trace file. // 10473, 00000, "enable BRR tracing" // *Document: NO // *Cause: // *Action: Set this event to enable tracing of Block Read Record generation. // 10474, 00000, "controlfile time tracing" // *Document: NO // *Cause: // *Action: Set this event to enable additional tracing of the time spent // in different controlfile operations. // 10475, 00000, "readable standby debug event" // *Document: NO // *Cause: // *Action: Set this event to enable additional tracing of readable standby. // 10476, 00000, "control file corruption range testing" // *Document: NO // *Cause: // *Action: Set this event to enable testing of control file // corruption ranges. // 10477, 00000, "simulated rollback error" // *Document: NO // *Cause: // *Action: Set this event to simulate a rollback failure. // 10478, 00000, "DBW0 file identification trace event" // *Document: NO // *Cause: // *Action: Set this event to enable DBW0 file identification tracing. // 10479, 00000, "disk sector size test event" // *Document: NO // *Cause: // *Action: Set this event to let OSD return a specified sector size // level 1: OSD returns 512 as the disk sector size // level 2: OSD returns 4096 (emulation) as the disk sector size // level 3: OSD returns 4096 (native) as the disk sector size // 10480, 00000, "Soft asserts for fast detection of datafile storage problems" // *Document: NO // *Cause: // *Action: Set this event to enable soft asserts to fire when a corrupt or // stale block is seen in some datafile mirrors. This event allows // for the proactive detection of datafile storage problems. // 10481, 00000, "Backup data block for data file has an unlogged change" // *Cause: Flashback was enabled for the data file when the backup data block used // for block media recovery had an unlogged change. // *Action: Remove the data file from the flashback set or use a backup block that // does not contain an unlogged change to perform block media recovery. // 10482, 00000, "Automatic block repair cannot repair an offline or read-only data file" // *Cause: Automatic block repair failed when trying to repair an offline or read-only // data file. // *Action: Bring the data file online in read/write mode. // 10483, 00000, "Simulate overly advanced incremental checkpoint" // *Document: NO // *Cause: // *Action: Set this event to advance the incremental checkpoint so that dirty // buffers exist with low RBAs less than that of the checkpoint. This // scenario will be detected and the database will be crashed in a // recoverable state. // // level 1: Generate error when linking buffer // level 2: Generate error when unlinking buffer // 10484, 00000, "Enable test move operation" // *Document: NO // *Cause: // *Action: Enable this event to test datafile move operation // 10485, 00000, "Real-Time Query cannot be enabled while applying migration redo." // *Cause: The Real-Time Query feature was enabled when an attempt was made // to recover through migration redo generated during primary upgrades or // downgrades. // *Action: Close the standby database in order to recover through // migration redo. Reenable the Real-Time Query feature afterwards. 10486, 00000, "Verify data file-related SGA alignment" // *Document: NO // *Cause: // *Action: Enable this event to verify data file-related SGA alignment. 10487, 00000, "Dump redo memory protection information." // *Document: NO // *Cause: // *Action: Enable this event to dump the details about redo memory protection. 10488, 00000, "Dump block headers read for media recovery." // *Document: NO // *Cause: // *Action: Enable this event to dump the block headers read during media // recovery before any redo application. If level is K_BTMAX+1, dump // all block types, otherwise dump only type equal to the event level. 10489, 00000, "Generate future redo for testing" // *Document: NO // *Cause: // *Action: Internal testing only. Level of non-zero generates a future // informational redo change with opcode not known by this release. // / Events 10490 - 10499 reserved for Oracle Storage Manager / 10490, 00000, "Trace OSM misc. 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. // 10491, 00000, "Trace OSM messaging (KFN) 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. // 10492, 00000, "Trace OSM metadata 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. // 10493, 00000, "Return empty define buffers on 1422" // *cause // *action: On error 1422 instead of returning data in define buffers // this mimics action of version 7 and doesn't return data // valid level = 1 // 10494, 00000, "Trace OSM metadata 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. // 10495, 00000, "Trace OSM metadata 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. // 10496, 00000, "Turn off fix for bug 2554178" // *cause // *action: Instead of checking the current schema against the owner of the // db link revert to previous scheme // 10497, 00000, "Trace OSM metadata 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. // 10498, 00000, "Trim blank characters including contol characters" // *Cause: // *Action: // *Comment: Set this event to any non-zero level to trim blank characters // including control characters. // Default behaviour: No control characters are trimmed. // 10499, 00000, "Trace OSM metadata 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. // 10500, 00000, "turn on traces for SMON" // *Document: NO // *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 10502, 00000, "CBO disable the fix for bug 2098120" // *Cause: // *Action: 10503, 00000, "enable user-specified graduated bind lengths" // *Cause: // *Action: 10504, 00000, "CBO disable the fix for bug 2607029" // *Cause: // *Action: 10505, 00000, "CBO enable dynamic sampling dump to table" // *Cause: // *Action: 10506, 00000, "Disable fix for bug 2588217" // *Cause: // *Action: 10507, 00000, "Trace bind equivalence logic" // *Cause: // *Action: 10509, 00000, "Check kghu subheaps at call boundaries" // *Cause: // *Action: // Level: 0x01 Call heap // 0x02 Session heap 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: 10515, 00000, "turn on event to use physical cleanout" // *Cause: // *Action: 10519, 00000, "enable ALTER TYPE RESET support" // *Cause: // *Action: 10520, 00000, "recreate 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 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. 10521, 00000, "CMON connection pool test event" // *Document: NO // *Cause: // *Action: // *Comment: 10522, 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 // default storage method is multiple lines per row, which // improves load and compile performance. No level number // required. 10523, 00000, "force recreate package even if definition is unchanged" // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: Changes behaviour of create or replace package, procedure, // function or type to force recreation of the object even if its new // definition exactly matches the old definition. // No level number required. 10524, 00000, "CMON connection pool trace event" // *Document: NO // *Cause: // *Action: // *Comment: 10525, 00000, "Disable automatic object validation for describe" // *Cause: // *Action: 10543, 00000, "Standby Block Media Recovery (bmr) and split brain testing event" // *Document: NO // *Cause: // *Action: Set this event in order to test the situation where standby bmr // does not have the necessary redo to recover a block or the situation // where a split brain occurs during instance/crash recovery. 10544, 00000, "Inject standby autobmr failures" // *Document: NO // *Cause: // *Action: Set this event to inject block failures that will trigger standby autobmr. 10545, 00000, "Print standby autobmr messages in alert log" // *Document: NO // *Cause: // *Action: Set this event to print standby autobmr messages in alert log. 10546, 00000, "Cannot perform block media recovery; standby database does not have requisite redo." // *Cause: An attempt was made to perform block media recovery on the standby // database when the necessary redo was not available. // *Action: Wait until the necessary redo is available and reattempt block // media recovery. 10547, 00000, "Cannot perform block media recovery; standby database is not caught up with primary." // *Cause: An attempt was made to perform block media recovery on the standby // database up to scn %s, which is greater than the highest scn of %s // yet applied at the standby. // *Action: Recover the standby up to scn %s and reattempt block media // recovery. 10548, 00000, "Cannot perform block media recovery on a read-only plugged-in datafile." // *Cause: An attempt was made to perform block media recovery on a read-only // plugged-in datafile. // *Action: Convert the plugged-in datafile to read/write and reattempt block // media recovery. 10549, 00000, "Cannot perform block media recovery using a read-only plugged-in backup datafile." // *Cause: An attempt was made to perform block media recovery using a backup // of a read-only plugged-in datafile. // *Action: Reattempt block media recovery using a backup taken after the // plugged-in datafile has been converted to read/write. 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, 00000, "Internal testing for ORA-1551 error handling" // *Cause: // *Action: / / 10552 -10589 reserved for recoverable media/standby recovery / 10553, 00000, "Incompatible UNTIL CONSISTENT clause" // *Cause: RECOVER UNTIL CONSISTENT required database-level recovery with // a backup control file. // *Action: Omit the UNTIL CONSISTENT clause and retry recovery. 10554, 00000, "Media recovery failed to bring datafile %s to a consistent point" // *Cause: Media recovery couldn't recover database to a consistent point due // to the specified datafile. // *Action: Restore a backup of the datafile. 10555, 00000, "Disable redo dumping" // *Cause: // *Action: 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, file offset is %s bytes)" // *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 // control file. // *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. 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: 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 dictionary managed tablespace" // *Cause: Rollback segments cannot be created in dictionary managed // tablespaces when SYSTEM tablespace is locally managed // *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, "specify retry count for online index build cleanup DML lock get" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Change the behaviour of online index build cleanup such that // a failed DML lock get will be reattempted. The number of retries // is dictated by the event level. Note that an event level of 1 // means try forever. Any other event level specifies the number // of attempts, and is internally increased to some minimum default. 10622, 00000, "test/trace online index (re)build" // *Cause: // *Action: set this event only under the supervision of Oracle development 10624, 00000, "Disable UJV invalidation on drop index" // *Cause: // *Action: set this event only under the supervision of Oracle development 10625, 00000, "Turn off redo log dump for the index when OERI 12700" // *Cause: // *Action: set this event only under the supervision of Oracle development 10626, 00000, "specify timeout for online index rebuild to wait for DML" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Change the behaviour of an online index rebuild such that it // will timeout, rather than wait indefinitely for existing DML // to complete. // The event level is the number of seconds the online index rebuild // should wait. Values outside the legal range of 2 to 300 seconds // will be adjusted automatically. 10627, 00000, "Dump the content of the index leaf block" // *Cause: Generate a complete index tree dump, not just an overview // during alter session set events immediate trace name treedump // *Action: This event is recommended only for small table/index since it / dumps very detail information of every keys in the index 10628, 00000, "Turn on sanity check for kdiss index skip scan state" // *Cause: Will do sanity checking on the kdiss state. // *Action: set this event only under the supervision of Oracle development 10629, 00000, "force online index build to backoff and retry DML lock upgrade" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Change the behaviour of an online index rebuild such that it // will backoff and retry a failed DML lock upgrade. // The event level is the number of retries the online index rebuild // should wait. Level 1 means backoff and retry indefinitely. Any // other value less than 32 will be adjusted automatically to be 32. 10630, 00000, "Illegal syntax specified with SHRINK clause" // *Cause: An illegal option was specified with the SHRINK clause // *Action: Verify the SQL Reference Manual and reissue the command 10631, 00000, "SHRINK clause should not be specified for this object" // *Cause: It is incorrect to issue shrink on the object // *Action: Verify the object name and type and reissue the command / 10632, 00000, "Invalid rowid" // *Cause: Segment Highwatermark was overwritten due to shrink and space reused // *Action: Reissue this command. 10633, 00000, "No space found in the segment" // *Cause: Raised while trying to find space during segment shrink // *Action: This error should be trapped internally and treated. The user should // not be able to see the error. 10634, 00000, "Segment is already being shrunk" // *Cause: Only one invocation of shrink can be in progress on a segment at any time // *Action: Reissue the command after the first shrink is over 10635, 00000, "Invalid segment or tablespace type" // *Cause: Cannot shrink the segment because it is not in auto segment space // managed tablespace or it is not a data, index or lob segment. // *Action: Check the tablespace and segment type and reissue the statement 10636, 00000, "ROW MOVEMENT is not enabled" // *Cause: To shrink a data segment, row movement must be enabled. // *Action: Enable row movement and reissue this command. 10637, 00000, "The segment does not exist" // *Cause: Segment to be shrunk has been dropped // *Action: 10638, 00000, "Index status is invalid" // *Cause: Cannot shrink an index which is being rebuilt or disabled // is an unusable state. // *Action: 10639, 00000, "Dump library cache during reparse loops" // *Cause: During this error a library cache dump is necessary , so enable // librarycache dump if event is set. // *Action: Dump a library cache if this event is set when reparse error. // 10640, 00000, "Operation not permitted during SYSTEM tablespace migration" // *Cause: SYSTEM tablespace is being migrated to locally managed format. // *Action: Reissue this command once SYSTEM tablespace migration is over. 10641, 00000, "Cannot find a rollback segment to bind to" // *Cause: SYSTEM tablespace migration requires rollback segment in locally // managed tablespace. // *Action: Drop rollback segments in dictionary managed tablespaces other than // SYSTEM and create rollback segments in locally managed tablespace // and retry migration. 10642, 00000, "Found rollback segments in dictionary managed tablespaces" // *Cause: When SYSTEM tablespace is migrated found rollback segments in // dictionary managed tablespaces. // *Action: Drop the rollback segments in dictionary managed tablespaces and // reissue the command 10643, 00000, "Database should be mounted in restricted mode and Exclusive mode" // *Cause: When SYSTEM tablespace is being migrated database should be mounted // in Exclusive mode and in Restricted mode. // *Action: Reissue this command after mounting the database in right mode. 10644, 00000, "SYSTEM tablespace cannot be default temporary tablespace" // *Cause: When SYSTEM tablespace is being migrated no user should have // SYSTEM as the default temporary tablespace. // *Action: Reissue this command after altering the default temporary // tablespace setting for all users. 10645, 00000, "Recursive Extension in SYSTEM tablespace during migration" // *Cause: When SYSTEM tablespace is being migrated, dictionary tables tried // to extend recursively. Must be caught and processed internally. // Should not be thrown to the user. // *Action: Report the error as a bug. 10646, 00000, "Too many recursive extensions during SYSTEM tablespace migration" // *Cause: When SYSTEM tablespace is being migrated, dictionary tables tried // to extend recursively more than 1000 times. // *Action: If SYSTEM tablespace is very large, then simply reissue the // tablespace migration command. 10647, 00000, "Tablespace other than SYSTEM, %s, %s not found in read only mode" // *Cause: When SYSTEM tablespace is being migrated, tablespaces other than // the three should be ALTERed to read only. // *Action: Alter the tablespace status to read only and retry migration. 10648, 00000, "Tablespace SYSAUX is not offline" // *Cause: The SYSAUX tablespace // was online while SYSTEM tablespace was being migrated. // *Action: Alter the SYSAUX tablespace status to offline and retry migration. 10649, 00000, "Turn off/trace lob index freelist coalesce" // *Cause: Will turn off or trace lob index freelist coalescing // *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 10652, 00000, "Object has on-commit materialized views" // *Cause: It is illegal to issue shrink on an object with on-commit // materialized views // *Action: 10653, 00000, "Table is in a cluster" // *Cause: It is illegal to shrink a table belonging to a cluster // *Action: 10654, 00000, "Table is of type temporary or external" // *Cause: It is illegal to shrink a temporary table or an external table // *Action: 10655, 00000, "Segment can be shrunk" // *Cause: Error message returned when called in probe mode by OEM // *Action: 10656, 00000, "Table is in unusable state due to incomplete operation" // *Cause: ALTER TABLE SHRINK operation was tried on the table which is in // unusable state because of previously failed/incomplete operation. // *Action: If the previous operation was // - DROP COLUMN, resubmit DROP COLUMN CONTINUE // - DROP TABLE, resubmit DROP TABLE
PURGE 10657, 00000, "Lob column to be shrunk does not exist" // *Cause: Shrink was issued on a lob segment that did not exist // *Action: 10658, 00000, "Lob column to be shrunk is marked unused" // *Cause: Shrink was issued on a lob segment that is marked as unused // *Action: 10659, 00000, "Segment being shrunk is not a lob" // *Cause: Shrink was issued on a segment that should be a first class lob // or other data type stored in lob // *Action: 10660, 00000, "Segment is a shared lob segment" // *Cause: Shrink was issued on a segment that was being shared by multiple // lob columns // *Action: 10661, 00000, "Invalid option specified" // *Cause: Check option can be specified for one segment only // *Action: 10662, 00000, "Segment has long columns" // *Cause: Shrink was issued on a segment with long columns. This is not // supported. // *Action: 10663, 00000, "Object has rowid based materialized views" // *Cause: Shrink was issued on an object with rowid based materialized // views. // *Action: Drop the rowid based materialized views and issue shrink on the // object 10664, 00000, "Table has bitmap join indexes" // *Cause: SHRINK was issued on a table with bitmap join indexes. // *Action: Drop bitmap join indexes and reissue SHRINK on the object. 10665, 00000, "Inject Evil Literals" // *Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all // literals to be replaced by 2000 letter 'A's. A value of 1 does // not corrupt anything. // *Action: never set this event 10666, 00000, "Do not get database enqueue name" // *Cause: // *Action: 10667, 00000, "Cause sppst to check for valid process ids" // *Cause: // *Action: 10668, 00000, "Inject Evil Identifiers" // *Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all // identifiers to be replaced by a maximum amount of x's. It is // common for an identifier to be parsed once with a max of 30 bytes, // then reparsed later with a max of 4000, so it may not be possible // to inject such an identifier without the aid of this event. A // value of 1 causes no identifiers to be corrupted. // *Action: never set this event 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, "Application continuity debugging was not enabled." // *Cause: Application continuity debugging was not enabled. // *Action: Enable application continuity debugging. // Level: 0x0001: Transaction intention debugging 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 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 trace information from the RAC buffer cache" // *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. 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: / 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: / 10724, 00000, "trace cross-instance broadcast" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables tracing of cross-instance broadcast (KSXR) / 10725, 00000, "bitmap index version control" // *Cause: // *Action: Set this event only under the supervision of Oracle development. // The trace level is a bitfield, so use it as you would a flag. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 For bitmap indexes with version 0, DML on these bitmap // indexes will be same as with 9i releases (that is, it // simulates the bitmap index DML of previous releases). / 10726, 00000, "frequent itemset counting" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables tracing of internal execution of frequent itemset // counting / 10727, 00000, "introduce failure events in IPC" // *Document: NO // *Cause: // *Action: Internal testing only. // *Comment: / / 10730 - 10800 general debugging events / 10730, 00000, "trace row level security policy predicates" // *Document: NO // *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 / 10732, 00000, "honor pctfree during insert into AQ IOTs" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: If set, then we will honor pctfree, during SQL INSERTs and direct // kdiins0 calls from AQ, for IOTs that are used as AQ queue tables. / 10733, 00000, "test transient-IOT metadata during PMO cleanup" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: causes an internal error to be raised if inconsistent metadata // is detected during cleanup of transient-IOTs which were left // behind by failed Partition Maintenance Operations. Enable this // event only during testing. / 10734, 00000, "reroute external procedures" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: execute external procedures using plsql / 10735, 00000, "debug ksws operations" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Causes debug trace to be dumped for ksws routines / 10736, 00000, "buffer cache pin history dump" // *Cause: // *Action: Set this event only under the supervision of Oracle development. // Trace level is a bitfield. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 Force redo dump during buffer pin history dump // 0x0002 Disable redo dump during buffer pin history dump // 0x0004 Print diagnostic text for the redo dump // / 10737, 00000, "test block checking" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development. // *Comment: Internal testing event for block checking. / 10738, 00000, "internal block testing" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development. / 10739, 00000, "debug WLM (kywm) operations" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Causes debug trace to be dumped for kywm routines / 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. / 10751, 00000, "override for remote row source maximum buffer size" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: To change the default value of 256000. / 10752, 00000, "override for the Exponential Moving Average factor" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: To change the default value of 50%. / 10753, 00000, "enforce deterministic behaviour for prefetching row source" // *Cause: // *Action: set this event only under the supervision of Oracle development. // *Comment: prefetch will disregard buffer cache state and be deterministic // based on level set // Trace level is a bitfield. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 Always enable prefetching // 0x0002 Always disable prefetching // 0x0004 Print diagnostic text for each of the above levels, ie // use level 5 to trace enabling and level 6 to trace disabling. // / 10780 - 10785 Reserved for LogMiner 10780, 00000, "LogMiner API trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst tracing of logminer internal api / 10781, 00000, "LogMiner reader trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst tracing of logminer reader process / 10782, 00000, "LogMiner preparer trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst tracing of logminer preparer process / 10783, 00000, "LogMiner builder trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst tracing of logminer builder process / 10784, 00000, "LogMiner dictionary trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst tracing of logminer dictionary / 10785, 00000, "LogMiner trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development / / 10786 - 10788 Reserved for ks* 10786, 00000, "call push/pop (KSU)" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables tracing of call push/pop operations / 10787, 00000, "trace intra-instance broadcast" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables tracing of intra-instance broadcast (KSR) / 10788, 00000, "trace call stacks" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables tracing of call stack info / / 10789 - 10790 Reserved for LogMiner 10789, 00000, "LogMiner test event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: changes logminer behavior for testing / 10790, 00000, "LogMiner trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development / / 10791 - 10799 Reserved for Logical Standby 10791, 00000, "Logical Standby swithover/failover trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst trancing of switchover and failover in logical / 10792, 00000, "Logical Standby XDAT trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables kst trancing os XDAT usage / 10793, 00000, "Logical Standby trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development / 10794, 00000, "Logical Standby trace event" // *Document: NO // *Cause: // *Action: set this event only under the supervision of Oracle development / 10795, 00000, "VKTM Process trace event" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle Support Services. // *Comment: enable ksd/kst tracing for VKTM process / 10796, 00000, "Elevate Scheduler Priority trace event" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: enable ksd tracing for elevate/revert process scheduler priority / 10797, 00000, "Logical Standby Test Event" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development. // *Comment: changes logical standby behavior for testing / 10800, 00000, "disable Smart Disk scan" // *Document: NO // *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: 10808, 00000, "Enable assert when waiting without a reason" // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: This event will catch clients that call kslwait without providing // any wait reason (see bug 1743159). 10809, 00000, "Trace state object allocate / free history" // *Document: NO // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: This event will trace the history of KSS allocations / deletions. // level: 0 = disabled, 1 = cleanup only, 2 = always / / / 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. / / 10826 - 10829 Reserved for upgrade/downgrade / 10826, 00000, "enable upgrade/downgrade error message trace" // *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. 10827, 00000, "enable upgrade/downgrade diagnostics" // *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. 10828, 00000, "memory allocator error" // *Cause: Error in the memory allocator // *Action: Check the trace files and other relevant output / / 10830 - 10838 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 / 10832, 00000, "Trace approximate NDV row source" // *Cause: // *Action: set this event only under the supervision of Oracle development. // trace level is a bitfield // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 trace / 10839, 00000, "trace / debug caching module (qesca.c)" // *Cause: // *Document: NO // *Action: Set this event only under the supervision of Oracle Development. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 trace / debug caching // 0x0002 dump probe / retrieve / insert cache values / 10840, 00000, "trace / debug pl/sql caching module (kkxmInitCache)" // *Cause: // *Document: NO // *Action: Set this event only under the supervision of Oracle Development. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 trace / debug pl/sql caching / / 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 10842, 00000, "Event for OCI Tracing and Statistics Info" // *Cause: This event is meant for tracing OCI Calls and getting statistics // *Action: This event sets tracing OCI Calls and gets statistics info 10843, 00000, "Event for client result cache tracing" // *Document: NO // *Cause: This is an internal event. // *Action: N/A 10844, 00000, "turn on Native Net IPC debugging (skgxp)" // *Cause: // *Action: Enables debugging code for Native Net IPC (skgxp) 10845, 00000, "Enable Director tracing" // *Cause: N/A // *Action: Enable tracing of director/workload manager packages / 10846, 00000, "Enable Director Single Node Testing" // *Document: NO // *Cause: N/A // *Action: Enable Single Node Testing / 10847, 00000, "OCI dump action is being invoked for internal error ORA-%s" // *Document: NO // *Cause: An internal error was encountered or EVENT_10842 was set to // level 8 or higher which dumped the OCI process state, current // state and the stack trace. // *Action: Disable EVENT_10842. If disabled, contact Oracle Support for the // internal error. / 10848, 00000, "OCI Non Blocking not supported with %s" // *Cause: Attempt made to set connection as non-blocking with another // feature that does not support non-blocking. // *Action: Use blocking connection. / 10849, 00000, "Internal OCI event number" // *Cause: N/A // *Action: Set this event only under the supervision of Oracle Support // or Development. This event enable compatible behavior with // sending describe information when a cursor rebuilt. / / / 10850 - 10869 Reserved for AQ / 10850, 00000, "Enable time manager tracing" // *Cause: // *Action: 10851, 00000, "Allow Drop command to drop queue tables" // *Document: NO // *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 tracing for Enqueue Dequeue Operations" // *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. 10854, 00000, "Sets poll count used for AQ listen code under RAC" // *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. 10863, 00000, "Control behavior of buffered background operations" // *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. 10864, 00000, "event to enable AQ dedicated propagation" // *Document: NO // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, ONE JOB QUEUE // PROCESS WILL PROPAGATE FOR ONLY ONE PROPAGATION SCHEDULE 10865, 00000, "Control tracing of notification operations" // *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. 10866, 00000, "event to order dequeue by condition" // *Document: NO // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, THE DEQUEUE // ORDER THE MESSAGES BASED ON CONDITION. // 10867, 00000, "event to turn off authentication for emon to oci client connections" // *Document: NO // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, THERE IS NO // MUTUAL AUTHENTICATION BETWEEN EMON AND OCI CLIENTS. // 10868, 00000, "event to enable interop patch for AQ enqueue options" // *Document: NO // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, AQ DOES NOT // USE ENQUEUE OPTIONS FOR PROPAGATION. // / / 10870 - 10879 Reserved for recovery layer / 10870, 00000, "Disable multi-instance standby role transition" // *Document: No // *Cause: // *Action: For testing purposes 10871, 00000, "dump file open/close timestamp during media recovery" // *Document: No // *Cause: // *Action: For dumping purpose. / 10872, 00000, "Flashback Database fault insertion event #%s." // *Document: NO // *Cause: Causes faults to be inserted into Flashback Database code. // This should only be enabled for internal testing. // *Action: Level 1 - Die after restoring database, before shrinking // fuzziness. // Level 2 - Die after rstoring database and after shrinking // fuzziness. // Level 3 - Die after restoring control file. // Level 4 - Die after set cf checkpoint during an undo of a cf change // Level 5 - Die after restoring cf, before setting cf checkpoint // Level 6 - Force a block checksum error on a flashback log block // Level 7 - Force a file creation error during fb recovery // Level 8 - Force an error after fb recovery file recreation // Level 9 - Force and error during open resetlogs (after flashback) // 10873, 00000, "file %s needs to be either taken out of backup mode or media recovered" // *Cause: An attempt was made to open a database after an instance failure or // SHUTDOWN ABORT interrupted an online backup. // *Action: If the indicated file is not a restored backup, then issue the // ALTER DATABASE END BACKUP command and open the database. If the // file is a restored online backup, then apply media recovery to // it and open the database. 10874, 00000, "Change max logfiles in hashtable in krfbVerifyRedoAvailable" // *Document: No // *Cause: // *Action: For testing purposes // 10875, 00000, "Require instance bounce after switchover to primary" // *Document: No // *Cause: // *Action: For testing purposes // / 10876, 00000, "IDR Test event" // *Document: No // *Cause: // *Action: Level 1 - x$ir_working_repair_set returns manual options. // Should only be used when testing IR framework. // 2 - force a failure revalidation timeout. // 3 - force a failure in getAdviseID. // 4-7 - simulate ADR timeout. // 8 - simulate ADR lock busy error // 9 - simulate OMF template name for logfile members // / 10877, 00000, "error signaled in parallel recovery slave %s" // *Cause: A parallel recovery logmerger reached an exception condition. // *Action: Check the following error message for the cause, and consult // your error manual for the appropriate action. // / 10878, 00000, "parallel recovery slave died unexpectedly" // *Cause: A parallel recovery slave died unexpectedly, PMON cleaning // up the process. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact Oracle Support Services. // See trace file for more details. / 10879, 00000, "error signaled in parallel recovery slave %s" // *Cause: A parallel recovery slave reached an exception condition. // *Action: Check the following error message for the cause, and consult // your error manual for the appropriate action. // / / 10880 - 10882 Reserved for Java Virtual Machine / 10880, 00000, "trace Java VM execution" // *Document: NO // *Cause // *Action // / 10885, 00000, "Switchover test event" // *Document: NO // *Cause: // *Action: 10890, 00000, "ADG test event" // *Document: NO // *Cause: // *Action: / 10891, 00000, "disable column pruning in ANSI join transformation" // *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 Do not attempt to automatically prune away unreferenced // columns during ANSI join transformation when compiling SQL // queries. / 10898, 00000, "LGWR timing event" // *Document: NO // *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 / 10901, 00000, "disable the fix for bug 1230798" // *Cause: // *Action: 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. 10910, 00000, "inject corner case events into the RAC buffer cache" // *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. 10911, 00000, "Locally managed SYSTEM tablespace bitmaps can be modified only under the supervision of Oracle Support" // *Cause: N/A // *Action: 10912, 00000, "Used to perform admin operations on locally managed SYSTEM tablespace" // *Cause: N/A // *Action: The event should be used only under the supervision of // Oracle Support 10913, 00000, "Create locally managed database if compatible > 920 by default" // *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. 10914, 00000, "invalid TABLESPACE GROUP clause" // *Cause: An invalid option appears for TABLESPACE GROUP clause. // *Action: Specify a valid tablespace group name. 10915, 00000, "TABLESPACE GROUP cannot be specified for this type of tablespace" // *Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP clause was used // while creating/altering a tablespace that is not TEMPORARY. // *Action: Remove the TABLESPACE GROUP clause. / 10916, 00000, "TABLESPACE GROUP already specified" // *Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP option was // specified more than once. // *Action: Remove all but one of the TABLESPACE GROUP specifications. / 10917, 00000, "TABLESPACE GROUP cannot be specified" // *Cause: The tablespace name specified in the command // is actually the name of a tablespace group. // *Action: Please specify an appropriate tablespace name. / 10918, 00000, "TABLESPACE GROUP name cannot be the same as tablespace name" // *Cause: The tablespace group name specified in the command // is the same as the tablespace being CREATEd/ALTERed. // *Action: Please specify an appropriate tablespace group name. / 10919, 00000, "Default temporary tablespace group must have at least one tablespace" // *Cause: An attempt was made to move the only tablespace in the default // database temporary tablespace group to another tablespace group. // *Action: Either change the database default temporary tablespace or // add another tablespace to the group that this tablespace belongs to. / 10920, 00000, "Cannot offline tablespace belonging to default temporary tablespace group" // *Cause: An attempt was made to offline a tablespace in the default // database temporary tablespace group. // *Action: Either change the database default temporary tablespace or // change the tablespace group of this tablespace. / 10921, 00000, "Cannot drop tablespace belonging to default temporary tablespace group" // *Cause: An attempt was made to drop a tablespace in the default // database temporary tablespace group. // *Action: Either change the database default temporary tablespace or // change the tablespace group of this tablespace. / 10922, 00000, "Temporary tablespace group is empty" // *Cause: An attempt was made to allocate a temporary segment in a group, // which now no longer has any members. // *Action: Either add some temporary tablespaces or change the // temporary tablespace for this user. / 10923, 00000, "prints debug information for object space server manageability" // *Cause: // *Action: 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 - 10959 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, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available only in version 11.x. // * Action: Set this event only if necessary - after reading the README for // this release or under supervision of Oracle Support Services. / / 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: // * Action: When set, this event enables tracing of PL/SQL packages. // * Comment: Setting this event could result in some performance slowdown. / / / 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. 10946, 00000, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available only in version 10.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / 10947, 00000, "trace name context forever" // * Cause: When enabled, causes various PL/SQL warnings related debugging // info to be written in a trace file. Useful for debugging varous // Oracle processes. available only in version 10.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. 10948, 00000, "trace name context forever" // * Cause: When enabled, inflate callout argument. // available only in version 10.x. // * Action: internal use only. / / 10949, 00000, "Disable autotune direct path read for full table scan" // *Cause: // *Action: Disable autotune direct path read for serial full table scan. / // /10960 - 10969 Reserved for Advanced Queuing / / 10960, 00000, "AQ tracing event" //*Document: NO // *Cause: // *Action: // / 10970 - 10974 Reserved for Lob Access / / 10970, 00000, "backout event for bug 2133357" // *Cause: 2133357 dynamically sets the varying width flag and character width. // Lob data which is not migrated during migration from single byte to // multibyte charater set will be displayed as special characters. // *Action: To help migrate lob data which was not migrated during migration // by backing out 2133357, so lob data can be selected and moved to // multibyte character set. / 10971, 00000, "prints debugging information for LOBs" // *Document: No // *Cause: // *Action: None / 10972, 00000, "raise a 1551 exception in kdu_array_flush" // *Document: No // *Cause: // *Action: None / 10973, 00000, "backout evet for 2619509" // *Cause: 2619509 catches offsets when not reading/writing on full character // boundary. To facilitate backward compatiblity event is being // introduced. // *Action: To help upgrade/migrate issues which already have corrupt data / 10974, 00000, "Turn on LOB integrity verification" // *Document: No // *Cause: // *Action: None / // / 10975 - 10995 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. 10978, 00000, "general event for materialized view logs" // *Document: NO // *Cause: N/A // *Action: This internal event is used to enable various actions // associated with MV logs. The event level is interpreted // as a bitmap of actions to enable. // // *Comment: Not for general purpose use. // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 use asynchronous purge // 0x0002 use scheduled purge // 0x0004 log commit scn when creating MV logs / 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 / 10990, 00000, "dump spreadsheet info" // *Cause: // *Action: set this event only under the supervision of Oracle Development // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 dump pruned rules during graph analysis // 0x0002 dump level of the rules after ordering in graph analysis // 0x0004 dump spreadsheet filter / 10991, 00000, "event for optimizing the online redefinition instantiation" / *Document: NO // *Cause: N/A // *Action: control the optimizations used during online redefinition. // *Comment: Not for general purpose use. // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 Turn off the index optimization during online redefinition // instantiation. // 0x0002 Turn off the ascending scn optimization during online redefinition // instantiation // 0x0004 Turn on the index and optimistic ascending scn optimization // during online redefinition instantiation. / 10992, 00000, "event to enable dbms_job instead of dbms_scheduler" // *Cause: // *Action: enables dbms_job instead of dbms_scheduler // *Comment: set this event only under the supervision of Oracle Development // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 enable dbms_job instead of dbms_scheduler for MV refresh / / 10993, 00000, "Runtime enable IOQ batching" // *Cause: // *Action: // *Comment: set this event only under the supervision of Oracle Development / / 10994, 00000, "Compiletime enable IOQ batching" // *Cause: // *Action: // *Comment: set this event only under the supervision of Oracle Development / / 10995, 00000, "general event for materialized views" // *Document: NO // *Cause: N/A // *Action: This internal event is used to enable various actions // associated with MVs. The event level is interpreted // as a bitmap of actions to enable. // // *Comment: Not for general purpose use. // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 enable callback-based refresh // 0x0002 invalidate dependents for online redef // 0x0004 allow PCT fast refresh after CONSIDER FRESH // 0x0008 do not use an extended Merge statement during MAV fast refresh / / / 10996 - 10998 Reserved for ks* / 10997, 00000, "another startup/shutdown operation of this instance inprogress" // *Cause: An Oracle Instance startup or shutdown operation failed to procure // the serialization primitive. Another foreground process may have // attempted startup or shutdown operation in parallel. // *Action: Check additional error messages in the alert log and the process // trace file. / 10998, 00000, "event to enable short stack dumps in system state dumps" // *Document: NO // *Cause: N/A // *Action: enables short stack dumps for every active process in a system // state dump // *Comment: set this event only under the supervision of Oracle Support 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. PCT // refresh is also not enabled on the materialized view // *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 or PCT refresh is // possible after a given set of changes, 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. // 12046, 00000, "cannot use trusted constraints for refreshing remote MV" // *Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER MATERIALIZED // VIEW or CREATE MATERIALIZED VIEW of a remote materialized view // *Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW DDL 12047, 00000, "PCT FAST REFRESH cannot be used for materialized view \"%s\".\"%s\"" // *Cause: PCT refresh is either not enabled on this materialized view or not // possible after set of the base table changes since last refresh. // *Action: Use just REFRESH FORCE, which will reinstantiate the entire table // and try to pick the best refresh method on the materialized view // Do explain_mview to look at the cause why PCT refresh is not possible // on this materialized view 12048, 00000, "error encountered while refreshing materialized view \"%s\".\"%s\"" // *Cause: Some problem occurs during refresh of multiple materialized views in // atomic mode. The materialized view whose refresh failed has raised // this error. // *Action: Examine the other messages on the stack to find the refresh problem. // 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, "do not invalidate result cache created during materialized view refresh" // *Cause: Result cache created during materialized view refresh was not invalidated at end. // *Action: Do not set this as an event. // 12080, 00000, "Buffer cache miss for IOQ batching" // *Cause: // *Action: // *Comment: never set this event // 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 // temporary table, an IOT overflow table, a table with fine-grained // access control or row-level security enabled, a CDC change table, // or a table with a CDC change table defined on it. // *Action: Do not attempt to online redefine a table that is not // supported by online redefinition. 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. // 12098, 00000, "cannot comment on the materialized view" // *Cause: An attempt was made to issue a COMMENT ON TABLE statement // on a materialized view. // *Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead. // 12099, 00000, "Don't go into fast table scan (kdst) mode" // *Cause: // *Action: set this event only under the supervision of Oracle development // 12100, 0000, "materialized view log on \"%s\".\"%s\" already has sequence" // *Cause: Materialized view log on the indicated table already has sequence // information. // *Action: No action required. // /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / 12100 - 12299 Reserved for Net8 errors / / / Copyright (c) 1991, 1996, 1997, 2001 by the Oracle Corporation. All rights reserved. / / / $Header: net12150.msg 06-dec-2002.07:12:56 mclose Exp $ / / / NAME / net12150.msg - Oracle Net 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 / cozhang 10/30/02 - Modify msg text 12170 to include STO and RTO. / mclose 10/01/02 - Improve key error messages / cozhang 03/07/02 - Change CONNECT_TIMEOUT to INBOUND_CONNECT_TIMEOUT. / cozhang 12/12/01 - Add message for connect time-out (12170 NIQECTO). / bnanjund 04/16/01 - 1714563_bugfix / 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: Reestablish 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: Reestablish 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: Reestablish connection. / 12154, 00000, "TNS:could not resolve the connect identifier specified" // *Cause: A connection to a database or other service was requested using // a connect identifier, and the connect identifier specified could not // be resolved into a connect descriptor using one of the naming methods // configured. For example, if the type of connect identifier used was a // net service name then the net service name could not be found in a // naming method repository, or the repository could not be // located or reached. // *Action: // - If you are using local naming (TNSNAMES.ORA file): // - Make sure that "TNSNAMES" is listed as one of the values of the // NAMES.DIRECTORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA) // - Verify that a TNSNAMES.ORA file exists and is in the proper // directory and is accessible. // - Check that the net service name used as the connect identifier // exists in the TNSNAMES.ORA file. // - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA // file. Look for unmatched parentheses or stray characters. Errors // in a TNSNAMES.ORA file may make it unusable. // - If you are using directory naming: // - Verify that "LDAP" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Verify that the LDAP directory server is up and that it is // accessible. // - Verify that the net service name or database name used as the // connect identifier is configured in the directory. // - Verify that the default context being used is correct by // specifying a fully qualified net service name or a full LDAP DN // as the connect identifier // - If you are using easy connect naming: // - Verify that "EZCONNECT" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Make sure the host, port and service name specified // are correct. // - Try enclosing the connect identifier in quote marks. // // See the Oracle Net Services Administrators Guide or the Oracle // operating system specific guide for more information on naming. / 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 an administrator to // get the proper permissions or set the TRACE_DIRECTORY_CLIENT // parameter in the net profile (SQLNET.ORA file) to 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:net service name is incorrectly specified" // *Cause: The connect descriptor corresponding to the net service name in // TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is // incorrectly specified. // *Action: If using local naming make sure there are no syntax errors in // the corresponding connect descriptor in the TNSNAMES.ORA file. If using // directory naming check the information provided through the administration // used for directory naming. / 12163, 00000, "TNS:connect descriptor is too long" // *Cause: The connect descriptor corresponding to the net service name // specified as the connect identifier is too long. The maximum length for // a connect descriptor is 512 bytes and this limit has been exceeded. // *Action: Check the net service name's connect descriptor in the local // naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet // Directory). 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 LDAP Directory Server" // *Cause: Cannot contact LDAP directory server to get Oracle Net configuration. // *Action: Verify that the directory server is up and accessible from the network. // Verify that directory access configuration is correct. For more // information see the Oracle Internet Directory Administrators Guide or // the Oracle Net Administrators Guide. / 12169, 00000, "TNS:Net service name given as connect identifier is too long" // *Cause: The net service name you are attempting to resolve is too long. // *Action: The maximum length of a net service name is 255 bytes; this limit // has been exceeded. Use a smaller net service name. If this // is not possible, contact Worldwide Customer Support. / 12170, 00000, "TNS:Connect timeout occurred" // *Cause: The server shut down because connection establishment or // communication with a client failed to complete within the allotted time // interval. This may be a result of network or system delays; or this may // indicate that a malicious client is trying to cause a Denial of Service // attack on the server. // *Action: If the error occurred because of a slow network or system, // reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, // SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. // If a malicious client is suspected, use the address in sqlnet.log to // identify the source and restrict access. Note that logged addresses may // not be reliable as they can be forged (e.g. in TCP/IP). / 12171, 00000, "TNS:could not resolve connect identifier: %s" // *Cause: A connection to a database or other service was requested using // a connect identifier, and the connect identifier specified could not // be resolved into a connect descriptor using one of the naming methods // configured. For example, if the type of connect identifier used was a // net service name then the net service name could not be found in a // naming method repository, or the repository could not be // located or reached. // *Action: // - If you are using local naming (TNSNAMES.ORA file): // - Make sure that "TNSNAMES" is listed as one of the values of the // NAMES.DIRECTORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA) // - Verify that a TNSNAMES.ORA file exists and is in the proper // directory and is accessible. // - Check that the net service name used as the connect identifier // exists in the TNSNAMES.ORA file. // - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA // file. Look for unmatched parentheses or stray characters. Errors // in a TNSNAMES.ORA file may make it unusable. // - If you are using directory naming: // - Verify that "LDAP" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Verify that the LDAP directory server is up and that it is // accessible. // - Verify that the net service name or database name used as the // connect identifier is configured in the directory. // - Verify that the default context being used is correct by // specifying a fully qualified net service name or a full LDAP DN // as the connect identifier // - If you are using easy connect naming: // - Verify that "EZCONNECT" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Make sure the host, port and service name specified // are correct. // - Try enclosing the connect identifier in quote marks. // // See the Oracle Net Services Administrators Guide or the Oracle // operating system specific guide for more information on naming. / / 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 address specified or destination is not listening. // This error can also occur because of underlying network or network // transport problems. // *Action: Verify that the net service name you entered was correct. // Verify that the ADDRESS portion of the connect descriptor which // corresponds to the net service name is correct. Ensure that the // destination process (for example the listener) is running at the // remote node. / 12204, 00000, "TNS:received data refused from an application" // *Cause: The application using 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 Interchanges 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 errors 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 or in the directory. Legal ADDRESS parameter formats may // be found in the Oracle operating system specific documentation or the // Oracle Net Administrator's Guide. Protocols that resolve names at the // transport layer are vulnerable to this error if not properly configured // or names are misspelled. / 12222, 00000, "TNS:no support is available for the protocol indicated" // *Cause: The protocol requested in the ADDRESS portion of the connect // descriptor identified through the net service name is not available. // If the supplied ADDRESS is typographically correct then support for // that protocol is not installed. // *Action: Install support for the protocol or correct typographical error, // as appropriate. Note: if the supplied address was derived from // resolving the net service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA) or in the directory server. / 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 Windows) protocol support is 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 occurred 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 support not loaded" // *Cause: On some platforms (such as Windows) protocol support is 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 / mjgreave 11/08/04 - add 12456 (bug #3998954) / mjgreave 11/08/04 - add 12457 / cchui 07/21/04 - add error message for sessinfo table clean up / pthornto 05/27/03 - add no-doc param for 12499 / shwong 11/14/02 - modify 12473 based on suggestions from errors_us / shwong 11/13/02 - add 12473: procedure disabled when OID is in use / srtata 10/21/02 - add 12472 / vpesati 12/12/01 - fix 12465 add 12471 / 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. 12455, 00000, "internal error in Label Security MMON cleanup task" // *Cause: An internal error occurred in the Label Security MMON cleanup task. // *Action: Contact Oracle Customer Support. 12456, 00000, "label security startup in progress" // *Cause: You attempted to connect to the database before the Oracle // Label Security component was fully initialized. // *Action: Wait until the database is fully open before attempting to // connect. 12457, 00000, "security label exceeded maximum allowable length" // *Cause: An operation attempted to materialize a security label // greater than 4000 bytes in length. // *Action: Consult the Oracle Label Security documentation for // information on how the length of a security label is // calculated. Re-submit the operation once the problem has // been corrected. / 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-12475 / 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 read or 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 read or write access. // *Action: Include read access when authorizing groups or compartments // for write access. 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. 12471, 00000, "Specified compartment or group is not authorized for user" // *Cause: The specified compartment or group is not in user's authorizations // or the user does not have read on compartment or group specified // for write. // *Action: Enter an authorized compartment or group. 12472, 00000, "policy %s is being used" // *Cause: The policy which was being dropped due to event propagation from // OID was applied to some table or schema. // *Action: Drop a policy in OID only if it is not used in any of the // databases using the policy. 12473, 00000, "The procedure is disabled when Label Security is used with OID." // *Cause: Using Label Security with OID disabled this procedure. // *Action: Do not use OID with Label Security if this procedure is required to // function. / 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, "" // *Document: NO // *Cause: // *Action: / Copyright (c) 1991, 1996, 1997, 1998, 1999, 2000, 2001 by the Oracle Corporation. All rights reserved. / / / $Header: network_src/mesg/net12500.msg /main/25 2009/02/26 22:21:05 sreguna Exp $ / / / NAME / net12500.msg - Oracle Net 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 / sreguna 02/23/09 - Add Wallet open failure error message / skramas 08/30/06 - Enhance error 12504 to include default service. / fekhan 05/09/06 - New dhctx related errors. / jpullokk 12/10/02 - Change documentation for 12535 / ppovinec 11/21/02 - 12526-12528 updated / ppovinec 10/08/02 - Add listener messages for RESTRICTED instance / mclose 10/03/02 - Improve messages / cozhang 07/24/02 - Msgs for 12607 NSECONNTIMEOUT, 12608 NSESENDTIMEOUT / & 12609 NSERECVTIMEOUT. Move NSEAPPTIMEOUT to 12606. / vle 07/16/02 - Modify NA error messages / cozhang 03/15/02 - Add msg for lsnr connect timeout (12525 NSGMOCTO). / cozhang 12/11/01 - Add message for app timeout (12604 NSEAPPTIMEOUT). / 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. / / Some error messages are obsolete (no longer used). They have been removed / from this file and their error numbers can at some point distant point / in the future be reused. In order to track there error numbers they are / listed below by what release they were removed for and the date they / were removed. / / Removed beginning with release 10.0.0.X on 10/03/2002: / 12501,12506,12507,12512,12517 / / 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. / 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 SERVICE_NAME in CONNECT_DATA" // *Cause: The listener was not configured with a default service and // SERVICE_NAME was missing from the CONNECT_DATA received by the listener. // *Action: Possible solutions are: // - Configure DEFAULT_SERVICE parameter in LISTENER.ORA with a valid service // name. Reload the listener parameter file using reload []. // This should be done by the LISTENER administrator. // - If using a service name, Check that the connect descriptor corresponding // to the service name in TNSNAMES.ORA has a SERVICE_NAME or SID component // in the CONNECT_DATA. / 12505, 00000, "TNS:listener does not currently know of SID given in connect descriptor" // *Cause: The listener received a request to establish a connection to a // database or other service. The connect descriptor received by the listener // specified a SID for an instance (usually a database instance) that either // has not yet dynamically registered with the listener or has not been // statically configured for the listener. This may be a temporary condition // such as after the listener has started, but before the database instance // has registered with the listener. // *Action: // - Wait a moment and try to connect a second time. // - Check which instances are currently known by the listener by executing: // lsnrctl services // - Check that the SID parameter in the connect descriptor specifies // an instance known by the listener. // - Check for an event in the listener.log file. / 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 Oracle Net. // *Comment: Check the COMMAND given to listener. This error is probably // caused by incompatible Oracle Net or Net8 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. / 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 does not currently know of service requested in connect descriptor" // *Cause: The listener received a request to establish a connection to a // database or other service. The connect descriptor received by the listener // specified a service name for a service (usually a database service) // that either has not yet dynamically registered with the listener or has // not been statically configured for the listener. This may be a temporary // condition such as after the listener has started, but before the database // instance has registered with the listener. // *Action: // - Wait a moment and try to connect a second time. // - Check which services are currently known by the listener by executing: // lsnrctl services // - Check that the SERVICE_NAME parameter in the connect descriptor of the // net service name used specifies a service known by the listener. // - If an easy connect naming connect identifier was used, check that // the service name specified is a service known by the listener. // - Check for an event in the listener.log file. / 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. / 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 does not currently know of instance requested in connect descriptor" // *Cause: The listener received a request to establish a connection to a // database or other service. The connect descriptor received by the listener // specified in addition to the service name an instance name for an instance // (usually a database instance) that either has not yet dynamically registered // with the listener or has not been statically configured for the listener. // This may be a temporary condition such as after the listener has started, // but before the database instance has registered with the listener. // *Action: // - Wait a moment and try to connect a second time. // - Check which instances are currently known by the listener by executing: // lsnrctl services // - Check that the INSTANCE_NAME parameter in the connect descriptor specifies // an instance name known by the listener. // - Check for an event in the listener.log file. / 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. / 12525, 00000, "TNS:listener has not received client's request in time allowed" // *Cause: The listener disconnected the client because the client failed to // provide the necessary connect information within the allowed time interval. // This may be a result of network or system delays; or this may indicate that a // malicious client is trying to cause a Denial of Service attack on the // listener. // *Action: If the error occurred because of a slow network or system, // reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious // client is suspected, use the address in listener.log to identify the // source and restrict access. Turn on tracing for more information. // *Comment: The logged address in listener.ora may not be reliable as it // can be forged at the lower networking layers (e.g. in the case of TCP/IP). / 12526, 00000, "TNS:listener: all appropriate instances are in restricted mode" // *Cause: Database instances supporting the service requested by the client // were in restricted mode. The Listener does not allow connections to // instances in restricted mode. This condition may be temporary, such as // during periods when database administration is performed. // *Action: Attempt the connection again. If error persists, then contact // the database administrator to change the mode of the instance, // if appropriate. / 12527, 00000, "TNS:listener: all instances are in restricted mode or blocking new connections" // *Cause: All appropriate database instances supporting the service requested // by the client reported that they either were in restricted mode or were // blocking the new connections. The Listener does not allow connections to // such instances. This condition may be temporary, such as at instance // startup. // *Action: Attempt the connection again. If error persists, then contact the // database administrator to check the status of the instances. / 12528, 00000, "TNS:listener: all appropriate instances are blocking new connections" // *Cause: All instances supporting the service requested by the client // reported that they were blocking the new connections. This condition may be // temporary, such as at instance startup. // *Action: Attempt the connection again. If error persists, then contact the // administrator to check the status of the instances. / 12529, 00000, "TNS:connect request rejected based on current filtering rules" // *Cause: Connection Manager and its listener were configured with filtering // rules specifying that the connect request be rejected. // *Action: If this connect request should be allowed, then contact the // administrator to modify the filtering rules. / / 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 operation could not be completed within the time out // period. // *Action: Look at the documentation on the secondary errors for possible // remedy. See SQLNET.LOG to find secondary error if not provided explicitly. // Turn on tracing to gather more 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 adapter 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 SQLNET.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' argument 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. / 12575, 00000, "TNS:dhctx busy" // *Cause: The handoff over a dhctx failed as dhctx was already busy // with an ongoing handoff. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12576, 00000, "TNS:handoff not supported for this session" // *Cause: Handoff of a established session was attempted which either had // tcps as its transport or NA options were enabled for this session. // *Action: Check the transport setting as well as NA options. // If error persists, contact Oracle Customer Support. / 12578, 00000, "TNS:wallet open failed" // *Cause: An error was encountered while trying to open the specified wallet. // *Action: For further details, turn on tracing and re-execute the operation. / 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 acknowledgment 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 reissues 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. / / 12606 - 12629 ns secondary errors / 12606, 00000, "TNS: Application timeout occurred" // *Cause: A network session did not reach an application-defined stage // within the allowed time interval. // *Action: This is an error which does not normally appear at the high level. // The action to take is application specific, and is detailed in the // higher level error description. / 12607, 00000, "TNS: Connect timeout occurred" // *Cause: A network session did not reach a predefined connect stage // within the allowed time interval. // *Action: This is an error which does not normally appear at the high level. // The action to take is application specific, and is detailed in the // higher level error description. / 12608, 00000, "TNS: Send timeout occurred" // *Cause: The send or write operation did not complete within the allowed // time interval. // *Action: Check if the peer host is available. Increase the send timeout // value if necessary. / 12609, 00000, "TNS: Receive timeout occurred" // *Cause: The receive or read operation did not complete within the allowed // time interval. // *Action: Check if the peer host is available. Increase the receive timeout // value if necessary. / 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 ongoing // 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. If error 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 Oracle 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. / 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: An Oracle Advanced Security 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: An Oracle Advanced Security 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 // truncated // *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 to connect 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 Oracle Advanced Security authentication service has determined // that the Oracle 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 Oracle Net session layer and should not // normally be visible. // If the error is seen, contact Oracle Worldwide Support. / 12662, 00000, "proxy ticket retrieval failed" // *Cause: The authentication adapter used by Oracle 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 // Oracle 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 Oracle Net connect descriptor // 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 // Oracle 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 Oracle Net connect descriptor // 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 Oracle Net connect descriptor used for // the connection that does support externally-authenticated proxy // connections. // NOTE: Because of a limitation in Oracle 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 Oracle Net connect descriptor used for // the connection that does support externally-authenticated proxy // connections. // NOTE: Because of a limitation in Oracle 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 shared 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 Oracle 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 Oracle Advanced // Security 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 Oracle Advanced Security. // *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 Oracle Advanced Security 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, "Credentials expired." // *Cause: The credentials that are used to authenticate the user for the // requested connection 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 alphanumeric 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 - 12750 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, "Cannot access NLS data files or invalid environment specified" // *Cause: Either an attempt was made to issue an ALTER SESSION command // with an invalid NLS parameter or value; or the environment // variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly // specified, therefore the NLS data files cannot be located. // *Action: Check the syntax of the ALTER SESSION command and the NLS // parameter, correct the syntax and retry the statement, or // specify the correct directory path/values in the environment // variables. 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 control file is unknown. // *Action: 12711, 00000, "this CREATE CONTROLFILE character set is not allowed" // *Cause: It is not allowed to create a control file 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 issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists" // *Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode // when converting to a multibyte character set and must be migrated. // *Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. // The above type 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 12722, 00000, "regular expression internal error" // *Cause: A regular expression internal error occurred. // *Action: This is an internal error. Contact Oracle Support Services. 12723, 00000, "regular expression too complex" // *Cause: The regular expression was too complex and could not be parsed. // *Action: This is an internal error. Contact Oracle Support Services. 12724, 00000, "regular expression corrupt" // *Cause: The regular expression contained an incorrect sequence of metacharacters. // *Action: Ensure the metacharacters are correctly positioned. 12725, 00000, "unmatched parentheses in regular expression" // *Cause: The regular expression did not have balanced parentheses. // *Action: Ensure the parentheses are correctly balanced. 12726, 00000, "unmatched bracket in regular expression" // *Cause: The regular expression did not have balanced brackets. // *Action: Ensure the brackets are correctly balanced. 12727, 00000, "invalid back reference in regular expression" // *Cause: A back references was found before a sub-expression. // *Action: Ensure a valid sub-expression is being referenced. 12728, 00000, "invalid range in regular expression" // *Cause: An invalid range was found in the regular expression. // *Action: Ensure a valid range is being used. 12729, 00000, "invalid character class in regular expression" // *Cause: An unknown character class was found in the regular expression. // *Action: Ensure a valid characters class is being used. 12730, 00000, "invalid equivalence class in regular expression" // *Cause: An unknown equivalence class was found in the regular expression. // *Action: Ensure a valid equivalence class is being used. 12731, 00000, "invalid collation class in regular expression" // *Cause: An unknown collation class was found in the regular expression. // *Action: Ensure a valid collation class is being used. 12732, 00000, "invalid interval value in regular expression" // *Cause: An invalid interval value was found in the regular expression. // *Action: Ensure a valid interval value is being used. 12733, 00000, "regular expression too long" // *Cause: The operation failed because the regular expression it used exceeds // the maximum supported size. // *Action: Use a shorter regular expression. 12734,00000,"Instant Client Light: unsupported client national character set %s" // *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national // character set. Instant Client Light has only minimal character sets. // *Action: Do not use Instant Client Light for this character set 12735, 00000, "Instant Client Light: unsupported client character set %s" // *Cause: The character set specified is not allowed for this operation // or is invalid. Instant Client Light has only minimal character sets. // *Action: Do not use Instant Client Light for this character set 12736,00000,"Instant Client Light: unsupported server national character set %s" // *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national // character set. Instant Client Light has only minimal character sets. // *Action: Do not use Instant Client Light for this character set 12737, 00000, "Instant Client Light: unsupported server character set %s" // *Cause: The character set specified is not allowed for this operation // or is invalid. Instant Client Light has only minimal character sets. // *Action: Do not use Instant Client Light for this character set 12738,00000,"Express Instant Client: unsupported client national character set %s" // *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national // character set. Instant Client has only minimal character sets. // *Action: Do not use Express Instant Client for this character set 12739, 00000, "Express Instant Client: unsupported client character set %s" // *Cause: The character set specified is not allowed for this operation // or is invalid. Express Instant Client has only minimal character // sets. // *Action: Do not use Express Instant Client for this character set 12740,00000,"Express Instant Client: unsupported server national character set %s" // *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national // character set. Instant Client has only minimal character sets. // *Action: Do not use Express Instant Client for this character set 12741, 00000, "Express Instant Client: unsupported server character set %s" // *Cause: The character set specified is not allowed for this operation // or is invalid. Express Instant Client has only minimal character // sets. // *Action: Do not use Express Instant Light for this character set / /============================================================================= / 12751 - 12799 reserved for VOS / / 12760-12780 reserved for ACMS infrastructure / /============================================================================= 12751, 00000, "cpu time or run time policy violation" // *Document: NO // *Cause: A piece of code ran longer than it is supposed to // *Action: If this error persists, contact Oracle Support Services. / 12760,00000, "ACMS tracing event" // *Document: NO // *Cause: // *Action: / 12761,00000, "ACMS debug event" // *Document: NO // *Cause: // *Action: / 12762,00000, "ACMS service status is unknown" // *Document: NO // *Cause: This is an internal status. // *Action: None. / 12763,00000, "ACMS service is disabled" // *Document: NO // *Cause: The ACMS service failed to initialize because of either variances // in the Oracle binaries or internal error. // *Action: Ensure all instances are using the same Oracle binary, and restart // all instances. / 12764,00000, "ACMS service encountered inconsistent state" // *Document: NO // *Cause: An internal error occured. // *Action: Ensure all instances are using the same Oracle binary, and restart // all instances. / 12765,00000, "ACMS operation is pending cleanup" // *Document: NO // *Cause: An attempt of the same operation previously failed and has yet // to be cleaned up by PMON. // *Action: Wait and retry the operation. / 12766,00000, "ACMS failed to acquire share-mode mount lock" // *Document: NO // *Cause: An operation was not permitted because the mount lock could // not be acquired. // *Action: Retry the operation. / 12767,00000, "ACMS memory allocation failure" // *Document: NO // *Cause: An operation was interrupted because an ACMS background // failed to allocate the needed SGA to stage an operation. // *Action: Ensure the instance has sufficient memory resources. / 12768,00000, "ACMS maximum message size exceeded" // *Document: NO // *Cause: An operation failed to start because the requested client data // exceeded the maximum supported size. // *Action: Reduce the size of the data. / 12769,00000, "ACMS message delivery or receipt failure" // *Document: NO // *Cause: An operation was interrupted because a failure occured during // message delivery or reply processing. // *Action: This is expected if instances are leaving the cluster. Retry // the operation. / 12770,00000, "ACMS operation failure with error context" // *Document: NO // *Cause: An operation was interrupted because a failure occured at one // or more sites. // *Action: If supplied, check the status buffer for per-instance error // context. / 12771,00000, "ACMS encountered client callback exception" // *Document: NO // *Cause: The ACMS server encountered an exception while performing the // client callback operation. // *Action: If supplied, check the status buffer for the exception. / 12772,00000, "ACMS encountered client callback failure status" // *Document: NO // *Cause: The ACMS server encountered a failure status from the client // callback operation. // *Action: If supplied, check the status buffer for the return value. / 12773,00000, "ACMS not enabled due to instance not being mounted" // *Document: NO // *Cause: The ACMS server could not execute due to the instance not // being mounted. // *Action: If supplied, check the status buffer to identify the // instance which experienced the error. / / / 12800 - 12898 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 Oracle Support Services. / 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 Oracle Support Services. / 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 Oracle Support Services. / 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 Oracle Support Services. // 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 Oracle Support Services. / 12807, 00000, "process queue could not receive parallel query message" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // contact Oracle Support Services. / 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 Services if error persists. / 12827, 00000, "insufficient parallel query slaves (requested %s, available %s, parallel_min_percent %s)" // *Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than // the minimum number of slaves were acquired // *Action: Either reexecute the query with a 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 // Services 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, "Cursor invalidated during parallel execution" // *Cause: The cursor was invalidated during the parse phase of deferred // parallel processing, e.g. when set operands are parallelized. // *Action: Depends on why the cursor was invalidated. Possible causes include // DDL on a schema object and shared pool being flushed. / 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. 12844, 00000, "cluster reconfiguration in progress" // *Cause: Internal error // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR. 12845, 00000, "failed to receive interinstance parallel execution message" // *Cause: OS or interconnect problem receiving interinstance message // *Action: Check OS specific diagnostics / 12850, 00000, "Could not allocate slaves on all specified instances: %s needed, %s allocated" // *Cause: When executing a query on a gv$ fixed view, one or more // instances failed to allocate a slave to process query. // *Action:Check trace output for instances on which slaves failed to start. // GV$ query can only proceed if slaves can be allocated on all // instances. / 12851, 00000, "PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, %s" // *Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter // to a value less than PARALLEL_MIN_SERVERS. // *Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to // PARALLEL_MIN_SERVERS value specified in the accompanying message // and retry. / 12852, 00000, "PARALLEL_MIN_SERVERS must be less than PROCESSES, %s" // *Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter // to a value higher than PROCESSES. // *Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value // specified in the accompanying message and retry. / 12853, 00000, "insufficient memory for PX buffers: current %sK, max needed %sK" // *Cause: Insufficient SGA memory for PX buffers // *Action: Reconfigure sga to include at least (max - current) bytes of // additional memory / 12854, 00000, "Parallel query is not supported on temporary LOBs" // *Cause: The parallel query statement produced a temporary LOB. // *Action: Turn off parallelism for the query or underlying table / 12855, 00000, "cannot run parallel or insert direct load in a loopback" // *Cause: A loopback was created in the transaction before this operation. // *Action: Do not use loopback when using pdml or insert direct load. 12856, 00000, "cannot run parallel query on a loopback connection" // *Cause: A table or index in a parallel query is referenced via a loopback // connection. // *Action: Do not use loopback connection when running a query in parallel. / 12857 - 12898 unused (parallel query/index creation messages) / / Not really! 12857 through 12871 is used dictionary code!!!! / 12873 - 12898 unused currently for PQ / 12872, 00000, "First slave parse gave different plan" // *Cause: First hard parse on slave given QC-supplied environment and // parameters gave different plan from QC. Try again with outline. // *Action: No external action. Internally used for outline-based reparse. / 12899 - Stole this one for new "value too large" message 12899, 00000, "value too large for column %s (actual: %s, maximum: %s)" // *Cause: An attempt was made to insert or update a column with a value // which is too wide for the width of the destination column. // The name of the column is given, along with the actual width // of the value, and the maximum allowed width of the column. // Note that widths are reported in characters if character length // semantics are in effect for the column, otherwise widths are // reported in bytes. // *Action: Examine the SQL statement for correctness. Check source // and destination column data types. // Either make the destination column wider, or use a subset // of the source column (i.e. use substring). /============================================================================ / 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 12912, 00000, "Dictionary managed tablespace specified as temporary tablespace" // *Cause: attempt to assign a dictionary managed tablespace to be a user's // temporary tablespace // *Action: Assign a locally managed temporary tablespace to be // user's temporary tablespace 12913, 00000, "Cannot create dictionary managed tablespace" // *Cause: Attemp to create dictionary managed tablespace in database // which has system tablespace as locally managed // *Action: Create a locally managed tablespace. 12914, 00000, "Cannot migrate tablespace to dictionary managed type" // *Cause: Attemp to migrate locally managed tablespace to dictionary managed // type when the database has locally managed system tablespace. // *Action: Command cannot be issued. 12915, 00000, "Cannot alter dictionary managed tablespace to read write" // *Cause: Attemp to alter dictionary managed tablespace to read write // in database which has system tablespace as locally managed. // This tablespace can only be dropped. // *Action: Command cannot be issued. 12916, 00000, "cannot shrink permanent or dictionary managed tablespace" // *Cause: An attempt was made to shrink a permanent tablespace or a // dictionary managed tablespace. // *Action: Check the tablespace type and issue the statement only on // locally managed temporary tablespaces. 12917, 00000, "Invalid option specified for default permanent tablespace" // *Cause: // *Action: 12918, 00000, "Invalid tablespace type for default permanent tablespace" // *Cause: The tablespace is either dropped, temporary or undo // *Action: Check the tablespace type and reissue the statement 12919, 00000, "Can not drop the default permanent tablespace" // *Cause: An attemp was made to drop the default permanent tablespace // *Action: Make a different tablespace as the default permanent tablespace // and reissue the drop / / 12920 - 12939 reserved for database/tablespace force logging mode messages / 12920, 00000, "database is already in force logging mode" // *Cause: ALTER DATABASE FORCE LOGGING command failed because the database // is already in force logging mode. // *Action: 12921, 00000, "database is not in force logging mode" // *Cause: ALTER DATABASE NO FORCE LOGGING command failed because the // database is not in force logging mode. // *Action: 12922, 00000, "concurrent ALTER DATABASE [NO] FORCE LOGGING command is running" // *Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER // DATABASE NO FORCE LOGGING command running in the system. // *Action: Contact the database administrator who is responsible for the // concurrent command. 12923, 00000, "tablespace %s is in force logging mode" // *Cause: An attempt to alter the specified tablespace temporary failed // because the tablespace is in force logging mode. // *Action: Put the tablespace out of force logging mode by ALTER TABLESPACE // NO FORCE LOGGING command. 12924, 00000, "tablespace %s is already in force logging mode" // *Cause: An attempt to alter the specified tablespace into force logging // mode failed because it is already in force logging mode. // *Action: 12925, 00000, "tablespace %s is not in force logging mode" // *Cause: An attempt to alter the specified tablespace out of force logging // mode failed because it is not in force logging mode. 12926, 00000, "FORCE LOGGING option already specified" // *Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more // than once. // *Action: Remove all but one of the FORCE LOGGING options. 12927, 00000, "RETENTION option already specified" // *Cause: In CREATE TABLESPACE, the RETENTION option was specified more // than once. // *Action: Remove all but one of the RETENTION options. 12928, 00000, "ENCRYPTION option already specified" // *Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more // than once. // *Action: Remove all but one of the ENCRYPTION options. / / 12940 - 12949 Reserved for server side DBVerify / 12940, 00000, "Not enough space in DBVerify text buffer" // *Cause: DBVerify ran out of text buffer. The error was trapped internally // by the system. DBVerify would return the result in text buffer and // then resume checking. // *Action: None 12941, 00000, "DBVerify exception" // *Cause: DBVerify encountered run-time error. The error signal was trapped // internally by the system. // *Action: None / / 12950 - 12960 Reserved for Space Management 12950, 00000, "SYSTEM tablespace specified as default permanent tablespace" // *Cause: SYSTEM tablespace was specified as the default permanent during // database creation. // *Action: If default permanent tablespace is not specified,then SYSTEM // will implicitly become the default permanent tablespace. // Specify an alternate tablespace or omit the default tablespace // clause and reissue the CREATE DATABASE statement 12951, 00000, "Attempt to change default permanent tablespace to temporary" // *Cause: It is incorrect to alter the default permanent tablespace // of a database to temporary type // *Action: 12952, 00000, "Control space growth in ASSM segment under concurrency" // *Cause: // *Action: Set this event only under the supervision of // Oracle Support Services. 12979, 00000, "general event for SQL execution" // *Document: NO // *Cause: N/A // *Action: This internal event is used to enable various actions // associated with SQL execution. The event level is // interpreted as a bitmap of actions to enable. // // *Comment: Not for general purpose use. // LEVEL ACTION // ---------------------------------------------------------------------------- // 0x0001 evastr() outputs "INVALID NUMBER" when there is an invalid number / / 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. 12998, 00000, "Ignore errors during drop column from atb.c" // *Cause: // *Action: 12999, 00000, "cannot DROP or SET UNUSED a column that has been set unused" // *Cause: An attempt was made to DROP or SET UNUSED a column that has // already been 'set unused'. // *Action: Use the DROP UNUSED COLUMNS option to remove the column. / / 13000 - 13499 (Reserved for Oracle Spatial) / 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 specified 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 Support Services. / 13005, 00000, "recursive HHCODE function error" // *Cause: An error occurred in a recursively called HHCODE function. // *Action: This is an internal error. Contact Oracle Support Services. / 13006, 00000, "the specified cell number is invalid" // *Cause: The cell identifier is either less than 0 or greater than // (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-F a-f] was // detected. // *Action: Verify that all characters in a string are in [0-9] or [A-F a-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 specified 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 specified" // *Cause: An invalid window type was specified. // *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, " specified topology [%s] is invalid" // *Cause: The specified topology did not exist in the database, // or some components of the topology were missing from the database. // *Action: Check the specified topology by executing the // SDO_TOPO.validate_topology function. / 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 Support Services. / 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: Redefine vertex coordinates within specified boundaries. / 13020, 00000, "coordinate is NULL" // *Cause: A vertex coordinate has a NULL value. // *Action: Redefine vertex coordinate to have non-NULL value. / 13021, 00000, "element not continuous" // *Cause: The coordinates defining a geometric element are not connected. // *Action: Redefine coordinates for the geometric element. / 13022, 00000, "polygon crosses itself" // *Cause: The coordinates defining a polygonal geometric element represent crossing segments. // *Action: Redefine 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: Redefine 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: Redefine the coordinates for the polygon. / 13025, 00000, "polygon does not close" // *Cause: The coordinates defining a polygonal geometric element represent an open polygon. // *Action: Redefine 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: Redefine 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 documentation 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 an 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, contact Oracle Support Services. / 13040, 00000, "failed to subdivide tile" // *Cause: This is an internal error. // *Action: Note any accompanying errors and contact Oracle Support Services. / 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_WITH_CONTEXT procedure. If the procedure // does not return any errors, note any errors that accompany ORA-13041 // and contact Oracle Support Services. / 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 documentation. Then retry the operation. / 13043, 00000, "failed to read metadata from the _SDOLAYER table" // *Cause: An error was encountered reading the layer metadata 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 Support Services. / 13044, 00000, "the specified tile size is smaller than the tolerance" // *Cause: The tile size specified for fixed size tessellation // is smaller than the tolerance as specified in the layer metadata. // *Action: See the Oracle Spatial documentation 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 geometric object or specifying a smaller tile size // value than the current one. / 13045, 00000, "invalid compatibility flag" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13046, 00000, "invalid number of arguments " // *Cause: An invalid number of arguments were specified for an // SDO_GEOM function. // *Action: See the Oracle Spatial 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 Support Services. / 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 Support Services. / 13051, 00000, "failed to initialize spatial object" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 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 // Oracle Spatial. // *Action: Check the Oracle Spatial documentation 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 documentation 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 Support Services. / 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. / 13060, 00000, "topology with the name %s already exists" // *Cause: The specified topology name was not unique in the database. // *Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology // name and that the procedure is invoked from the correct schema. / 13061, 00000, "topology with the name %s does not exist" // *Cause: The specified topology did not exist in the database. // *Action: Verify that the current procedure/function call specifies the // correct schema and topology name. / 13062, 00000, "topology IDs do not match in the feature table and the topology" // *Cause: The specified topology ID in the feature table did not match the // topology ID stored in the topology metadata. // *Action: Verify that the specified topology ID matches the topology ID stored // in the topology metadata. / 13063, 00000, "relationship information table is missing data for feature table [%s]" // *Cause: The topology relationship information table (xxx_RELATION$) did not // have the matching partition corresponding to the feature table. // *Action: Make sure the correct topology IDs and names are specified in the // call to register the feature table with the topology. / 13064, 00000, "relationship information table has inconsistent data for feature table [%s]" // *Cause: The topology_id, tg_layer_id values stored in the feature table // did not match the values stored in the topology relationship // information table (xxx_RELATION$). // *Action: Make sure that the correct feature tables are specified in the // call to register the feature table with the topology. / 13065, 00000, "cannot delete a child layer with a parent layer" // *Cause: A call was made to delete a feature layer which has a dependent // layer defined on it. // *Action: Make sure that all dependent feature layers are deleted before // deleting the current feature layer. / 13066, 00000, "wrong feature geometry or element type" // *Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element // type. // *Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY // object. / 13067, 00000, "operator requires both parameters from the same topology" // *Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same // topology. // *Action: Make sure both the parameters to the operator are from the same // topology. If this is not possible, consider using a signature of // the operator that does not use two SDO_TOPO_GEOMETRY parameters. / 13068, 00000, "wrong table or column name in SDO_TOPO_GEOMETRY constructor" // *Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect // parameters for table name and/or column name. // *Action: Fix the parameters in the call and try again. / 13108, 00000, "spatial table %s not found" // *Cause: The specified spatial table does not exist. // *Action: Check the Spatial 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 dictionary. // *Action: Remove the existing table from the Spatial // data dictionary or use a different name. / 13110, 00000, "cannot drop topology with associated topo_geometry tables" // *Cause: The drop_topology procedure was invoked for a topology that has // assocated topo_geometry layers with it. // *Action: Delete the topo_geometry layers from the topology before dropping // the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete // topo_geometry layers from the topology. / 13111, 00000, "cannot add topo_geometry layer [%s] to topology" // *Cause: It was not possible to add the specified topo_geometry layer // to the topology. // *Action: Make sure the topo_geometry layer table exists in the database. / 13112, 00000, "cannot delete topo_geometry layer [%s] from topology" // *Cause: It was not possible to delete the specified topo_geometry layer // from the topology. // *Action: Check USER_SDO_TOPO_METADATA to see if the specified // topo_geometry layer is part of the topology. Only those // topo_geometry layers which are part of the topology can be // deleted from it. / 13113, 00000, "invalid tg_layer_id in sdo_topo_geometry constructor" // *Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor. // *Action: Valid layer_ids are obtained by adding a topo_geometry layer to // the topology. Check USER_SDO_TOPO_METADATA to find out the // layer_id for an existing topo_geometry layer. / 13114, 00000, "[%s]_NODE$ table does not exist" // *Cause: The NODE$ table for the topology did not exist in the database. // *Action: There is a severe corruption of the topology. // Call Oracle Support Services with the error number. / 13115, 00000, "[%s]_EDGE$ table does not exist" // *Cause: The EDGE$ table for the topology did not exist in the database. // *Action: There is a severe corruption of the topology. // Call Oracle Support Services with the error number. / 13116, 00000, "[%s]_FACE$ table does not exist" // *Cause: The FACE$ table for the topology did not exist in the database. // *Action: There is a severe corruption of the topology. // Call Oracle Support Services with the error number. / 13117, 00000, "[%s]_RELATION$ table does not exist" // *Cause: The RELATION$ table for the topology did not exist in the database. // *Action: There is a severe corruption of the topology. // Call Oracle Support Services with the error number. / 13118, 00000, "invalid node_id [%s]" // *Cause: A topology node operation was invoked with an invalid node_id. // *Action: Check the topology node$ table to see if the specified node_id // exists in the topology. / 13119, 00000, "invalid edge_id [%s]" // *Cause: A topology edge operation was invoked with an invalid edge_id. // *Action: Check the topology edge$ table to see if the specified edge_id // exists in the topology. / 13120, 00000, "invalid face_id [%s]" // *Cause: A topology face operation was invoked with an invalid face_id. // *Action: Check the topology face$ table to see if the specified face_id // exists in the topology. / 13121, 00000, "layer type type mismatch with topo_geometry layer type" // *Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the // type specified for the layer. // *Action: Check the USER_SDO_TOPO_METADATA view to see the layer type // for the layer and use it in the constructor. / 13122, 00000, "invalid topo_geometry specified" // *Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was // not valid. // *Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid // topo_geometry object. / 13123, 00000, "invalid name specified" // *Cause: The create_topo operation requires a unique TOPOLOGY name, that // already does not exist in the database. // *Action: Check to see if there is already an entry in the // USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE) // with this topology name. / 13124, 00000, "unable to determine column id for column %s" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 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: Contact Oracle Support Services. / 13127, 00000, "failed to generate target partition" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13128, 00000, "current tiling level exceeds user specified tiling level" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 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 dictionary. / 13135, 00000, "failed to alter spatial table" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13136, 00000, "null common code generated" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13137, 0000, "failed to generate tablespace sequence number" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13138, 00000, "could not determine name of object %s" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13139, 00000, "could not obtain column definition for %s" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13140, 00000, "invalid target type" // *Cause: The specified target type is not valid. // *Action: Substitute a valid target type. Valid target types are TABLE and // 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: Contact Oracle Support Services. / 13145, 00000, "failed to generate range list" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 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: Contact Oracle Support Services. / 13148, 00000, "failed to generate SQL filter" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 13149, 00000, "failed to generate next sequence number for spatial table %s" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 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 remove a record from 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 high water mark must be greater than or equal to zero. // *Action: Make sure that the high water 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: The 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 Support Services. / 13185, 00000, "failed to generate initial HHCODE" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Support Services. / 13186, 00000, "fixed tile size tessellation failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Support Services. / 13187, 00000, "subdivision failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Support Services. / 13188, 00000, "cell decode failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Support Services. / 13189, 00000, "recursive SQL parse failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Support Services. / 13190, 00000, "recursive SQL fetch failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Support Services. / 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 Support Services. / 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 Support Services. / 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 Support Services. / 13194, 00000, "failed to decode supercell" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. / 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 Support Services. / 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 error: %s" // *Cause: Internal error in some Oracle Spatial stored procedure. // *Action: Record the sequence of procedure calls or events that // preceded this error, and contact Oracle Support Services 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 Support Services. / / (13200 - 13499 Reserved for Oracle Spatial 8.1.3 and future use) 13200, 00000, "internal error [%s] in spatial indexing." // *Cause: This is an internal error. // Action: Contact Oracle Support Services 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 Oracle Spatial documentation 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 view" // *Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA // view. // *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 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 Oracle Support Services with the 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: Contact Oracle Support Services with the exact error text. / 13209, 00000, "internal error while reading SDO_INDEX_METADATA table" // *Cause: An internal error was encountered while trying to read the // SDO_INDEX_METADATA table. // *Action: Contact Oracle Support Services. 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_WITH_CONTEXT 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_WITH_CONTEXT procedure. If the procedure // does not return any errors, note any accompanying errors and contact // Oracle Support Services. / 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, contact Oracle Support Services. / 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, contact Oracle Support Services. / 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 Oracle Spatial documentation for the number, syntax, // and semantics of expected parameters for the spatial ALTER INDEX // statement. / 13218, 00000, "max number of supported index tables reached for [%s] index" // *Cause: An add_index parameter was 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 statement 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. Validate the geometry using the // VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure // does not return any errors, note any errors that accompany // ORA-13220 and contact Oracle Support Services. / 13221, 00000, "unknown geometry type in the geometry object" // *Cause: The SDO_GTYPE attribute in the geometry object contains // an invalid value // *Action: Redefine the geometric type in the geometry table // using one of the supported SDO_GTYPE values. // See the Oracle Spatial documentation 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" // *Cause: There are duplicate entries for the given table and column // value pair in the USER_SDO_GEOM_METADATA view. // *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 USER_SDO_GEOM_METADATA view. / 13224, 00000, "zero tolerance specified for layer in USER_SDO_GEOM_METADATA" // *Cause: A tolerance of zero or NULL is supplied for a layer in // USER_SDO_GEOM_METADATA view. // *Action: Check the tolerance specified to make sure it is a positive value. / 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. Quadtree indexes are compatible 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 privileges 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. // *Action: Delete the table if it already exists and verify if the current // user has CREATE TABLE privileges and has sufficient space in // the default or specified tablespace. // If that fails to correct the problem, contact Oracle Support Services. / 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 insert operations for the rest of the data. / 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 Support Services. / 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 Support Services with // accompanying error messages. / 13236, 00000, "internal error in R-tree processing: [%s]" // *Cause: An internal error occurred in R-tree processing. // *Action: Contact Oracle Support Services with the 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 the ALTER // SESSION statement, or contact Oracle Support Services 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 the query minimum // bounding rectangle (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 statement does not match that of the data. // *Action: Change the statement to reflect the data dimensionality. / 13243, 00000, "specified operator is not supported for 3- or higher-dimensional R-tree" // *Cause: Currently, an R-tree index with three or more index dimensions can be used // only with the SDO_FILTER operator. // *Action: Use the SDO_FILTER operator, and check the documentation for the querytype // parameter for SDO_FILTER; or contact Oracle Support Services. / 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 Support Services 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 layer name 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 re-create 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 column name 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 // exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer. / 13268, 00000, "error obtaining dimension from USER_SDO_GEOM_METADATA" // *Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified // geometry table. // *Action: Insert an entry for the destination geometry table with // the correct dimension information. / 13269, 00000, "internal error [%s] encountered when processing geometry table" // *Cause: An internal error occurred. // *Action: Contact Oracle Support Services with the exact error message text. / 13270, 00000, "OCI error \n%s" // *Cause: An OCI error occurred 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 the validation function. // *Action: Check the Oracle Spatial documentation for information about the // geometric integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT // 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 was invoked with a window geometry with an SRID // but the layer has no SRID; or the window has no SRID but the // layer has an SRID. // *Action: Make sure that the layer and window both have an SRID or that they // both do not have an SRID. / 13275, 00000, "spatial index creation failure on unsupported type" // *Cause: An attempt was made to create a spatial index create on a column // that is not of type SDO_GEOMETRY. // *Action: A spatial index can only be created on a column of type // SDO_GEOMETRY. Make sure the indexed column is of type SDO_GEOMETRY. / 13276, 00000, "internal error [%s] in coordinate transformation " // *Cause: OCI internal error. // *Action: Contact Oracle Support Services with the exact error message text. / 13278, 00000, "failure to convert SRID to native format" // *Cause: OCI internal error. // *Action: Contact Oracle Support Services 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 the validity of the WKT for table entries, and check if the // requested transformation is valid. / 13283, 00000, "failure to get new geometry object for conversion in place" // *Cause: OCI internal error. // *Action: Contact Oracle Support Services with the exact error message text. / 13284, 00000, "failure to copy geometry object for conversion in place" // *Cause: OCI internal error. // *Action: Contact Oracle Support Services 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: Check the Oracle Spatial documentation for SDO_GTYPE values, and // specify a value whose last digit is 1 or higher. / 13288, 00000, "point coordinate transformation error" // *Cause: An internal error occurred while transforming points. // *Action: Check the accompanying error messages. / 13290, 00000, "the specified unit is not supported" // *Cause: An Oracle Spatial function was called with an unknown UNIT value. // *Action: Check Spatial documentation for the supported units, and call the // 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 the 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: An Oracle Spatial function with a UNIT parameter was 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: An Oracle Spatial function was called with two geometries that have 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 the MDSYS.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: Contact Oracle Support Services with the exact error message text. / 13304, 00000, "failure to insert a transformed geometry object in a table" // *Cause: OCI internal error. // *Action: Contact Oracle Support Services with the exact error message text. / 13330, 00000, "invalid MASK" // *Cause: The MASK passed to the RELATE function is not valid. // *Action: Verify that the mask is not NULL. See the Oracle Spatial documentation // for a list of supported masks. / 13331, 00000,"invalid LRS segment" // *Cause: The given LRS segment was not a valid line string. // *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 the Oracle Spatial // metadata. Currently, the number of dimensions for an LRS segment must // be greater than 2 (x/y or longitude/latitude, plus measure) / 13332, 00000,"invalid LRS point" // *Cause: The specified 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 an additional dimension for measure. / 13333, 00000, "invalid LRS measure" // *Cause: The given measure for linear referencing was out of range. // *Action: Redefine the measure. / 13334, 00000, "LRS segments not connected" // *Cause: The specified geometric segments are 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 geometric segment 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: There is no room for the measure dimension in the given diminfo, or // the specified standard geometry is not a point a line string. // *Action: Check if the diminfo dimensions are less than 3 or if the // geometry type is point or line string. / 13337, 00000, "failure in concatenating LRS polygons" // *Cause: LRS concatenation involving LRS polygons is not supported. // *Action: Check the geometry and element types to make sure the concatenate // 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. // *Action: Check the geometry type to make sure this operation is // called on non-polygon geometries. / 13339, 00000, "LRS polygon clipping across multiple rings" // *Cause: Clipping (dynseg) a polygon across multiple rings is not allowed. // *Action: Polygon clipping is allowed only 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, set the // appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single // point object, remove the extraneous coordinates from its // definition. / 13341, 00000, "a line geometry has fewer than two coordinates" // *Cause: A geometry, specified as being a line, has fewer 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 fewer than three coordinates" // *Cause: A geometry, specified as being an arc, has fewer 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 fewer than four coordinates" // *Cause: A geometry, specified as being a polygon, has fewer 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 fewer than five coordinates" // *Cause: A geometry, specified as being an arcpolygon, has fewer than five // 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 fewer than five coordinates" // *Cause: A geometry, specified as being a compound polygon, has fewer // 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 definition of an arc. An arc is defined using three // non-collinear coordinates. // *Action: Alter the definition of 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 to ensure 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 definition 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 definition 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 an SDO_GEOMETRY definition 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 an SDO_GEOMETRY definition // references an invalid array subscript in SDO_ORDINATE_ARRAY. // *Action: Confirm that the offset is a valid array subscript in // SDO_ORDINATE_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 multiple of // the number of dimensions supplied by the user. // *Action: Confirm that the number of dimensions is consistent with data // representation in SDO_ORDINATE_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 two points: // lower left and upper right. // *Action: Confirm that there are only two points for an extent type. / 13358, 00000, "circle type does not contain 3 points" // *Cause: Circle type should be represented by three distinct points // on the circumference. // *Action: Confirm that there are only three points for a circle type. / 13359, 00000, "extent does not have an area" // *Cause: The two points representing the extent are identical. // *Action: Confirm that the two 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: Check the Oracle Spatial documentation 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: The 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 that they match the dimensions in the SDO_DIM_ARRAY object // for the layer in the USER_SDO_GEOM_METADATA view. / 13365, 00000, "layer SRID does not match geometry SRID" // *Cause: The 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 that the // SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view. / 13366, 00000, "invalid combination of interior exterior rings" // *Cause: In an Oracle 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 an Oracle Spatial geometry, the exterior and/or interior rings are not // oriented correctly. // *Action: Be sure that the exterior rings are oriented counterclockwise and the // interior rings are oriented clockwise. / 13368, 00000, "simple polygon type has more than one exterior ring" // *Cause: In a polygon geometry there is more than one exterior ring. // *Action: Set the type to be multipolygon if more than one exterior ring is // present in the geometry. / 13369, 00000, "invalid value for etype in the 4-digit format" // *Cause: A 4-digit etype for a non-polygon type element is used, or // the orientation is not a valid orientation for interior/exterior // rings of the polygon. // *Action: Correct the geometry definition. / 13370, 00000, "failure in applying 3D LRS functions" // *Cause: Only non-geodetic 3D line string geometries (made of line segments) // are supported for 3D LRS functions. // *Action: Check the geometry and element types and the SRID values. / 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 the dim_info_array. // *Action: Check the geometry's gtype and its position in the 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 an // inconsistency between the geometry's gtype and diminfo. // *Action: Modify (or Prepare) metadata before creating an index on the // SDO_GEOMETRY column. / 13373, 00000, "invalid line segment in geodetic data" // *Cause: A geodetic line segment was not less than half of a great circle. // *Action: Densify the line by adding points. / 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 constraint. // *Action: See the Spatial documentation for of valid keywords // that can be used in defining a layer_gtype constraint. / 13377, 00000, "invalid combination of elements with orientation" // *Cause: An element of the geometry has orientation specified while some // other element has no orientation specified (4-digit etype). // *Action: Make sure all the polygon elements have orientation specified // using the 4-digit etype notation. / 13378, 00000, "invalid index for element to be extracted" // *Cause: An invalid (or out of bounds) index was specified for extracting // an element from a geometry. // *Action: Make sure the parameters to the extract function are in the // valid range for the geometry. / 13379, 00000, "invalid index for sub-element to be extracted" // *Cause: An invalid (or out of bounds) index was specified for extracting // a sub-element from a geometry. // *Action: Make sure the parameters to the extract function are in the // valid range for the geometry. / 13380, 00000, "network not found" // *Cause: The specified network was not found in the network metadata. // *Action: Insert the network information in the USER_SDO_NETWORK_METADATA // view. / 13381, 00000, "table:%s not found in network:%s" // *Cause: The specified table was not found in the network metadata. // *Action: Insert the table information in the USER_SDO_NETWORK_METADATA view. / 13382, 00000, "geometry metadata (table:%s column:%s) not found in spatial network:%s" // *Cause: The specified geometry metadata was not found in the spatial // network metadata. // *Action: Insert the spatial metadata information in the // USER_SDO_NETWORK_METADATA view. / 13383, 00000, "inconsistent network metadata: %s" // *Cause: There was an inconsistency between the network metadata // and the node/link information. // *Action: Check the network metadata and the node/link information. / 13384, 00000, "error in network schema: %s" // *Cause: The network table(s) did not have required column(s) // *Action: Check the network schema. / 13385, 00000, "error in network manager: [%s]" // *Cause: There was an internal error in network manager. // *Action: Contact Oracle Customer Support for more help. / 13386, 00000, "commit/rollback operation error: [%s]" // *Cause: The index-level changes were not fully incorporated as part of // the commit or rollback operation. // *Action: Correct the specified error and use the following statement: // ALTER INDEX PARAMETERS ('index_status=synchronize'); / 13387, 00000, "sdo_batch_size for array inserts should be in the range [%d,%d]" // *Cause: The specified value for sdo_batch_size was too high or too low. // *Action: Change the value to be in the specified range. / 13388, 00000, "invalid value for dst_spec parameter" // *Cause: The dst_spec parameter was specified in the wrong format. // *Action: Check the documentation for this parameter. / 13389, 00000, "unable to compute buffers or intersections in analysis function" // *Cause: There was an internal error in computing the buffers or // intersections in the specified spatial analysis function. // *Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA // view before invoking the spatial analysis function. / 13390, 00000, "error in spatial analysis and mining function: [%s]" // *Cause: There was an internal error in the specified analysis function. // *Action: Contact Oracle Customer Support for more help. / / 13391 - 13499 for all GeoRaster errors / / 13391-13399 GeoRaster management errors / 13400-13429 general pl/sql errors -- schema and user errors / 13430-13479 all XML errors and other data related errors -- data errors / 13480-13490 external format related errors -- external data errors / 13491-13498 GeoRaster internal errors -- code errors and rdbms errors / 13391, 00000, "%s" // *Cause: An attempt was made to violate GeoRaster management restrictions. // *Action: Check the documentation for more detailed information. / 13393, 00000, "null or invalid %s parameter" // *Cause: The operation failed because the input parameter was null or // invalid. // *Action: Correct the parameter and try again. / 13400, 00000, "duplicate entry for %s in USER_SDO_GEOR_SYSDATA view" // *Cause: The current operation caused a duplicate RASTER_DATA_TABLE and // RASTER_ID combination to be inserted into the // USER_SDO_GEOR_SYSDATA view. // *Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID combination to // be inserted into the USER_SDO_GEOR_SYSDATA view is unique. / 13401, 00000, "duplicate entry for %s in USER_SDO_GEOR_SYSDATA view" // *Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same // information in two or more rows in the USER_SDO_GEOR_SYSDATA view. // *Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the // USER_SDO_GEOR_SYSDATA view contain the correct information, and // that the value pair is unique for each row. / 13402, 00000, "the rasterType is null or not supported" // *Cause: The specified rasterType was null or not supported. // *Action: Check the documentation for the rasterType number and/or // formats supported by GeoRaster. / 13403, 00000, "invalid rasterDataTable specification: %s" // *Cause: Each GeoRaster object must have an associated raster data table // whose name is unique among raster data table names in the database. // If the GeoRaster object is not empty and not blank, the raster // data table must exist, be visible in the current schema, be defined // in the same schema as the GeoRaster data table, and be an object // table of SDO_RASTER type. However, one or more of these requirements // were not met. // *Action: Check the rasterDataTable specification and ensure that all // relevant raster data table requirements are met. / 13404, 00000, "invalid ultCoordinate parameter" // *Cause: The ultCoordinate array parameter had the wrong length or // contained an invalid value. // *Action: Check the documentation, and make sure the ultCoordinate // parameter is correct. / 13405, 00000, "null or invalid dimensionSize parameter" // *Cause: The dimensionSize array parameter was null, had the wrong length, // or contained an invalid value. // *Action: Check the documentation, and make sure the dimensionSize // parameter is correct. / 13406, 00000, "null or invalid GeoRaster object for output" // *Cause: The GeoRaster object for output was null or invalid. // *Action: Make sure the GeoRaster object for output has been // initialized properly. / 13407, 00000, "invalid storage parameter%s" // *Cause: The storage parameter contained an invalid specification. // *Action: Check the documentation, and make sure the storage parameter is // correct. / 13408, 00000, "invalid blockSize storage parameter" // *Cause: The blockSize storage parameter had the wrong length or // contained invalid value. // *Action: Check the documentation, and make sure the blockSize storage // parameter is correct. / 13409, 00000, "null or invalid pyramidLevel parameter" // *Cause: The specified pyramidLevel parameter was null or invalid. // *Action: Make sure the pyramidLevel parameter specifies a valid pyramid // level value for the GeoRaster object. / 13410, 00000, "invalid layerNumbers or bandNumbers parameter" // *Cause: The layerNumbers or bandNumbers parameter was invalid. // *Action: Check the documentation and make sure the layerNumbers or // bandNumbers parameter is valid. / 13411, 00000, "subset results in null data set" // *Cause: The intersection of cropArea and source GeoRaster object was null. // *Action: Check the documentation, and make sure the cropArea parameter // is correct. / 13412, 00000, "invalid scale parameter%s" // *Cause: The scale parameter contained an invalid specification. // *Action: Check the documentation, and make sure the scale parameter is // correct. / 13413, 00000, "null or invalid resampling parameter" // *Cause: The resampling parameter was null or invalid. // *Action: Check the documentation, and make sure the resampling parameter // is correct. / 13414, 00000, "invalid pyramid parameter" // *Cause: The pyramid parameter was invalid. // *Action: Check the documentation, and make sure the pyramid parameter is // correct. / 13415, 00000, "invalid or out of scope point specification" // *Cause: The point position specified by the or // parameter combination was // invalid or out of scope. // *Action: Make sure the parameter(s) specify a valid point that is or can be // translated into a cell position inside the cell space of the // GeoRaster object. / 13416, 00000, "invalid geometry parameter" // *Cause: The geometry parameter did not specify a valid single-point // geometry. // *Action: Specify a valid single-point geometry. / 13417, 00000, "null or invalid layerNumber parameter" // *Cause: The layerNumber parameter was null or out of scope. // *Action: Specify a valid layerNumber parameter. / 13418, 00000, "null or invalid parameter(s) for set functions" // *Cause: A parameter for set metadata operations was null or invalid. // *Action: Check the documentation for information about the parameters. / 13419, 00000, "cannot perform mosaick operation on the specified table column" // *Cause: An attempt to perform a mosaick operation failed because the // GeoRaster objects in the specified table column did not meet // necessary conditions. // *Action: Check the documentation for SDO_GEOR.Mosaick for details. / 13420, 00000, "the SRID of the geometry parameter was not null" // *Cause: The input geometry must be in the GeoRaster cell space, // which has a null SRID value. // *Action: Make sure the geometry parameter has a null SRID. / 13421, 00000, "NULL or invalid cell value" // *Cause: The cell value was NULL or out-of-scope. // *Action: Make sure the cell value is not NULL and is in the range as designated // by the cellDepth definition of the specified GeoRaster object. / 13422, 00000, "invalid model coordinate parameter" // *Cause: The model coordinate array parameter had the wrong length // or had null ordinate element(s). // *Action: Make sure the model coordinate parameter is valid. / 13423, 00000, "invalid cell coordinate parameter" // *Cause: The cell coordinate array parameter had the wrong length // or had null ordinate element(s). // *Action: Make sure the cell coordinate parameter is valid. / 13424, 00000, "the GeoRaster object is not spatially referenced" // *Cause: The GeoRaster object was not spatially referenced. // *Action: Make sure the GeoRaster object is spatially referenced. / 13425, 00000, "invalid background filling value parameter" // *Cause: The background filling value parameter was invalid either because // the array had the wrong size or because some of the element values // were invalid. // *Action: Make sure the parameter that specifies the background filling // value is valid. The size of the array must equal to either 1 // (the value is for all bands) or the exact band dimension size. // The element values must be valid cell values as determined by // the cell depth. / 13426, 00000, "invalid window parameter" // *Cause: The specified window parameter was invalid. // *Action: Specify a valid window parameter. Check the documentation // for details. / 13427, 00000, "invalid bitmap mask" // *Cause: The bitmap mask was not a valid 1BIT GeoRaster object, or it had // the wrong dimension sizes. // *Action: Make sure the bitmap mask is a valid 1BIT GeoRaster object with // only one band, and the row and column dimension sizes of the // bitmap mask are the same as those of the target GeoRaster object. / 13428, 00000, "invalid modelCoordinateLocation" // *Cause: The program [or user] specified a modelCoordinateLocation // that is not supported, or the modelCoordinateLocation of // the GeoRaster object was wrong. // *Action: Set or specify the modelCoordinateLocation to be // CENTER (0) or UPPERLEFT (1). / 13429, 00000, "invalid xCoefficients or yCoefficients parameter(s)" // *Cause: An attempt to perform a georeference operation failed. // Possible reasons include xCoefficients or yCoefficients having // the wrong number of coefficients or invalid coefficients. // *Action: Check the documentation for supported coefficient specifications. / 13430, 00000, "the GeoRaster object has null attribute(s)" // *Cause: The metadata or rasterType of the GeoRaster object was null. // *Action: This object may only be used as an output parameter of // procedures or functions. It is not valid for other purposes. / 13431, 00000, "GeoRaster metadata rasterType error" // *Cause: The rasterType in the metadata of the GeoRaster object // was inconsistent with the GeoRaster rasterType attribute. // *Action: Make sure the rasterType in the metadata of the GeoRaster object // and the GeoRaster rasterType attribute have the same value. / 13432, 00000, "NULL or invalid blankCellValue" // *Cause: The blankCellValue element could not be found in the metadata of // a blank GeoRaster object, or the specified blankCellValue element // value was NULL or invalid. // *Action: Call SDO_GEOR.setBlankCellValue to add blankCellValue to the // metadata whenever the isBlank element value is TRUE, and make sure // that the specified blankCellValue element value is not NULL and is // in the range as designated by the cellDepth definition of the // GeoRaster object. / 13433, 00000, "GeoRaster metadata default RGB error" // *Cause: At least one of the defaultRed, defaultGreen, and defaultBlue // values (logical layer numbers) was zero, negative, or out of range. // *Action: Check the documentation for details. / 13434, 00000, "GeoRaster metadata cellRepresentation error" // *Cause: The cellRepresentation type was not supported. // *Action: Check the documentation for supported cellRepresentation types. / 13435, 00000, "GeoRaster metadata dimension inconsistent" // *Cause: The specification of dimensions or totalDimensions // was inconsistent with rasterType, or vice versa. // *Action: Make sure dimension specifications are consistent. / 13436, 00000, "GeoRaster metadata dimensionSize error" // *Cause: Either the dimensionSize for each dimension was not specified, // or an extraneous dimensionSize was specified. // *Action: Add a dimsenionSize for each dimension of the GeoRaster // object and delete extra dimensionSize elements. / 13437, 00000, "GeoRaster metadata blocking error" // *Cause: Either the wrong block number(s) or block size(s) along dimensions // were specified, or the block numbers and sizes when taken // together were not consistent. // *Action: Check the documentation for details. / 13438, 00000, "GeoRaster metadata pyramid type error" // *Cause: The specified pyramid type was not supported. // *Action: Check the documentation for supported pyramid types. / 13439, 00000, "GeoRaster metadata pyramid maxLevel error" // *Cause: The specified maxLevel exceeded the maximum level // allowed by the specified pyramid type. // *Action: Check the documentation for supported pyramid types // and their total level limitations. / 13440, 00000, "GeoRaster metadata compression type error" // *Cause: The specified compression type was not supported. // *Action: Check the documentation for supported compression types. / 13441, 00000, "GeoRaster metadata SRS error: %s" // *Cause: The specified error relates to the polynomialModel element in // the Spatial Reference System (SRS) metadata. // *Action: Check the documentation and make sure that a valid polynomial // model is specified. / 13442, 00000, "GeoRaster object not registered: %s" // *Cause: There was no sysdata entry for the specified GeoRaster object. // *Action: Make sure that a sysdata entry has been inserted for the specified // GeoRaster object. / 13443, 00000, "null or invalid values in %s" // *Cause: There were null or invalid component values in the specified // metadata. // *Action: Check the documentation and make sure that all the component // values are valid. / 13444, 00000, "cannot perform mergeLayers operation" // *Cause: The two GeoRaster objects whose layers are to be combined together // either had different row or column dimension sizes, or their // georeferencing information did not match. // *Action: Make sure the objects have the same row and column dimension // sizes. If neither is georeferenced, their ULTCoordinate values // must be the same. Otherwise, they must be both georeferenced // and cover the same area in the model space. / 13445, 00000, "NULL or invalid NODATA value or value range" // *Cause: There was invalid NODATA value or value range in the metadata, or // the specified NODATA value or value range was invalid. // *Action: Make sure the NODATA value or value range is not NULL and is // completely contained in the range as designated by the cellDepth // definition of the specified GeoRaster object. / 13446, 00000, "GeoRaster metadata TRS error" // *Cause: The GeoRaster Temporal Reference System was not supported. // *Action: Set isReferenced to FALSE. / 13447, 00000, "GeoRaster metadata BRS error" // *Cause: The GeoRaster Band Reference System was not supported. // *Action: Set isReferenced to FALSE. / 13448, 00000, "GeoRaster metadata BRS error" // *Cause: The GeoRaster spectral extent specification was incorrect. // *Action: The MIN value must be less than the MAX value // in the spectralExtent element. / 13449, 00000, "GeoRaster metadata ULTCoordinate error" // *Cause: The GeoRaster rasterInfo ULTCoordinate was not correct. // *Action: Check the documentation for restrictions. / 13450, 00000, "GeoRaster metadata layerInfo error" // *Cause: The GeoRaster had more than one layerInfo element, // or the layerDimension value was not supported. // *Action: The current release only supports one layerInfo element; // layer can only be defined along one dimension, // and this dimension must be BAND. / 13451, 00000, "GeoRaster metadata scaling function error" // *Cause: The scaling function had a zero denominator. // *Action: Make sure the scaling function denominator is not zero. / 13452, 00000, "GeoRaster metadata BIN function error" // *Cause: The bin function data did not match its type. // *Action: For EXPLICIT type, provide a binTableName element; // otherwise, provide a binFunctionData element. / 13453, 00000, "GeoRaster metadata layer error" // *Cause: Too many subLayers were defined for the GeoRaster object, // or layerNumber or layerDimensionOrdinate was not assigned correctly. // *Action: The total number of logical layers cannot exceed the total number // of physical layers, and each logical layer must be assigned // a valid physical layer number following the same order. // Check the documentation for more details. / 13454, 00000, "GeoRaster metadata is invalid" // *Cause: The GeoRaster metadata was invalid against its XML Schema. // *Action: Run the schemaValidate routine to find the errors. / 13455, 00000, "GeoRaster metadata TRS error" // *Cause: The beginDateTime value was later than the endDateTime value. // *Action: Make sure that the beginDateTime value is not later than the // endDateTime value. / 13456, 00000, "GeoRaster cell data error: %s" // *Cause: There was an error in the original GeoRaster cell data or in the // cell data of the pyramids. // *Action: If the error is related to the original GeoRaster cell data, the // GeoRaster object is invalid and has to be deleted or manually // repaired. If the error is related to pyramids, delete the pyramids // and regenerate them. / 13457, 00000, "bitmap mask cell data error: %s" // *Cause: There was an error in the cell data of an original bitmap mask // or in the cell data of the pyramids of a bitmap mask. // *Action: If the error is related to an original bitmap mask, remove the // bitmap mask. If the error is related to the pyramids of a bitmap // mask, delete the pyramids and regenerate them. / 13458, 00000, "GeoRaster metadata SRS error" // *Cause: The polynomial model did not match the requirements // of a rectified GeoRaster object. // *Action: Check the documentation for the requirements of the // polynomial model for a rectified GeoRaster object, or // set isRectified to be false. / 13459, 00000, "GeoRaster metadata SRS error" // *Cause: The polynomial model was not an six-parameter transformation, // or the six-parameter transformation was not valid. // *Action: Check the documentation and make sure the polynomial model // is a valid six-parameter affine transformation. / 13460, 00000, "GeoRaster metadata SRS error" // *Cause: The referenced GeoRaster object had a zero model space SRID // or the specified model space SRID was zero. // *Action: Set or specify the model space SRID to be a nonzero number. / 13461, 00000, "the interleaving type is not supported" // *Cause: The interleaving type of the GeoRaster object was not supported. // *Action: Check the documentation for the interleaving types // supported by GeoRaster. Use SDO_GEOR.changeFormatCopy // to transform the image to a supported interleaving type. / 13462, 00000, "invalid blocking specification" // *Cause: The specified blocking configuration was invalid. // *Action: Check the documentation for the blocking specification supported // by GeoRaster. / 13463, 00000, "error retrieving GeoRaster data: %s" // *Cause: An internal error occurred while retrieving GeoRaster data from // the database. // *Action: Check the error message for details. / 13464, 00000, "error loading GeoRaster data: %s" // *Cause: An internal error occurred while loading GeoRaster data into the // database. // *Action: Check the error message for details. / 13465, 00000, "null or invalid table or column specification" // *Cause: The specified table or column did not exist, or the column was not // a GeoRaster column. // *Action: Make sure the specified table exists and the specified column is // a GeoRaster column. / 13466, 00000, "format not appropriate for specified compression method: %s" // *Cause: The operation failed because the GeoRaster object had an // inappropriate type or format for the specified compression // method. The GeoRaster type or format is not supported for the // specified compression. // *Action: Check the error message for details. Check the documentation for // the appropriate GeoRaster types and formats for each compression // method. Use SDO_GEOR.changeFormatCopy to transform the GeoRaster // object to an appropriate format, or apply another compression // method. / 13467, 00000, "unsupported GeoRaster metadata specification: %s" // *Cause: The GeoRaster metadata specification is not supported. // *Action: Check the documentation for the supported GeoRaster metadata // specifications. / 13468, 00000, "invalid blockMBR" // *Cause: Invalid blockMBR geometries were stored in the raster data table. // *Action: Make sure the blockMBR geometries stored in the raster data table // are valid, or call SDO_GEOR.generateBlockMBR() to regenerate // the blockMBR geometries. / 13469, 00000, "cannot perform updateRaster operation" // *Cause: The data of the source GeoRaster object could not be used to update // that of the target GeoRaster object. // *Action: Make sure the source and the target GeoRaster objects have the same // cell depth, and that both objects are either georeferenced or // not georeferenced at all. If both are georeferenced, they should // be in the same coordinate system and have the same spatial // resolutions. / 13470, 00000, "target and source layers or bands mismatched" // *Cause: The number of specified target layers or bands and source layers // or bands did not match. // *Action: When updating layers or bands of a target GeoRaster object to // reflect the associated layers or bands of the source GeoRaster // object, specify the same number of layers or bands for both the // source and the target objects. Check the documentation for details. / 13471, 00000, "unable to determine the owner of %s" // *Cause: The owner of the specified raster data table could not be determined. // *Action: Make sure the GeoRaster object that refers to the raster data table // has been registered by inserting the object into a GeoRaster table. / 13472, 00000, "invalid geometry parameter" // *Cause: The geometry parameter did not specify a valid geometry. // *Action: Specify a valid 2D or 3D geometry. If the model SRID is null or // indicates a 2D coordinate system, the geometry must be 2D. If the // model SRID indicates a 3D coordinate system, the geometry must // either be a 3D geometry or a 2D geometry that can be converted to // 3D with the specified vertical axis (or vertical SRID) and // ellipsoidal parameters. / 13473, 00000, "invalid rasterSpec parameter" // *Cause: The rasterSpec parameter contained an invalid specification. // *Action: Check the documentation and make sure the rasterSpec // parameter contains only valid keywords and values. / 13474, 00000, "invalid rasterDataTable name: %s" // *Cause: The rasterDataTable name was not a valid nonquoted identifier, // it contained a period separator, or not all of the alphanumeric // characters were uppercase. // *Action: Ensure that the table name is a valid nonquoted identifier // without any period separators, and that all the alphanumeric // characters are uppercase. / 13475, 00000, "invalid GeoRaster object for output" // *Cause: The output GeoRaster object had the same RASTER_DATA_TABLE // and RASTER_ID combination as that of an input GeoRaster object. // *Action: Ensure that the output GeoRaster object is different from any // of the input GeoRaster objects. / 13476, 00000, "invalid or out of scope point specification" // *Cause: The point position specified by the point geometry parameter or // the rowNumber/colNumber parameter combination was null or out of // scope. // *Action: Ensure that the parameters specify a valid point that translates // or can be translated into a cell position inside the cell space // of the GeoRaster object. / 13477, 00000, "invalid GCP georeferencing specification: %s" // *Cause: The specified functional fitting method was not supported, // the number of GCPs was insufficient, some GCPs were invalid, // or the distribution of the GCPs led to no solution or // an unstable solution. // *Action: Check the GeoRaster documentation for the supported // functional fitting methods and the requirements of GCPs. / 13478, 00000, "the target SRID is the same as the source GeoRaster object's SRID" // *Cause: The target SRID was not different from the source GeoRaster object's SRID. // *Action: Specify a different valid SRID for the target GeoRaster object. / 13479, 00000, "cannot reproject" // *Cause: Reprojection from source to destination projection produced // a large distortion. // *Action: Check the destination projection and make sure it is suitable for // the area covered by the source GeoRaster object. Check the GeoRaster // documentation for more information about reprojection. / 13480, 00000, "the Source Type is not supported" // *Cause: The specified source type was not supported. // *Action: Check the documentation for the source types (such as // FILE and HTTP) supported by GeoRaster. / 13481, 00000, "the destination type is not supported" // *Cause: The specified destination type was not supported. // *Action: Check the documentation for the destination types (such as // FILE) supported by GeoRaster. / 13482, 00000, "GeoRaster object is not initialized for the image" // *Cause: No GeoRaster object has been initialized for the specified image. // *Action: Initialize a GeoRaster object to hold this image before loading // it into the database. Check the documentation for details. / 13483, 00000, "insufficient memory for the specified GeoRaster data" // *Cause: There was insufficient memory to hold the specified GeoRaster data // for this operation. // *Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or // reblock the GeoRaster data into smaller sized blocks. Check the // documentation for details. / 13484, 00000, "the file format or compression type is not supported: %s" // *Cause: The file format or compression type was not supported. // *Action: Check the documentation for formats that are currently supported // by GeoRaster. / 13485, 00000, "error occurred during compression or decompression: %s" // *Cause: The operation could not be completed because an error occurred // during compression or decompression. Check the error message // for details. // *Action: Check that the GeoRaster object is valid, that its metadata // is valid for the specified compression format, and that valid // parameters are passed into the compression or decompression // operation. / 13486, 00000, "invalid or insufficient GeoTIFF metadata to georeference the GeoRaster object: %s" // *Cause: The GeoTIFF metadata of the specified input image contained invalid // or insufficient information to georeference the GeoRaster object. // *Action: Check the error message for details. / 13487, 00000, "SRID not found for source coordinate system metadata" // *Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the // source coordinate system metadata. // *Action: Add a user-defined coordinate reference system for this coordinate // system, as explained in the Oracle Spatial documentation. / 13497, 00000, "%s" // *Cause: This is an internal GeoRaster error. // *Action: Contact Oracle Support Services. You may want to make // sure the GeoRaster object is valid before you do so. / 13498, 00000, "%s" // *Cause: An error related to an external plugin was encountered in the // GeoRaster component. // *Action: Check the documentation for the external plugin, or contact // the plugin provider and supply the exact error text. / 13499, 00000, "%s" // *Cause: This is an internal Spatial error. // *Action: Contact Oracle Support Services. / /============================================================================= / 13500 - 13999 reserved for Server Manageability Layer / / 13500-13599 reserved for AWR / 13600-13699 reserved for the adv fmwk. / 13700-13749 reserved for the ADDM, ASH, general manageability / 13750-13799 reserved for sql tune and sql tune set / 19371-19390 reserved for sql tune and sql tune set (2) / 13800-13849 reserved for the SQL Tuning Base and for SQL profiles. / 13850-13899 reserved for end-to-end tracing / 13900-13949 reserved for threshold-based alerts / 13950-13969 reserved for MMON infrastructure / 13970-13999 reserved for the common reporting framework (KER) / / =============================================================== / NOTE: NEXT CHUNK OF MESSAGES RESERVED BETWEEN 15500 AND 15999 / If your project belongs to the Server Manageability layer / please allocate yourself a chunk in that range. / ================================================================ / /============================================================================= / / 13500 - 13599 reserved for AWR / 13500, 00000, "SYSAUX DATAFILE clause specified more than once" // *Cause: The CREATE DATABASE command contains more than one SYSAUX // DATAFILE clause. // *Action: Specify at most one SYSAUX DATAFILE clause. / 13501, 00000, "Cannot drop SYSAUX tablespace" // *Cause: Tried to drop SYSAUX tablespace // *Action: None / 13502, 00000, "Cannot rename SYSAUX tablespace" // *Cause: An attempt to rename the SYSAUX tablespace failed. // *Action: No action required. / 13503, 00000, "Creating SYSAUX tablespace with invalid attributes" // *Cause: An attempt to create the SYSAUX tablespace with invalid attributes. // *Action: Create SYSAUX tablespace with ONLINE, PERMANENT, // EXTENT MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO // attributes. / 13504, 00000, "No SYSAUX datafile clause specified" // *Cause: If Create Database has the datafile clause, then // SYSAUX datafile clause has to be specified, unless using OMF. // *Action: Specify the SYSAUX datafile clause. / 13505, 00000, "SYSAUX tablespace can not be made read only" // *Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX // tablespace must remain read write for database operation. // *Action: Leave SYSAUX tablespace read write. / 13506, 00000, "operation failed due to invalid snapshot range (%s, %s)" // *Cause: An attempt was made to perform operation with an invalid Start/End // Snapshot Pair. // *Action: Choose a valid Start/End Snapshot Pair. / 13507, 00000, "Event for Testing SYSAUX occupant view" // *Document: NO // *Cause: // *Action: Display the test SYSAUX occupant in the V$SYSAUX_OCCUPANT view / 13508, 00000, "Event to update INTERVAL and RETENTION in number of seconds" // *Document: NO // *Cause: // *Action: / 13509, 00000, "error encountered during updates to a AWR table" // *Cause: An update error occurred during OCI operation due to an underlying // error. // *Action: Check associated OCI error. Correct problem and retry // the operation. / 13510, 00000, "invalid RETENTION %s, must be in the range (%s, %s)" // *Cause: The user has specified a RETENTION setting that is not in the // supported range of (MIN, MAX). // *Action: Choose a valid RETENTION setting and retry the operation. / 13511, 00000, "invalid INTERVAL %s, must be in the range (%s, %s)" // *Cause: The user has specified a INTERVAL setting that is not in the // supported range of (MIN, MAX). // *Action: Choose a valid INTERVAL setting and retry the operation. / 13512, 00000, "event #1 to test the top Segment Statistics" // *Document: NO // *Cause: // *Action: will compute the top 10 segments based on logical reads. / 13513, 00000, "event #2 to test the top Segment Statistics" // *Document: NO // *Cause: // *Action: will compute the top 5 segments for logical reads and wait count. / 13514, 00000, "Metric Capture too close to last capture, group %s" // *Cause: The metric capture cannot be executed because it is too close // to the last capture (within 1 centi-second). // *Action: add some delay and reissue command to retry. / 13515, 00000, "Error encountered during Database Usage Statistics capture" // *Cause: Error occurred during OCI operation due to underlying error. // *Action: Check associated OCI error. Correct problem and retry // the operation. / 13516, 00000, "AWR Operation failed: %s" // *Cause: The operation failed because AWR is not available. The // possible causes are: AWR schema not yet created; AWR // not enabled; AWR schema not initialized; or database // not open or is running in READONLY or STANDBY mode. // *Action: check the above conditions and retry the operation. / 13517, 00000, "Baseline (id = %s) does not exist" // *Cause: The operation failed because the specified baseline ID // does not exist in the Workload Repository. // *Action: check the baseline id and retry the operation. / 13518, 00000, "Invalid database id (%s)" // *Cause: The operation failed because the specified database ID // does not exist in the Workload Repository. // *Action: check the database id and retry the operation. / 13519, 00000, "Database id (%s) exists in the workload repository" // *Cause: The operation failed because the specified database ID // already exists in the Workload Repository. // *Action: check the database id and retry the operation. / 13520, 00000, "Database id (%s) not registered, Status = %s" // *Cause: The operation failed because the specified database ID // was not registered in the Workload Repository properly. // *Action: check the status of database id and retry the operation. / 13521, 00000, "Unregister operation on local Database id (%s) not allowed" // *Cause: The operation failed because the local database ID // cannot be unregistered from the Workload Repository. // *Action: check the database id and retry the operation. / 13522, 00000, "event to toggle checking for duplicate sql id (num)" // *Document: NO // *Cause: // *Action: Event will determine whether to filter out duplicates for // Top SQL selection. / 13523, 00000, "unable to allocate required space for return type" // *Cause: Out of memory to allocate the space for the return variable // for an external procedure. // *Action: Try operation again. / 13524, 00000, "error encountered while retrieving baseline information" // *Cause: A read error occurred during the OCI operation to retrieve // the baseline information // *Action: Check associated error. Correct problem and retry // the operation. / 13525, 00000, "error with computing space usage for sysaux occupant" // *Cause: Error occurred during OCI operation due to underlying error. // *Action: Check associated OCI error. Correct problem and retry // the operation. / 13526, 00000, "baseline (%s) does not exist" // *Cause: The operation failed because the specified baseline name // does not exist in the Workload Repository. // *Action: check the baseline name and retry the operation. / 13527, 00000, "invalid baseline name" // *Cause: The operation failed because the specified baseline name // is invalid. // *Action: check the baseline name and retry the operation. / 13528, 00000, "name (%s) is already used by an existing baseline" // *Cause: The operation failed because the specified baseline name // already exists in the Workload Repository. // *Action: check the baseline name and retry the operation. / 13529, 00000, "Error occurred when flushing AWR table group" // *Cause: An error occurred during the flushing of a table group. // Because of the error in the group, we are unable to flush // this table. // *Action: Check the error associated with the table group. / 13530, 00000, "invalid TOPNSQL %s, must be in the range (%s, %s)" // *Cause: The user has specified a TOPNSQL setting that is not in the // supported range of (MIN, MAX). // *Action: Choose a valid TOPNSQL setting and retry the operation. / 13531, 00000, "SQL Text was purged from AWR before the operation completed" // *Cause: A SQL was purged from AWR before the operation completed. // *Action: Retry the operation. / 13532, 00000, "SQL ID [%s] already exists" // *Cause: The operation failed because the specified SQL ID // already existed in the repository. // *Action: Check the SQL ID and retry the operation. / 13533, 00000, "invalid SQL ID" // *Cause: The operation failed because the specified SQL ID was // invalid. // *Action: Check the SQL ID and retry the operation. / 13534, 00000, "Current SQL count(%s) reached maximum allowed (%s)" // *Cause: The operation failed because the maximum allowed colored // SQL was exceeded. // *Action: Check the count for colored SQL. / 13535, 00000, "name (%s) is already used by an existing baseline template" // *Cause: The operation failed because the specified baseline template name // already existed in the Workload Repository. // *Action: Check the baseline template name and retry the operation. / 13536, 00000, "baseline template (%s) does not exist" // *Cause: The operation failed because the specified baseline template name // did not exist in the Workload Repository. // *Action: Check the baseline template name and retry the operation. / 13537, 00000, "invalid input for create baseline template (%s, %s)" // *Cause: Invalid input was specified for the create baseline template // routine. // *Action: Check the argument displayed in the error message text. / 13538, 00000, "invalid value for baseline expiration (%s)" // *Cause: An invalid value was specified for the expiration of a baseline. // The expiration is specified in number of days, and the expiration // must be at least one day. // *Action: Check the value for expiration. / 13539, 00000, "invalid input for modify baseline window size (%s, %s)" // *Cause: Invalid input was specified for the modify baseline window // size routine. // *Action: Check the argument displayed in the error message text. / 13540, 00000, "operation not allowed on system moving window baseline (%s)" // *Cause: The requested operation was not allowed on the system moving // window baseline. // *Action: Retry the operation with another baseline name. / 13541, 00000, "system moving window baseline size (%s) greater than retention (%s)" // *Cause: The system moving window baseline size must be less than the // retention setting. The specified window size or retention // violate this. // *Action: Check the moving window baseline size or retention. / 13542, 00000, "baseline ID (%s) does not exist" // *Cause: The operation failed because the specified baseline ID // did not exist in the Workload Repository. // *Action: Check the baseline ID and retry the operation. / 13543, 00000, "error encountered while retrieving baseline template information" // *Cause: A read error occurred during the OCI operation to retrieve // the baseline template information. // *Action: Check associated error. Correct problem and retry // the operation. / 13544, 00000, "error encountered while automatically generating a baseline" // *Cause: An error occurred while automatically generating a baseline // based on the template information. // *Action: Look in the trace file for more error information. / 13545, 00000, "invalid baseline template name" // *Cause: The operation failed because the specified baseline // template name was an invalid identifier. // *Action: Check the baseline template name and retry the operation. / 13546, 00000, "Error encountered during maintenance of Adaptive Thresholds" // *Cause: Error occurred during OCI operation due to underlying error. // *Action: Check associated OCI error. Correct problem and retry // the operation. / 13547, 00000, "Unable to drop baseline since it is in use by %s" // *Cause: The system is not able to drop the baseline since the baseline // is in use by a functionality that depends on its existence. // *Action: Note the name of the functionality using the baseline, and // check if the functionality still needs the baseline. / 13548, 00000, "Unable to find valid snapshot IDs for the inputted baseline time range" // *Cause: The system is not able to find valid snapshot IDs for the inputted // time range while attempting to create a baseline. // *Action: Check that the inputted time range has at least two valid // snapshots. The dba_hist_snapshot displays the snapshot id and // time information. / 13549, 00000, "invalid input for create baseline with time range (%s)" // *Cause: Invalid time input was specified for the create baseline // routine. // *Action: Check the argument displayed in the error message text. / / ======================================== / 13600 - 13699 reserved for the adv fmwk. / ======================================== 13600, 00000, "error encountered in Advisor\n%s" // *Cause: An error occurred in the Advisor. // This message will be followed by a second message giving // more details about the nature of the error. // *Action: See the Advisor documentation // for an explanation of the second error message. / 13601, 00000, "The specified Advisor %s does not exist." // *Cause: The user specified an advisor name that has not be defined // in the advisor repository. // *Action: Correct the advisor name and retry the operation. / 13602, 00000, "The specified parameter %s is not valid for task or object %s." // *Cause: The user attempted to access a task parameter that does not // exist for the specified advisor object. The parameter may be // misspelled or the user has selected a parameter that is not // supported by the particular advisor. // *Action: Validate the parameter name and retry the operation. / 13603, 00000, "The specified parameter %s cannot be fetched as a numeric value for task or object %s." // *Cause: The user attempted to retrieve a string parameter as a numeric // value. // *Action: Check the datatype for the task parameter and retry the operation. / 13604, 00000, "The specified parameter %s cannot be fetched as a SQL table." // *Cause: The user attempted to retrieve a non-table parameter as a table // name. // *Action: Check the datatype for the task parameter and retry the operation. / 13605, 00000, "The specified task or object %s does not exist for the current user." // *Cause: The user attempted to reference an advisor task or object // using a name that does not exist in the Advisor repository. // *Action: Adjust the name and retry the operation. / 13606, 00000, "the specified task parameter element %s is out of range for parameter %s." // *Cause: The user attempted to reference an invalid parameter element. // *Action: Adjust the element offset and retry the operation. / 13607, 00000, "The specified task or object %s already exists" // *Cause: The user attempted to create the specified task or object // using a name that already exists in the Advisor repository. // Task names must be unique to the database user. // *Action: Adjust the name and retry the operation. / 13608, 00000, "The specified name %s is invalid." // *Cause: An attempt was made to specify a name for a task, object, execution // or directive instance, which contained invalid characters or // an invalid wildcard specifier. // *Action: Adjust the name and retry the operation. / 13609, 00000, "The specified task %s must be executing to be cancelled or interrupted." // *Cause: The user attempted to cancel or interrupt a task that is not // currently executing. // *Action: Check the status of the task and retry the operation. / 13610, 00000, "The directive %s does not exist for task %s." // *Cause: The user attempted to access a task directive that does not exist. // *Action: Validate the directive and retry the operation. / 13611, 00000, "The command %s is not a valid advisor command." // *Cause: The user attempted to specify a command that does not exist. // *Action: Validate the command and retry the operation. / 13612, 00000, "The recommendation action %s,%s is not valid for task %s." // *Cause: The user attempted to access a recommendation action that does // not exist in the task. // *Action: Validate the recommendation-action and retry the operation. / 13613, 00000, "The requested operation is not supported for this advisor object." // *Cause: The user attempted to perform an operation that is not supported // for the particular advisor or task type. // *Action: Validate the task or object and retry the operation. / 13614, 00000, "The template %s is not compatible with the current advisor." // *Cause: The user attempted to create a new task or object using // an existing task or object that was not created by the // same advisor. // *Action: Validate the template and retry the operation. / 13615, 00000, "The task or object %s is greater than the maximum allowable length of 30 characters." // *Cause: The user attempted to create a new task or object using // a name that is too long. // *Action: Shorten the name and retry the operation. / 13616, 00000, "The current user %s has not been granted the ADVISOR privilege." // *Cause: The user attempted an advisor operation that requires privilege. // *Action: Adjust the user's privileges and retry the operation. / 13617, 00000, "The specified task %s already executing" // *Cause: The user attempted to execute a task that is currently executing. // *Action: Wait for the task to finish before attempting any further task // activities. / 13618, 00000, "The specified value is not a valid value for procedure argument %s." // *Cause: The user executed a procedure but failed to provide // correct values for the argument. // *Action: Correct the procedure arguments and retry the operation. / 13619, 00000, "The procedure argument %s is greater than the maximum allowable length of %s characters." // *Cause: The user attempted to pass a character argument that is too long. // *Action: Shorten the specified character argument and retry the operation. / 13620, 00000, "The task or object %s is read-only and cannot be deleted or modified." // *Cause: The user attempted to perform an operation that will update // or delete a read-only task or object. // *Action: Adjust the READ_ONLY property for the object and retry the // operation. / 13621, 00000, "The task_or object %s is marked as a template and cannot perform the requested operation." // *Cause: The user attempted perform an unsupported operation on a task or // object that is identified as a template. // *Action: Choose a different object and retry the operation. / 13622, 00000, "invalid recommendation annotation" // *Cause: The user attempted to mark a recommendation using an invalid // annotation. Valid annotation actions are ACCEPT, REJECT and // IGNORE. // *Action: Correct the action and retry the operation. / 13623, 00000, "The recommendation %s is not valid for task %s." // *Cause: The user attempted to access a recommendation that does // not exist in the task. // *Action: Validate the recommendation and retry the operation. / 13624, 00000, "The task %s is executing and cannot be deleted or modified." // *Cause: The user attempted to access a task that currently executing. // *Action: Wait for the task to complete and retry the operation. / 13625, 00000, "%s is an invalid advisor object type." // *Cause: The user has specified an invlaid object type. // *Action: Refre to dba_advisor_object_types for all valid object types / 13626, 00000, "The specified object %s is not valid for task %s." // *Cause: The user specified an non-existent object for the task // *Action: Choose a different object and retry the operation. / 13627, 00000, "Setting of parameter %s is disallowed until the task is reset." // *Cause: The user attempted to set the value of a parameter before the task // was reset. This parameter cannot be changed until the task is // reset. // *Action: Reset the task and retry the operation. / 13628, 00000, "Insufficient privileges to access the task belonging to the specified user" // *Cause: The user could not access dba_* views. // *Action: Retry operation as owner of the task or after granting new privileges. / 13629, 00000, "The task or object %s is being used by another operation." // *Cause: The user attempted to access a task or object that is locked by // another session. // *Action: Wait for the task or object activity to complete and retry // the operation. / 13630, 00000, "The task %s contains execution results and cannot be executed." // *Cause: The user attempted to execute a task that already contains // execution results. // *Action: Reset the task to its initial state and retry the operation. / 13631, 00000, "The most recent execution of task %s contains no results." // *Cause: The user attempted to create a report or script from a task that // has not successfully completed an execution. // *Action: Execute the task and then retry the operation / 13632, 00000, "The user cancelled the current operation." // *Cause: The user signaled a cancel during a task or object operation. // *Action: None / 13633, 00000, "The task %s was interrupted and needs to be resumed." // *Cause: The user attempted to execute a task that was interrupted. // *Action: Resume the execution of the task via the RESUME_TASK API. / 13634, 00000, "The task %s needs to be reset before being re-executed." // *Cause: The task must be in an inital state to be executed. // *Action: Reset the task to its initial state and retry the operation. / 13635, 00000, "The value provided for parameter %s cannot be converted to a number." // *Cause: A numeric parameter was incorrectly supplied in string form. // *Action: Retry by supplying valid numeric value. / 13636, 00000, "The specified value provided for parameter %s is not valid for this advisor." // *Cause: The user supplied an invalid parameter value. // *Action: Retry by supplying valid value. / 13637, 00000, "Executing or modifying task %s is disallowed until the task is reset to its initial state." // *Cause: The user attempted to execute or modify the task that is in // not in its INITIAL state. // *Action: Reset the task and retry the operation. / 13638, 00000, "The user interrupted the current operation." // *Cause: The user signaled an interrupt during a task or object operation. // *Action: None / 13639, 00000, "The current operation was interrupted because it timed out." // *Cause: The task or object operation timed out. // *Action: None / 13640, 00000, "The current operation was cancelled because it timed out, and was not in interruptible mode." // *Cause: The task or object operation timed out. // *Action: None / 13641, 00000, "Task cannot be interrupted yet. You may cancel it instead." // *Cause: The user attempted to interrupt a task that has not // reached interruptible mode. // *Action: Wait until the task reaches interruptible mode, or cancel the // task execution. / 13642, 00000, "The specified string %s provided for %s cannot be converted to a date. The acceptable date format is %s." // *Cause: The user supplied a date value in an incorrect format. // *Action: Retry by supplying valid value. / 13643, 00000, "The task can not be interrupted or cancelled." / *Cause: Request to interrupt or cancel task execution can not be granted // because the task has not reached the appropriate mode. // *Action: User should wait for a few seconds and try again. / 13644, 00000, "The user \"%s\" is invalid." // *Cause: Invalid user name specified to advisor framework // *Action: User should specify a correct, case-sensitive, name / 13645, 00000, "The specified execution %s does not exist for this task." // *Cause: You attempted to reference an advisor task execution // using a name that did not exist. // *Action: Adjust the name and retry the operation. / 13646, 00000, "The specified execution %s already exists" // *Cause: You attempted to perform a new execution // using a name that already exists for the specified task. // Execution names must be unique within the same task. // *Action: Adjust the name and retry the operation. / 13647, 00000, "Setting of parameter %s is disallowed during task execution." // *Cause: You attempted to set the value of a parameter while the task // was being executed. This parameter cannot be changed until the task // finishes its execution. // *Action: Verify the status of the task and retry the operation. / 13648, 00000, "The specified execution type does not exist for this advisor." // *Cause: You attempted to use an advisor task execution type // using a name that did not exist. // *Action: Adjust the name and retry the operation. / 13649, 00000, "The type of execution is not specified for this advisor or task." // *Cause: You attempted to execute a task for a multi-execution task // advisor without specifying the type of execution to perform. // *Action: Set the execution type and retry the operation. / 13650, 00000, "The specified object does not exist for this execution." // *Cause: You attempted to associate an object to a task execution // that id not contain the object. // *Action: Adjust the execution name and object ID, and then retry the operation. / 13651, 00000, "The specified list of execution parameters is invalid." // *Cause: The list did not include pairs of (parameter_name, parameter_value) // where every parameter is a valide task parameter. Duplicates are // not allowed. // *Action: Adjust the content of the list, and then retry the operation. / 13652, 00000, "Cannot set execution parameters for this advisor" // *Cause: You attempted to set execution parameters for an advisor // that did not support multiple executions of its tasks. // *Action: Adjust the property of the advisor, and then retry the operation. / 13653, 00000, "The directive with definition id %s was not found." // *Cause: An invalid directive identifier was specified to advisor framework. // *Action: User should specify a correct identifier number and retry the // operation. / 13654, 00000, "The directive with instance id of %s was not found." // *Cause: An invalid instance identifier was specified to advisor framework. // *Action: User should specify a correct instance identifier number and retry the // operation. / 13655, 00000, "The directive document contains a syntax error and cannot be loaded." // *Cause: An attempt was made to load an XML-based directive that does not // conform to the documented DTD. // *Action: Reformat the directive according the documented DTD. / 13656, 00000, "The parameter was not found in directive %s." // *Cause: The specified parameter name could not be located within the directive // XML document. // *Action: Verify the existence of the parameter in the specified directive. / 13657, 00000, "The filter Xpath specification has invalid syntax." // *Cause: The specified filter could not be compiled within the directive // XML document. // *Action: Verify the syntax of the filter and retry the operation. / 13658, 00000, "The specified directive already has an instance" // *Cause: An attempt was made to create multiple instances of a directive when not permitted // *Action: Verify the parent directive identifier and the instance name. / 13659, 00000, "A directive with domain \"%s\" and name \"%s\" already exists for advisor %s." // *Cause: The specified directive is not unique among the directives. // *Action: Choose a directive name and domain that is distinct for the associated advisor. / 13660, 00000, "A directive instance with the name \"%s\" already exists." // *Cause: The specified directive instance is not unique among instances for this directive. // *Action: Choose an instance name that is distinct for the associated directive. / 13661, 00000, "A directive instance with the name \"%s\" was not found." // *Cause: An attempt was made to update or delete a non-existent directive instance. // *Action: Verify the parent directive identifier and the instance name. / 13662, 00000, "The specified value provided for parameter %s is not valid for this task." // *Cause: The supplied parameter value was not valid for the current task // configuration. // *Action: Retry by supplying valid value. Check the current task // configuration. / 13663, 00000, "The task %s contains no results for execution %s." // *Cause: An attempt was made to create a report or script from an execution // that had not been successfully completed. // *Action: Run a new execution and then retry the operation. / 13664, 00000, "A task-managed \"SQL Tuning Set\" already exists for task \"%s\"." // *Cause: An attempt was made to create a task-managed SQL Tuning Set for // a task that already had one. // *Action: Create a new task to use a different SQL Tuning Set. / 13665, 00000, "Execution names are not correctly ordered." // *Cause: The supplied execution names were not properly ordered by // execution start date. // *Action: Retry by supplying a valid order. / 13666, 00000, "Task ID %s does not exist." // *Cause: The supplied task ID was invalid. // *Action: Check the task ID and try again. / 13667, 00000, "Execution ID %s does not exist." // *Cause: The supplied execution ID was invalid. // *Action: Check the execution ID and try again. / 13668, 00000, "The current operation was aborted because it was blocking another session." // *Cause: The task or object operation interrupted itself when it detected // that it was blocking some other session. // *Action: Retry the operation when the conflicting operations are not // running. / 13669, 00000, "Execution provided has type \"%s\", expected \"%s\"." // *Cause: An execution was provided whose type did not match the one // expected by the API. // *Action: Check the execution name, and try again. / 13670, 00000, "No execution of type %s exists for task provided." // *Cause: No execution of the required type existed for the given advisor // task. // *Action: Check the task, and try again. / 13699, 00000, "Advisor feature is not currently implemented." // *Cause: An attempt was made to execute an unsupported advisor operation. // *Action: Verify the availability of the operation. // / / ======================================== / 13700 - 13749 reserved for the ADDM, ASH / ======================================== / 13700, 00000, "Reserved for ADDM tracing." // *Cause: // *Action: / 13701, 00000, "Snapshot pair [%s, %s] seems to be specified in reverse order." // *Cause: The start snapshot id was greater than the end snapshot id. // *Action: Swap the start and end snapshot ids. / 13702, 00000, "Snapshot IDs specified by the range [%s, %s] are equal." // *Cause: The start snapshot id and end snapshot id were identical. // *Action: Provide different start and end snapshot ids. / 13703, 00000, "The snapshot pair [%s, %s] for database_id %s and instance_id %s are not found in the current repository." // *Cause: The snapshot ids or the database id or the instance id was invalid // or the specified snapshots have already been purged. // *Action: Set valid snapshot ids and retry. / 13704, 00000, "Invalid value \"%s\" specified for parameter \"%s\"." // *Cause: The parameter was not set before executing the ADDM. // *Action: Set the parameter to a valid value and retry. / 13705, 00000, "There was a instance shutdown/startup between the snapshots in the range [%s, %s]." // *Cause: Instance was shut down and restarted between the // two specified snapshots. // *Action: Specify start and end snapshot ids that does not have a // shutdown/startup in between them. / 13706, 00000, "Invalid value \"%s\" specified for parameter \"%s\" in \"%s\" analysis mode." // *Cause: The parameter was not set to an acceptable value for this // particular mode of analysis. // *Action: Set the parameter to a valid value and retry. / 13707, 00000, "Either the start snapshot %s or the end snapshot %s is incomplete or missing key statistics." // *Cause: Either the start or the end snaphots was missing or purged // or had encountered errors while creating them. // *Action: Verify that AWR is done taking these two snapshots, or // Look in DBA_HIST_SNAP_ERROR to find what tables are missing // in the start/end snapshots. // Use the ERROR_NUMBER column in that view together with the // alert log to identify the reason for failure and take // necessary action to prevent such failures in the future. // Try running ADDM on a different snapshot range that has // valid start and end snapshots. / 13708, 00000, "Some snapshots in the range [%s, %s] were purged before the analysis was complete." // *Cause: One or both of the snapshots have been purged from AWR. // *Action: Verify that the AWR auto purging is not trying to purge // these snapshots and re-run ADDM. / 13709, 00000, "Required parameter \"%s\" must be set before execution." // *Cause: The parameter needs to be set before running the ADDM // *Action: Set the parameter to a valid value and retry. / 13710, 00000, "Parameter \"%s\" must have a higher value than parameter \"%s\". The values supplied were \"%s\" and \"%s\" respectively." // *Cause: Invalid interaction between two parameter values. // *Action: Set at least one of the values so the value of the first parameter // is higher than the value of the second parameter. / 13711, 00000, "Some snapshots in the range [%s, %s] are missing key statistics." // *Cause: Some AWR tables encountered errors while creating one or more // snapshots in the given range. The data present in one or more of // these missing tables is necessary to perform an ADDM analysis. // *Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing // in the given snapshot range. Use the ERROR_NUMBER column in // that view together with the alert log to identify the reason // for failure and take necessary action to prevent such failures // in the future. // Try running ADDM on a different snapshot range that // does not include any incomplete snapshots. / 13712, 00000, "Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version \"%s\" do not match the database version \"%s\"." // *Cause: ADDM analysis can only be performed on AWR snapshots taken in the // current release. // *Action: One can still generate AWR and ASH reports using // ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots // to analyze the data in them. / 13713, 00000, "Finding name \"%s\" does not exist. Look in DBA_ADVISOR_FINDING_NAMES for all valid values" // *Cause: Attempt to refer to an advisor's finding name that does not exist. // *Action: Specify a valid value. The list of all valid values is in // DBA_ADVISOR_FINDING_NAMES 13714, 00000, "\"%s\" is not a valid SQL_ID value" // *Cause: The specified value of SQL_ID was not properly formatted. // *Action: Specify a valid value consisting of a 13 character string with characters // from '0' to '9' and from 'a' to 'z'. 13715, 00000, "\"%s\" is not recognized by ADDM as a parameter name" // *Cause: The specified value for a system parameter was not recognized by ADDM. // *Action: Specify a value that appears in the NAME column of V$PARAMETER. / 13716, 00000, "Diagnostic Package License is needed for using this feature." // *Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS // indicated that the Diagnostic Package was disabled. // *Action: Modify the parameter value if the Diagnostic Package License was // purchased. / 13717, 00000, "Tuning Package License is needed for using this feature." // *Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS // indicated that the Tuning Package was disabled. // *Action: Modify the parameter value if the Tuning Package License was // purchased. / 13718, 00000, "Tuning Package License or Real Application Testing Option is needed for using this feature." // *Cause: The specified package license and option were not installed. // *Action: Consider purchasing and installing either the missing package licence // or option. If the tuning package license was purchased, then check // the value of system parameter CONTROL_MANAGEMENT_PACK_ACCESS. / 13719, 00000, "Imported AWR snapshots are from a database with an incompatible character set." // *Cause: ADDM analysis was attempted on imported Automatic Workload Repository (AWR) // snapshots with incompatible character set. // *Action: Perform ADDM analysis using a database with the same version and character set // as the original database. / /============================================== /= 13750 - 13799 reserved for SqlSet = /= 19371 - 19390 reserved for sqlset/sqltune = /============================================== / 13750, 00000, "User \"%s\" has not been granted the \"ADMINISTER SQL TUNING SET\" privilege." // *Cause: The user attempted an SQL Tuning Set operation that requires // a specific privilege. // *Action: Adjust the user's privileges and retry the operation. / 13751, 00000, "\"SQL Tuning Set\" \"%s\" does not exist for owner \"%s\" or user \"%s\" does not have permission to access the \"SQL Tuning Set\"." // *Cause: The user attempted to access a SQL Tuning Set that does not exist // or the user does have permission to access the SQL Tuning Set // *Action: Check the existence of the \"SQL Tuning Set\" or adjust the user's // privileges and retry the operation. / 13752, 00000, "User \"%s\" must be SYS or must have the \"ADMINISTER ANY SQL TUNING SET\" privilege." // *Cause: The attempted to create a SQL Tuning Set in another schema without having // the right privilege. // *Action: Connect as SYS or adjust the user's privilege and retry // the operation. / 13753, 00000, "\"SQL Tuning Set\" \"%s\" already exists for user \"%s\"." // *Cause: The user attempted to create a "\SQL Tuning"\ Set using a name // that already exists for that owner. // *Action: Change the name of the SQL Tuning Set and retry the operation. / 13754, 00000, "\"SQL Tuning Set\" \"%s\" does not exist for user \"%s\"." // *Cause: The user attempted to access a SQL Tuning Set that does not exist. // *Action: Check the speelling of the SQL Tuning Set name and retry // the operation. / 13755, 00000, "invalid \"SQL Tuning Set\" name" // *Cause: The user attempted to specify a SQL Tuning Set name that is invalid. // A name must not contain wildcards and its length must be less than // 30 characters. // *Action: Adjust the name and retry the operation. / 13756, 00000, "Cannot update attribute \"%s\"." // *Cause: The user attempted to update an attribute element that // cannot be modified. The only string attributes that can // be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER. // *Action: Adjust the attribute name and retry the operation. / 13757, 00000, "\"SQL Tuning Set\" \"%s\" owned by user \"%s\" is active." // *Cause: The user attempted to update an active SQL Tuning Set. // *Action: Remove all reference to the SQL Tuning Set and retry the operation. / 13758, 00000, "\"SQL Tuning Set\" \"%s\" owned by user \"%s\" is in use." // *Cause: The user attempted to modify a SQL Tuning Set or to add a reference // to a SQL Tuning Set which is in use. // *Action: Wait until the end of the previous operation and retry. / 13759, 00000, "User \"%s\" cannot remove reference \"%s\"." // *Cause: The user attempted to remove a SQL Tuning Set reference that // does not exist. The user might not own the reference. // *Action: Check the reference ID and the reference owner and retry // the operation. / 13761, 00000, "invalid filter" // *Cause: The user attempted to select data from a data source using // an invalid filter. A filter is a WHERE clause on data source // content. // *Action: Correct the filter and retry the operation. / 13762, 00000, "The %s ranking measure is invalid." // *Cause: The user attempted to select data from a data source // using an invlaid ranking measure. // A ranking measure must represent a valid numerical expression. // *Action: Correct the ranking measure and retry the operation. / 13763, 00000, "illegal ranking attribute \"%s\"" // *Cause: The user attempted to use an attribute element that // is not allowed in a ranking meseare. // *Action: Check the attribute in the ranking meseare and retry // the operation. / 13764, 00000, "Value \"%s\" is illegal as a result percentage." // *Cause: The user attempted to select data from a SQL Tuning Set using // an invalid result percentage. The result percentage must be // between 0 and 1. // *Action: Correct the result percentage value and retry the operation. / 13765, 00000, "Value \"%s\" is illegal for a result limit." // *Cause: The user attempted to select data from a SQL Tuning Set // using an invalid result limit. // A result limit must be a positive interger. // *Action: Correct the result limit value and retry the operation. / 13766, 00000, "A ranking measure is required." // *Cause: The user attempted to select data from a SQL Tuning Set // using a percentage argument without specifying a ranking measure. // *Action: Add a ranking measure or remove the percentage argument // and retry the operation. / 13767, 00000, "End snapshot ID must be greater than begin snapshot ID." // *Cause: The user attempted to select data from the workload repository // using an invalid snaphot ID range. // *Action: Adjust the snapshot ID range and retry the operation. / 13768, 00000, "Snapshot ID must be between %s and %s." // *Cause: The user attempted to select data from the workload repository // using a snaphot ID which does not exist. // *Action: Adjust the snapshot ID and retry the operation. / 13769, 00000, "Snapshots %s and %s do not exist." // *Cause: The user attempted to select data from the workload repository // using snapshots that do not exist. // *Action: Check the snapshot identifiers and retry the operation. / 13770, 00000, "Baseline \"%s\" does not exist." // *Cause: The user attempted to access a baseline that does not exsit. // *Action: Check the speelling of the baseline name and retry the operation. / 13771, 00000, "cannot obtain exclusive lock %s on \"SQL Tuning Set\" \"%s\" owned by user \"%s\"" // *Cause: Unexpected error from DBMS_LOCK.REQUEST. // *Action: This error should not normally occur. Check your system for // anomalies and retry the operation. If this error persists, // contact Oracle Support Services. / 13772, 00000, "unexpected deadlock on \"SQL Tuning Set\" \"%s\" owned by user \"%s\"" // *Cause: Unexpected error from DBMS_LOCK.REQUEST // *Action: This error should not normally occur. Check your system for // anomalies and retry the operation. If this error persists, // contact Oracle Support Services. / 13773, 00000, "insufficient privileges to select data from the cursor cache" // *Cause: The user attempted to perform an operation without having the // appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE. // *Action: Adjust the user's privileges and retry the operation. / 13774, 00000, "insufficient privileges to select data from the workload repository" // *Cause: The user attempted to perform an operation without having // the appropriate privileges on views DBA_HIST_BASELINE, // DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, // DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT. // *Action: Adjust the user's privileges and retry the operation. / 13775, 00000, "inconsistent datatype in input cursor" // *Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor. // All rows in the cursor must match type SQLSET_ROW. // *Action: Check the rows type in the cursor and retry the operation. / 13776, 00000, "User \"%s\" has not been granted the \"SELECT\" privilege on the \"SQL tuning set\" DBA views." // *Cause: The user attempted to read a SQL tuning set belonging to someone // else without having SELECT privilege on the DBA views // *Action: User should be granted the privilege or only access his own STS / 13777, 00000, "invalid list of attribute names" // *Cause: The user specified an attribute element that is not valid. // The only attributes that can be selected are NULL, // BASIC, TYPICAL, ALL or a comma separated list of the names including // EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN. // *Action: Adjust the attribute list and retry the operation. 13778, 00000, "no new name or owner specified for \"SQL Tuning Set\"" // *Cause: The user attempted to call remap_stgtab_sqlset without specifying // either a new SQL tuning set name or a new SQL tuning set owner // *Action: Specify at least one or the other argument as non-NULL / 13779, 00000, "invalid load option" // *Cause: The user attempted to call load_sqlset with a load option // that is different than INSERT, UPDATE and MERGE. // *Action: Adjust the load option and retry the operation. / /====================================== /= 13780-13799 reserved for SQLTune = /====================================== 13780, 00000, "SQL statement does not exist." // *Cause: The user attempted to tune a SQL statement that does not exist. // *Action: Verify the sql_id and the plan hash value of the statement and // retry the operation. / 13781, 00000, "cannot perform test-execute and explain plan operations on the automatic SQL tuning task" // *Cause: The user attempted to test-execute or generate explain plans for a SQL workload using the automatic SQL tuning task. // *Action: Verify the name of the tuning task and retry the operation. / 13783, 00000, "invalid tuning scope" // *Cause: The user attempted to specify a tuning task scope that is invalid. // The possible values are LIMITED or COMPREHENSIVE. // *Action: Check the scope value and retry the operation. // / 13784, 00000, "cannot accept SQL profiles for all statements in the \"%s\"" // *Cause: An attempt was made to accept SQL profiles for all statements in // the input workload. // *Action: Provide the object identifier corresponding to a statement // in the workload and retry the operation. / 13785, 00000, "missing target object for tuning task \"%s\"" // *Cause: The user attempted to perform an operation on a task without // specifying a target object or by using an invalid object identifier. // *Action: Check the identifier of the object and retry the operation. / 13786, 00000, "missing SQL text of statement object \"%s\" for tuning task \"%s\"" // *Cause: The user attempted to accept SQL profile for an object // that has not a SQL text associated to it. // *Action: Check the identifier of the object and retry the operation. / 13787, 00000, "missing SQL profile for statement object \"%s\" for tuning task \"%s\"" // *Cause: The user attempted to accept a SQL profile for an object // that has not a SQL profile associated to it. // *Action: Check the identifier of the object and retry the operation. / 13788, 00000, "invalid recommendation type" // *Cause: The user passed an invalid recommendation type in the rec_type // argument to script_tuning_task. Possible values are ALL or any // subset of a comma-separated list of PROFILES, STATISTICS // and INDEXES. // *Action: Check the rec_type arg and retry the operation. / 13789, 00000, "invalid process action" // *Cause: The user passed an invalid action to process a SQL statement. // Possible value is any subset of a comma-seperated list of // EXECUTE and EXPLAIN_PLAN. // *Action: Check the action argument and retry the operation. / 13790, 00000, "invalid value for time limit" // *Cause: The user passed an invalid value for the time limit argument. // *Action: Check the argument specified value and retry the operation. / 13791, 00000, "cannot resume a task created to process a single statement" // *Cause: An attempt was made to resume a task that was created // for a single SQL statement. A task can be resumed only if it is // used for a SQL Tuning Set. // *Action: No action required. / 13793, 00000, "invalid comparison metric" // *Cause: An invalid metric to compare SQL performance was specified. // *Action: Use execution statistics to compare the result of two executions // and optimizer_cost to analyze performance of two explain plan // actions. / 13794, 00000, "execution type mismatch" // *Cause: An attempt was made to analyze the performance of a SQL workload // using two executions that were generated using two different // actions. // *Action: check the name and type of task executions to analyze // and retry the operation. / 13795, 00000, "missing task execution" // *Cause: An insufficient number of valid task executions to analyze // the performance of a SQL workload were specified. // *Action: run the task to generate two executions of the same type // and retry the operation. / 13796, 00000, "invalid value %s specified for problem type" // *Cause: An invalid problem type was specified to the SQL diagnosis // advisor. Problem type should be one of the PROBLEM_TYPE_* // defined in 'admin/dbmsdiag.sql'. // *Action: Specify valid problem type. // / 13797, 00000, "invalid SQL Id specified, %s" // *Cause: Invalid SQL Id specified for conversion. // *Action: Specify valid SQL Id. / 13798, 00000, "Parameter %s cannot be NULL." // *Cause: A call to GET_THRESHOLD procedure was made without a required // parameter. // *Action: Specify a valid value for this parameter. / 13799, 00000, "threshold not found" // *Cause: No threshold was found with the specified threshold key. // *Action: No action required. / / ============================================== / 13800 - 13824 reserved for the SQL Tuning Base / ============================================== 13800, 00000, "concurrent DDL failure on SQL repository objects" // *Cause: A SQL repository object was the target of two concurrent // DDL operations. // *Action: Check the current state of the object and retry the operation // that failed. 13801, 00000, "invalid value for SQLTUNE_CATEGORY parameter" // *Cause: An invalid Oracle identifier was used as the value of the // parameter. // *Action: Specify the parameter conforming to the rules for Oracle // identifiers. 13802, 00000, "failed to purge SQL Tuning Base entry from sql$" // *Cause: An error occured while try to delete a SQL Tuning Base // object. // *Action: Look at the underlying error(s) on the error stack. / / ======================================= / 13825 - 13849 reserved for SQL profiles / ======================================= 13825, 00000, "missing SQL statement text for create SQL profile" // *Cause: No SQL text was provided to the create SQL profile operation. // *Action: Retry with properly specified SQL text. 13826, 00000, "empty SQL profile not allowed for create or update SQL profile" // *Cause: No attributes were specified to the create SQL profile operation. // *Action: Retry with at least one hint specified. 13827, 00000, "null or zero length attribute specified in SQL profile collection" // *Cause: One of the attributes within the SQL profile was not properly specified. // *Action: Retry with a fully specified SQL profile. 13828, 00000, "generated SQL profile name %s already exists" // *Cause: A SQL profile already exists with the name generated by the system. // *Action: Retry the operation as the generated name is time sensitive. 13829, 00000, "SQL profile named %s already exists" // *Cause: A SQL profile already exists with the name specified. // *Action: Specify a different name or drop the existing SQL profile. 13830, 00000, "SQL profile with category %s already exists for this SQL statement" // *Cause: A SQL profile already exists for the given SQL statement and category. // *Action: Drop or update the existing SQL profile. 13831, 00000, "SQL profile name specified is invalid" // *Cause: An invalid SQL profile name was specified. // *Action: Look for the underlying error on the error message stack. 13832, 00000, "category name specified is invalid" // *Cause: An invalid category name swas pecified. // *Action: Look for the underlying error on the error message stack. 13833, 00000, "SQL profile named %s doesn't exist" // *Cause: A SQL profile name was specified that doesn't exist. // *Action: Verify the name of the SQL profile. 13834, 00000, "name of SQL profile to be cloned must be provided" // *Cause: A SQL profile name was not provided as the from target of a clone // SQL profile operation. // *Action: Provide the name of the SQL profile being cloned. 13835, 00000, "invalid attribute name specified" // *Cause: An invalid attribute name was specified for an alter SQL profile // operation. // *Action: Verify the name of the attribute. 13836, 00000, "invalid attribute value specified" // *Cause: An invalid attribute value was specified for an alter SQL profile // operation. // *Action: Verify the attribute value. 13837, 00000, "invalid HASH_VALUE" // *Cause: An invalid HASH_VALUE was passed to a create SQL profile operation // *Action: Verify the HASH_VALUE. 13838, 00000, "invalid ADDRESS value" // *Cause: An invalid ADDRESS value was passed to a create SQL profile operation. // *Action: Verify the ADDRESS value. 13839, 00000, "V$SQL row doesn't exist with given HASH_VALUE and ADDRESS." // *Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL profile // operation doesn't coorespond to an existing V$SQL entry. // *Action: Verify the HASH_VALUE and ADDRESS in V$SQL. 13840, 00000, "Concurrent DDL Error in create SQL profile operation." // *Cause: A concurrent DDL operation was performed during a create or replace // sql profile operation. // *Action: Try operation again 13841, 00000, "SQL profile named %s already exists for a different signature/category pair" // *Cause: A SQL profile already exists with the name specified under a // different signature/category pair so it cannot be replaced, even // with FORCE specified. // *Action: Specify a different name or drop the existing SQL profile. 13842, 00000, "no SELECT privilege on DBA_SQL_PROFILES" // *Cause: A user has tried to perform an operation that requires SELECT // privileges on the DBA_SQL_PROFILES view. // *Action: Either perform the operation as another user or get the privilege 13843, 00000, "no SQL profile with name like \"%s\" exists for category like \"%s\"" // *Cause: A user tried to perform an operation by specifying a profile name/ // category filter that did not target any profiles // *Action: Try a different filter after checking the profile name/category 13844, 00000, "no new SQL profile name or category specified." // *Cause: A user called remap_stgtab_sqlprof without specifying new values // for the sql profile name or category. At least one is required. // *Action: Specify either a new profile name, or a new category, or both 13845, 00000, "invalid SQL profile XML specification provided" // *Cause: The supplied XML specification for the SQL profile did not adhere // to the proper schema. // *Action: Check the syntax and try again. 13846, 00000, "Cannot create SQL plan baseline on the given plan" // *Cause: There are either multiple plans exist for the given value or the // plan is not reproducible. // *Action: Call Oracle Support. 13847, 00000, "The plan with plan hash value %s does not exist" // *Cause: The give plan does not exist. // *Action: Check the available plans. / / ============================================= / 13850 - 13899 reserved for end-to-end tracing / ============================================= 13850, 00000, "Tracing for client identifier %s is not enabled" // *Cause: Attempt to disable a client identifier tracing which // was never enabled // *Action: Supply correct client identifier / 13851, 00000, "Tracing for client identifier %s is already enabled" // *Cause: Attempt to enable a client identifier tracing which // has been already enabled // *Action: Supply correct client identifier, or disable and re-enable // tracing with different bind/wait options / 13852, 00000, "Tracing for service(module/action) %s is not enabled" // *Cause: Attempt to disable a service-level tracing which // was never enabled // *Action: Supply correct service(module/action) name / 13853, 00000, "Tracing for service (module/action) %s is already enabled" // *Cause: Attempt to enable a service-level tracing which // has been already enabled // *Action: Supply correct service(module/action), or disable and re-enable // tracing with different bind/wait options / 13854, 00000, "Tracing for service(module/action) %s on instance %s is not enabled" // *Cause: Attempt to disable a service-level tracing which // was never explicitly enabled on a specific instance // *Action: Supply correct service(module/action) name / 13855, 00000, "Tracing for service (module/action) %s on instance %s is already enabled" // *Cause: Attempt to enable a service-level tracing which // has been already enabled on a specific instance // *Action: Supply correct service(module/action), or disable and re-enable // tracing with different bind/wait options / 13856, 00000, "Service name must be specified" // *Cause: Omitting service name while enabling/disabling tracing or // aggregation // *Action: Supply the service name / 13857, 00000, "Invalid module name" // *Cause: Module name is too long (exceeding 48 characters) // *Action: Supply correct name / 13858, 00000, "Invalid action name" // *Cause: Action name is too long (exceeding 32 characters) // *Action: Supply correct name / 13859, 00000, "Action cannot be specified without the module specification" // *Cause: Action name is specified, but the module name is not // *Action: Supply the module name / 13860, 00000, "Invalid service name" // *Cause: Service name is too long (exceeding 64 characters) // *Action: Supply correct name / 13861, 00000, "Statistics aggregation for client identifier %s is already enabled" // *Cause: Attempt to enable a client identifier aggregation which // has been already enabled // *Action: Supply correct client identifier / 13862, 00000, "Statistics aggregation for client identifier %s is not enabled" // *Cause: Attempt to disable a client identifier statistics aggregation which // was never enabled // *Action: Supply correct client identifier / 13863, 00000, "Statistics aggregation for service(module/action) %s is not enabled" // *Cause: Attempt to disable a service-level statistics aggregation which // was never enabled // *Action: Supply correct service(module/action) name / 13864, 00000, "Statistics aggregation for service (module/action) %s is already enabled" // *Cause: Attempt to enable a service-level statistics aggregation which // has been already enabled // *Action: Supply correct service(module/action) / 13865, 00000, "Module name must be specified" // *Cause: Attempt to enable/disable a service-level statistics aggregation // without a module specification // *Action: Supply module name / 13866, 00000, "Client identifier must be specified" // *Cause: Omitting client identifier while enabling/disabling tracing or // aggregation // *Action: Supply the client identifier / 13867, 00000, "Database-wide SQL tracing is already enabled" // *Cause: Attempt to enable a database-level tracing which // has been already enabled // *Action: Disable and re-enable tracing with different bind/wait options / 13868, 00000, "Instance-wide SQL tracing on instance %s is not enabled" // *Cause: Attempt to disable a service-level tracing which // was never explicitly enabled on a specific instance // *Action: No action required / 13869, 00000, "Instance-wide SQL tracing on instance %s is already enabled" // *Cause: Attempt to enable an instance-level tracing which // has been already enabled on a specific instance // *Action: Disable and re-enable tracing with different bind/wait options / 13870, 00000, "Database-wide SQL tracing is not enabled" // *Cause: Attempt to disable a database-level tracing which // was never enabled // *Action: No action required / 13871, 00000, "Invalid instance name" // *Cause: Instance name is too long (exceeding 16 characters) // *Action: Supply correct name / / 13900 - 13949 reserved for threshold-based alert / 13900, 00000, "missing or invalid parameter %s" // *Cause: A call to SET_THRESHOLD procedure was either missing a parameter, // or the parameter was invalid. // *Action: Specify a valid value for this parameter. / 13901, 00000, "Object %s was not found." // *Cause: An object name was passed to SET_THRESHOLD procedure that did not // map to a valid object. // *Action: Specify a valid object name. / 13902, 00000, "The specified file %s is not a data file." // *Cause: The object name was passed to a SET_THRESHOLD procedure that did // not map to a valid data file. // *Action: Specify a valid data file name. / 13903, 00000, "Invalid combination of %s threshold value and operator." // *Cause: A non-positive number was used for "Blocked User Session // Count" metrics while operator contains equal. // *Action: Use a positive number for the threshold value or use "greater than" // operator. / 13904, 00000, "The file has been dropped and recreated during the procedure call." // *Cause: The file on which threshold is specified was dropped and // recreated during the procedure call. // *Action: Retry this operation. / 13905, 00000, "Critical or warning threshold have incorrect values" // *Cause: The tablespace threshold values can be in the range 0 to 100 // only. // *Action: Check the threshold values / 13906, 00000, "The tablespace is not of the right type." // *Cause: An attempt was made to set a threshold on dictionary-managed // tablespaces. // *Action: Check the tablespace type and reissue the command. / 13907, 00000, "Threshold value is invalid." // *Cause: An attempt was made to specify an invalid value for critical // or warning thresholds. // *Action: Use non-negative integers only for threshold values. / 13908, 00000, "Invalid combination of metrics id and object type parameters." // *Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters. // *Action: Specify a valid combination of metrics id and object type // parameters. / 13909, 00000, "Invalid combination of threshold value and operator." // *Cause: An attempt was made to specify an invalid combination of threshold // value and operator. // *Action: Check the operator and threshold values and reissue statement. / 13910, 00000, "Parameter %s cannot be NULL." // *Cause: An attempt was made to call GET_THRESHOLD procedure without a // required parameter. // *Action: Specify a valid value for this parameter. / 13911, 00000, "Threshold not found" // *Cause: The threshold did not exist with the specified threshold key. // *Action: No action required. / 13912, 00000, "Critical threshold value is less than warning threshold value." // *Cause: An attempt was made to call SET_THRESHOLD procedure with the // critical threshold value less than the warning threshold value. // *Action: Check the threshold values and reissue the statement. / 13913, 00000, "The threshold cannot be set when SYSAUX is offline." // *Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was // offline. // *Action: Call SET_THRESHOLD procedure when SYSAUX is online. / 13914, 00000, "Threshold notification failed." // *Cause: An error occurred when sending notification for this threshold. // *Action: Make sure you have enough space on SYSAUX tablespace and retry // this operation. / 13915, 00000, "Critical byte based free space threshold value is greater than warning threshold value." // *Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based // critical threshold value greater than the warning threshold value. // *Action: Check the threshold values and reissue the statement. / 13916, 00000, "Invalid value \"%s\" specified for parameter \"%s\"" // *Cause: An invalid value was specified for the the given parameter. // *Action: Correct the value being specified for the parameter. / 13917, 0000, "Posting system alert with reason_id %s failed with code [%s] [%s]" // *Cause: Connection to the database is dead, or invalid parameter // to alert routine. // *Action: If this condition repeats, please contact Oracle Support. / 13918, 0000, "Updating system alert with reason_id %s failed; previous alert not found" // *Cause: System Error: An attempt to update a system alert failed. // The alert was improperly cleared from WRI$_ALERT_OUTSTANDING. // *Action: Do not delete from WRI$_ALERT_OUTSTANDING. // If this condition repeats, please contact Oracle Support. / 13919, 00000, "Cannot specify values for parameter \"%s\" and for parameter \"%s\"" // *Cause: Can only specify a value for one or the other. // *Action: Pass just one of the parameters. / 13920, 00000, "Threshold cannot be set when database is in read-only mode." // *Cause: SET_THRESHOLD procedure was called when database was open in read-only // mode. // *Action: Call SET_THRESHOLD procedure when database is open in read/write mode. / / / 13950 - 13969 reserved for MMON infrastructure / 13950, 00000, "MMON action time limit exceeded" // *Document: NO // *Cause: MMON action did not complete within the system specified // time frame. // *Action: None. / 13951, 00000, "MMON sub-action time limit exceeded" // *Cause: MMON sub-action did not complete within the system specified // time frame. // *Action: None. / / / 13970-13998 reserved for common reporting framework / 13970, 00000, "Invalid name of \"%s\" given" // *Cause: Passed an invalid component, report, or transformation name // to the framework. Names must be alphanumeric and can contain the // underscore (_) character. // *Action: Try again with a valid name / 13971, 00000, "%s \"%s\" unknown" // *Cause: Passed an unknown component, report, or transformation to the // framework. // *Action: Give a different name / 13972, 00000, "%s \"%s\" unknown for %s \"%s\"" // *Cause: An object with the first name is unknown within the naming scope // of the second name // *Action: Change the parameters passed in or register the proper object / 13973, 00000, "%s unknown for %s \"%s\"" // *Cause: An object is unknown within the given naming scope // *Action: Change the parameters passed in or register the proper object / 13974, 00000, "%s with name \"%s\" already exists" // *Cause: An object with the given name already exists // *Action: Give a different name / 13975, 00000, "%s with name \"%s\" already exists for %s \"%s\"" // *Cause: An object with the first name already exists within the naming // scope of the second name // *Action: Give a different name / 13976, 00000, "Improperly-formed report tag" // *Cause: The top-level report tag was not built properly // *Action: Make sure that the report tag is built using the common tag // library function / 13977, 00000, "Invalid content type" // *Cause: An invalid content type was passed to the register format API // *Action: Correct your code to use the values in dbmsrep.sql / 13978, 00000, "Invalid reference string parameter or value" // *Cause: An invalid parameter/value was passed to a dbms_report API // *Action: Ensure that the parameter names and values are alphanumeric. / 13979, 00000, "Filename too long" // *Cause: An invalid file name was passed to STORE_FILE // *Action: Ensure that the filename is less than 500 bytes / 13980, 00000, "Invalid file URL" // *Cause: A URL with invalid syntax was provided, either directly to the // function or via an XML IMPORT or INCLUDE. // *Action: Check the URL. / 13981, 00000, "Invalid file URL or path prefix" // *Cause: Either a URL or path prefix with invalid syntax was provided. // *Action: Check the URL / 13982, 00000, "Could not find file at URL provided" // *Cause: The file requested could not be found in the given location. // *Action: Check the URL provided. / 13983, 00000, "Missing tag from HTML" // *Cause: An HTML document was passed to the function missing its // tag. // *Action: Check the HTML source. / 13984, 00000, "Invalid reference string" // *Cause: The given reference string could not be parsed. // *Action: Check the reference string syntax. / 13985, 00000, "Invalid URL provided to servlet" // *Cause: An invalid URL was provided to the servlet. // *Action: Check the URL. / 13986, 00000, "Error \%s received from XPath engine" // *Cause: An error was received from the xpath library during an xpath // operation. // *Action: Check xmlerr.h to understand the cause of the error. / 13987, 00000, "Invalid input to build common <%s> tag" // *Cause: Invalid input was given when attempting to build a common tag. // *Action: Check the function input to make sure all necessary information // is given. / 13988, 00000, "Invalid input given to variable argument list report function." // *Cause: An invalid parameter was provided to one of the report // framework variable argument list functions. // *Action: Check the function input and try again. / 13989, 00000, "Invalid input given to structured argument list report function." // *Cause: An invalid parameter was provided to one of the report // framework structured argument list functions. // *Action: Check the function input and try again. / 13990, 00000, "Invalid tag name given to common tag callout function." // *Cause: An invalid tag name was provided to the report // framework common tag callout function. // *Action: Check the function input and try again. / /13999, 00000, "%s" // *Cause: This is an internal Server Manageability Error // *Action: Contact Oracle Support Services / / / 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 1048575 (1024K-1). // *Action: Reduce number of partitions to not exceed 1048575 (1024K -1). 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 tbl$or$idx$part$num" // *Document: NO // *Cause: tbl$or$idx$part$num was supplied with fewer than 5 // arguments which is illegal // *Action: Supply tbl$or$idx$part$num with table name, index // dictionary object number or 0, dimension number, composite // partition number (if dimension is 2) 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 index-organized table" // *Cause: An attempt was made to issue a CREATE or ALTER TABLE // command on a non-partitioned IOT, but the command contains an // option that is legal only for partitioned index-organized 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, "submitted alter index partition/subpartition operation is not valid for local partitioned index" // *Cause: User attempted to either drop, split, add or coalesce a partition or // a subpartition 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 tbl$or$idx$part$num must be an integer constant" // *Document: NO // *Cause: Second argument to tbl$or$idx$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 tbl$or$idx$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 tbl$or$idx$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 tbl$or$idx$part$num was not partitioned // *Action: Second argument passed to tbl$or$idx$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 tbl$or$idx$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 tbl$or$idx$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 // tbl$or$idx$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 and editioning views" // *Cause: An attempt was made to use a partition-extended object name // with an object which was not a table or an editioning view. // *Action: Avoid using partition-extended name syntax with objects // which are not tables or editioning views 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 a GLOBAL partitioned index 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/HASH clause along with any partition // descriptions 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 is a temporary 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 // - it is created with row dependency and the partitioned table is not // - it is created without row dependency and the partitioned table is // *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. 14137, 00000, "Table in partially dropped state, submit DROP TABLE PURGE" // *Cause: An attempt was made to access a partitioned table in a partially // dropped state. // *Action: Submit DROP TABLE
PURGE to drop the table. 14138, 00000, "An unexpected error encountered during drop table operation" // *Cause: Drop table encountered an unexpected error. // *Action: a. Submit drop table
purge, or // b. If the situation described in the next error on the stack // can be corrected, do so. // c. Contact Oracle Support. 14139, 00000, "table %s.%s is already in read-only mode" // *Cause: an attempt was made to set a read-only table in read-only mode // *Action: this DDL can only be executed on a read/write table 14140, 00000, "table %s.%s is already in read/write mode" // *Cause: an attempt was made to set a read/write table in read/write mode // *Action: this DDL can only be executed on a read-only table 14141, 00000, "ALTER INDEX VISIBLE|INVISIBLE may not be combined with other operations" // *Cause: ALTER INDEX statement attempted to combine a VISIBLE|INVISIBLE // operation with some other operation which is illegal // *Action: Ensure that VISIBLE|INVISIBLE operation is the sole operation // specified in ALTER INDEX statement 14142, 00000, "ALTER INDEX VISIBLE|INVISIBLE may not be used with certain types of index" // *Cause: Using the ALTER INDEX VISIBLE|INVISIBLE statement on certain types // of indexes (IOT-TOP, Cluster indexes) is illegal. // *Action: Remove the option VISIBLE|INVISIBLE. 14143, 00000, "CREATE INDEX INVISIBLE may not be used with this type of index" // *Cause: Certain types of indexes (IOT-TOP, Cluster indexes) cannot // be created invisible. // *Action: Remove the option INVISIBLE 14144, 00000, "arguments to tbl$or$idx$part$num must not be bind variables" // *Document: NO // *Cause: Second, third or fourth argument to tbl$or$idx$part$num was found // to be a bind variable and not an integer constant. // *Action: Ensure that the argument passed to tbl$or$idx$part$num // is an integer constant and not a bind variable. 14145, 00000, "only one UNUSABLE clause may be specified" // *Cause: UNUSABLE was specified more than once. // *Action: Remove all but one of the UNUSABLE clauses and reissue the statement. 14146, 00000, "Old CONNECT BY does not support partitioned tables" // *Cause: The query used the old CONNECT BY clause on a partitioned object. // *Action: Disable old CONNECT BY by disabling the _old_connect_by_enabled parameter. / / 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, LIST, SYSTEM, or // Composite Range-Hash/List/Range (R+H/L/R). // *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-1048575) // *Action: Specify a number between 1 and 1024K-1 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 | SUBPARTITION TEMPLATE] clause" // *Cause: number-of-subpartitions clause contained in CREATE TABLE or // CREATE INDEX statement specified a number of subpartitions // outside of legal range (1-1048575) // *Action: Specify a number between 1 and 1024K-1 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 1048575. // *Action: Reduce number of subpartitions to not exceed 1024K-1. 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 <(sub)partition-description> clause in CREATE TABLE or CREATE INDEX" // *Cause: A request was made to generate default partition description(s) // (possibly via PARTITIONS ) while at // the same time specified <(sub)partition-description> 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 an object 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 Hash or Composite Range Hash table" // *Cause: STORE-IN (Tablespace list) clause was used while creating a local // index on a range/list/composite range list partitioned table // *Action: Do not use the STORE_IN (Tablespace list) clause while creating // a local index on range/list/composite range list partitioned table 14178, 00000, "STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes" // *Cause: STORE IN (DEFAULT) is valid only for local indexes. // *Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove // STORE IN clause and specify tablespaces individually for each // index partition. 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 EXTENT may not be specified for composite partitioned object" // *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement // issued against a composite partitioned index which is illegal. // *Action: Remove the illegal option. If you want to add // storage to individual [sub]partitions,the ALLOCATE EXTENT clause // may be specified with ALTER TABLE OR INDEX MODIFY [SUB]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. 14196, 00000, "Specified index cannot be used to enforce the constraint." // *Cause: The index specified to enforce the constraint is unsuitable // for the purpose. // *Action: Specify a suitable index or allow one to be built automatically. 14197, 00000, "dimension values 3,4 cannot be used with domain indexes" // *Document: NO // *Cause: A dimension value of 3 or 4 was used in conjunction with a // domain index // *Action: Do not use dimension value 3,4 for domain indexes in // tbl$or$idx$part$num function 14198, 00000, "rowid column must refer to table specified in 1st parameter" // *Document: NO // *Cause: The table name specified in the 1st parameter and the table that // the rowid column belongs to are not the same // *Action: Make sure the table name in the 1st parameter is the same as the // table that rowid column belongs to 14199, 000000, "Disable fix for 4900129" // *Document: NO // *Cause: // *Action: 14200, 00000, "Only one parameter can be specified and it must be constant or bind" // *Document: NO // *Cause: When dimension value is 5, only 1 parameter can be specified and // it must be a constant or bind variable. // *Action: Make sure the parameter is a constant or bind variable. / 14201-14239 reserved for errors which may be generated during / processing of DDL statements specific to range-range / partitioned tables 14201, 00000, "specified subpartition bound is too long" // *Cause: Length of a linear key representation of a high bound of a table // subpartition being added or along which an existing table or // index subpartition is being split exceeded the legal limit (4K). // *Action: Change the representation of a subpartition high bound to bring // its length within legal limit. 14202, 00000, "subpartition bound of subpartition \"%s\" is too high" // *Cause: High bound of the specified subpartition displayed in this // message did not collate lower than that of the subsequent // subpartition. // *Action: Ensure that high bound of every subpartition (except for the last // one) collates lower than that of a subsequent subpartition. 14203, 00000, "subpartition bound of subpartition \"%s\" is too long" // *Cause: Length of linear key representation of a high bound of the // specified subpartition displayed in this message exceeded the // legal limit (4K). // *Action: Change the representation of a subpartition high bound to bring // its length within legal limit. 14204, 00000, "subpartition bound of subpartition number %s is too high" // *Cause: High bound of the specified subpartition displayed in this message // did not collate lower than that of the subsequent subpartition. // *Action: Ensure that high bound of every subpartition (except for the last // one) collates lower than that of a subsequent subpartition. 14205, 00000, "subpartition bound of subpartition number %s is too long" // *Cause: Length of linear key representation of a high bound of the // specified subpartition displayed in this message exceeded the // legal limit (4K). // *Action: Change the representation of a subpartition high bound to bring // its length within legal limit. 14206, 00000, "table is not subpartitioned by List or Range methods" // *Cause: A subpartition maintenance operation such as ALTER TABLE DROP|SPLIT|MERGE // SUBPARTITION can only be performed on List or Range subpartitioned objects // *Action: Issue the command only against a List or Range subpartitioned object. 14207, 00000, "maximum number of subpartitioning columns is 16" // *Cause: number of columns in a subpartitioning column list exceeded // the legal limit of 16 // *Action: modify subpartitioning column list so that it consists of at // most 16 columns 14208, 00000, "lower-bound subpartition must be specified first" // *Cause: A higher-bound subpartition was specified before the lower-bound // subpartition in ALTER TABLE MERGE SUBPARTITIONS statement. // *Action: Specify lower-bound subpartition first and then higher-bound subpartition 14209, 00000, "subpartitions being merged are not adjacent" // *Cause: Attempted to merge two subpartitions that are not adjacent // to each other. // *Action: Specify two subpartitions that are adjacent 14210, 00000, "cannot reuse lower-bound subpartition as resulting subpartition" // *Cause: Attempted to reuse the lower-bound subpartition of the subpartitions // being merged. // *Action: Specify new resulting subpartition name or reuse the higher-bound // subpartition only 14211, 00000, "subpartition bound must collate higher than that of the last subpartition" // *Cause: Subpartition bound specified in ALTER TABLE MODIFY PARTITION ADD SUBPARTITION // statement did not collate higher than that of the partition's // last subpartition. // *Action: Ensure that the subpartition bound of the subpartition to be added // collates higher than that of the table partition's last subpartition. 14212, 00000, "subpartition cannot be split along the specified high bound" // *Cause: Attempted to split a subpartition along a bound which // either collates higher than that of the subpartition to be split or // lower than that of a subpartition immediately preceding the one // to be split // *Action: Ensure that the bound along which a subpartition is to be split // collates lower than that of the subpartition to be split and // higher than that of a subpartition immediately preceding the one // to be split 14213, 00000, "VALUES LESS THAN or AT clause cannot be used for List subpartitioned tables" // *Cause: VALUES LESS THAN or AT clause was used for List // subpartitioned tables // *Action: Use VALUES () clause for List subpartitioned tables 14214, 00000, "VALUES () cannot be used for Range subpartitioned tables" // *Cause: VALUES () clause was used for Range // subpartitioned tables // *Action: Use VALUES LESS THAN or AT clause with Range subpartitioned tables 14215, 00000, "subpartition bound list contains too many elements" // *Cause: Subpartition bound list contained more elements than there are // subpartitioning columns // *Action: Ensure that the number of elements in subpartition bound list is // equal to the number of subpartitioning columns of the table or index 14216, 00000, "subpartition bound list contains too few elements" // *Cause: Subpartition bound list contained fewer elements than there are // subpartitioning 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 14217, 00000, "VALUES () clause expected" // *Cause: VALUES () clause was not specified for the list // subpartition being added // *Action: Specify a VALUES () clause 14218, 00000, "Invalid operation for object without a segment" // *Cause: The object (table or index or lob) did not have a segment. // *Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command. 14220, 00000, "Invalid operation for object without a segment" // *Cause: Attempted to modify storage or allocate an extent for an object // (table or LOB or index) without a segment. // *Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command. 14221, 00000, "Dictionary managed tablespace cannot be used for this operation" // *Cause: Attempted to create an index or add a LOB column in a dictionary // managed tablespace to a table without a segment. // *Action: Specify a locally managed tablespace OR create segments for the // table with the ALTER TABLE ALLOCATE EXTENT command. 14223, 00000, "Deferred segment creation is not supported for this table" // *Cause: The SEGMENT CREATION DEFERRED clause was specified in the // CREATE TABLE statement. // *Action: Remove the SEGMENT CREATION DEFERRED clause. 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, LIST, // 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, List, or Hash method" // *Document: NO // *Cause: The table in the MOVE PARTITION operation is partitioned by // method other than Range, System, List, or Hash method // *Action: Ensure that the table is partitioned by Range, System, List, or // Hash method 14244, 00000, "illegal operation for a Composite Range/System partitioned table" // *Document: NO // *Cause: any operation done to a 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, List, Composite Range or Composite List method" // *Cause: The table was not partitioned by Range, List, Composite Range // or Composite List method. // *Action: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS // command is only valid for table partitioned by Range, List, // Composite Range or Composite List methods. Ensure that the table // is partitioned appropriately. 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, List, System, or Hash partition" // *Cause: User attempt to move a partition that is not a Range,List,System, or Hash // partition which is illegal // *Action: Specify MOVE PARTITION for a Range,List,System, 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,List,System, or Hash partition" // *Cause: User attempt to exchange a partition with a non-partitioned table // but the specified partition is not a Range,List,System, or Hash partition // which is illegal // *Action: Specify EXCHANGE PARTITION for a Range,List,System, or Hash partition only 14270, 00000, "table is not partitioned by Range, System, 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,List,System, or Hash method which is illegal. // *Action: Ensure that the table is partitioned by Range,List,System, or Hash method 14271, 00000, "table is not partitioned by Composite Range method" // *Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL // INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not // partitioned by Composite Range method which is illegal. // *Action: Ensure that the table is partitioned by Composite Range // 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 hash partitioned table or index" // *Cause: A COALESCE PARTITION command was issued when there is only // one partition in the table or index, which is illegal // *Action: Ensure that there is at least one partition. // Drop the table or index 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. 14299, 00000, "total number of partitions/subpartitions exceeds the maximum limit" // *Cause: The total number of combined fragments specified in partitions // /subpartitions exceeds 1048575. // *Action Reissue the statement with fewer number of fragments 14300, 00000, "partitioning key maps to a partition outside maximum permitted number of partitions" // *Cause: The row inserted had a partitioning key that maps to a partition number greater than 1048575 // *Action Ensure that the partitioning key falls within 1048575 partitions or subpartitions. 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 524288 list values // *Action: Reduce the number of values to not exceed 524288 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 524288 list values // *Action: Reduce number of values to less than 524288. 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 partitioned 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 / 14318, 00000, "DEFAULT partition must be last partition specified" // *Cause: A partition description follows the one describing the default // partition // *Action: Ensure that the DEFAULT partition is the last partition description / 14319, 00000, "DEFAULT cannot be specified with other values" // *Cause: DEFAULT keyword has been specified along with other // values when specifying the values for a list partition // *Action: Ensure that if DEFAULT is specified, it is the only value specified / 14320, 00000, "DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT" // *Cause: DEFAULT keyword has been specified when doing a ADD VALUES or // DROP VALUES or SPLIT partition or subpartition. // *Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or // SPLIT partition/subpartition operation. / 14321, 00000, "cannot add/drop values to DEFAULT partition" // *Cause: A ADD/DROP VALUES operation is being done on the default partition // *Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition / 14322, 00000, "DEFAULT partition already exists" // *Cause: A partition already exists with DEFAULT value // *Action: / 14323, 00000, "cannot add partition when DEFAULT partition exists" // *Cause: An ADD PARTITION operation cannot be executed when a partition // with DEFAULT values exists // *Action: Issue a SPLIT of the DEFAULT partition instead / 14324, 00000, "values being added already exist in DEFAULT partition" // *Cause: An ADD VALUE operation cannot be executed because the values // being added exist in the DEFAULT partition // *Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split // partition into the partition to which values need to be added / 14325, 00000, "only LOCAL indexes may be specified in this clause" // *Cause: A global index has been specified in the UPDATE INDEXES (..) clause // *Action: Only specify local indexes when using this clause / 14326, 00000, "Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause" // *Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified // in the UPDATE INDEXES (..) clause // *Action: Do not specify any of these indexes when using this clause / 14327, 00000, "Some index [sub]partitions could not be rebuilt" // *Cause: The first phase (partition DDL and index [sub]partition placement) // completed successfully. During the second phase, some of the index // [sub]partitions could not be rebuilt. // *Action: Search the alert log for the string DBMS_INDEX_UTL. // Check the error associated with each of the [sub]partitions // that could not be rebuilt and take the appropriate corrective // action. / 14328, 00000, "Allow UPDATE INDEXES clause for PIOTs. To be used for testing" // *Document: NO // *Cause: // *Action: // Level 1+ Allow UPDATE INDEXES clause for IOTs. / 14329, 00000, "domain index [sub]partitions cannot be renamed in this clause" // *Cause: The user tried to rename a domain index [sub]partition in the // UPDATE INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION // operation. This is not allowed. // *Action: Leave the name blank or use the same name. / 14330, 00000, "Cannot drop a partition of a global hash-partitioned index" // *Cause: An attempt was made to drop a partition of a hash-partitioned global // index. // *Action: Try COALESCE PARTITION instead. / / 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 14410, 00000, "RPI LOCK TABLE issued to table referenced through synonym" // *Document: NO // *Cause: RPI LOCK TABLE statement was issued to acquire DML locks before // KGL locks for a table referenced through a synonym. This error // is never returned to user. // *Action: nothing to be done, error should never be returned to user 14411, 00000, "The DDL cannot be run concurrently with other DDLs" // *Cause: Another conflicting DDL was already running. // *Action: Retry after the conflicting DDL has finished. 14412, 00000, "Error occurred during execution of partition pruning subquery" // *Document: NO // *Cause: The partition pruning subquery could not be run with the SCN of // the top level query. // *Action: N/A. Error should never be returned to user. / / 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 Nested Table column in a Temporary table" // *Cause: An attempt made to create a 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. 14460, 00000, "only one COMPRESS or NOCOMPRESS clause may be specified" // *Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more // than once, or both COMPRESS and NOCOMPRESS were specified. // *Action: specify each desired COMPRESS or NOCOMPRESS clause option only once. 14461, 00000, "cannot REUSE STORAGE on a temporary table TRUNCATE" // *Cause: REUSE STORAGE was specified with TRUNCATE on a temporary table. // This is unsupported as it is meaningless. // *Action: Specify DROP STORAGE instead (which is the default). 14462, 00000, "cannot TRUNCATE temporary table in an autonomous transaction which is already in use by the parent transaction" // *Cause: An attempt was made to TRUNCATE a temporary table in an autonomous // transaction which is already in use by the parent transaction. // *Action: Make sure the temporary table is not being used by the parent // transaction before trying to TRUNCATE in an autonomous transaction. 14463, 00000, "OPERATIONS keyword not specified" // *Cause: OPERATIONS keyword was not specified in the Compression Clause. // *Action: specify OPERATIONS in the Compression Clause. 14464, 00000, "Compression Type not specified" // *Cause: Compression Type was not specified in the Compression Clause. // *Action: specify Compression Type in the Compression Clause. 14465, 00000, "Fast-Split is not possible on these partitions" // *Cause: The Fast-Split event was forced in this session. // *Action: Disable the event that forces Fast-Split. / / 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. 14525, 00000, "Fast Split event" // *Document: NO // *Cause: // *Action: // Level Action // 0x0001 Dont try fast split // 0x0002 Tracing for why fast split failed 14526, 00000, "This event is no longer used." // *Document: NO // *Cause: // *Action: // However don't reuse the event because there might be installations // have it set. 14527, 00000, "Allow ROWID datatype for partitioning key columns" // *Document: NO // *Cause: // *Action: // Level 1+ Allow partitioning on columns having ROWID datatype. // Note: remove this event once we fully support // partitioning on columns with ROWID datatype in 10g+. 14528, 00000, "simulated crash during drop table optimization" // *Document: NO // *Cause: Oracle internal testing only // *Action: Never set this event (to be used only for internal testing) / 14529, 00000, "copy hakan factor during ctas at facilitate exchange partition" // *Document: NO // *Cause: Oracle internal testing only // *Action: Never set this event unless running into bug 3747472 14530, 00000, "row mismatches found in table %s.%s and index %s.%s" // *Document:YES // *Cause: rows in table and index inconsistent // *Action: run complete analyze to determine corrupt rows 14531, 00000, "Event to enable Hash composite partitioning for 11.0.0.0" // *Document: NO // *Cause: Oracle internal testing only // *Action: Never set this event (to be used only for internal testing) 14532, 00000, "Event for bug 5618049" // *Document: NO // *Cause: Needs to be set to turn on fix for 5618049 // *Action: 14533, 00000, "Event for ALTER TABLE enhancements for code point semantics" // *Document: NO // *Cause: // *Action: Needs to be set to turn on fix for bug 5952255 14534, 00000, "Event for bug 5996430 fix to be turned on" // *Document: NO // *Cause: // *Action: Needs to be set to turn on fix for bug 5996430 14536, 00000, "Event to turn on row movement during CREATE TABLE" // *Document: NO // *Cause: // *Action: / /============================================================================ / 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. 14554, 00000, "cannot perform requested operation during database startup " // *Cause: Requested operation requires the Cost Based Optimizer(CBO) which is // not available during database startup. Features like partitioning, // IOTs, grouping sets, and flashback cursor require the CBO. // *Action: Retry the query after the database is open. /============================================================================ / 14601 - 14700 reserved for 9.0.2 partitioning project / / Begin messages for 9.0.2 partitioning changes /============================================================================ / 14601, 00000, "Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template" // *Cause: Cannot specify these clauses while specifying a template // *Action: Correct the subpartition template clause. 14602, 00000, "SUBPARTITION TEMPLATE is legal only for a composite partitioned table" // *Cause: SUBPARTITION TEMPLATE can be specified only for composite // partitioned tables // *Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or // non-composite partitioned tables. 14603, 00000, " [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables" // *Cause: This syntax is valid only if subpartitioning dimension is hash // *Action: 14604, 00000, "During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified" // *Cause: Once a subpartition template has been specified during a CREATE // TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere // else // Action: Remove either the SUBPARTITIONS | STORE IN or remove the // SUBPARTITION TEMPLATE clause 14605, 00000, "Name missing for subpartition / lob segment in template" // *Cause: A subpartition / lob segment was not specified a name in the // template descriptions // *Action: All subpartitions / lob segments must have names specified in the // template 14606, 00000, "Tablespace was specified for previous subpartitions in template but is not specified for %s" // *Cause: Tablespaces may either be specified for all subpartitions or must // not be specified for any subpartitions // *Action: Either specify tablespaces for all or for none of the subpartitions 14607, 00000, "Tablespace was not specified for previous subpartitions in template but is specified for %s" // *Cause: Tablespaces may either be specified for all subpartitions or must // not be specified for any subpartitions // *Action: Either specify tablespaces for all or for none of the subpartitions 14608, 00000, "Tablespace was specified for the previous lob segments of column %s in template but is not specified for %s" // *Cause: Tablespaces may either be specified for all lob segments of a // column or must not be specified for any lob segments of this // column // *Action: Either specify tablespaces for all or for none of the lob segments 14609, 00000, "Tablespace was not specified for the previous lob segments of column %s in template but is specified for %s" // *Cause: Tablespaces may either be specified for all lob segments of a // column or must not be specified for any lob segments of this // column // *Action: Either specify tablespaces for all or for none of the lob segments 14610, 00000, "Lob attributes not specified for lob column %s for subpartition %s" // *Cause: Lob attributes of a column must be specified for all subpartitions // or must not be specified at all // *Action: Ensure lob attributes of a column are specified for all // subpartitions or not specified at all 14611, 00000, "Duplicate subpartition name %s in template" // *Cause: A subpartition name cannot be duplicated within the template // *Action: Rename one of the subpartitions. 14612, 00000, "Duplicate lob segment name %s for lob column %s in template" // *Cause: Two lob segments of the same column were given the same name in the // template // *Action: Rename one of the lob segments 14613, 00000, "Attempt to generate name from parent name %s and template name %s failed as the combine named would have been longer than allowed" // *Cause: Any name generated from a partition name and template name must be // less than the maximum permissible name for an identifier // *Action: Shorten either partition or template name. 14614, 00000, "List value '%s' specified twice in subpartition '%s'" // *Cause: A list value cannot be specified more that once // *Action: Remove one of the specifications of the value 14615, 00000, "List value '%s' specified twice in subpartitions '%s', '%s'" // *Cause: A list value cannot be specified more that once // *Action: Remove one of the specifications of the value 14616, 00000, "table is not subpartitioned by List method" // *Cause: A subpartition maintenance operation, such as ALTER TABLE MODIFY // SUBPARTITION ADD|DROP VALUES, was performed on a non-List // subpartitioned object. // *Action: Reissue the command against a List subpartitioned object. 14617, 00000, "cannot add/drop values to DEFAULT subpartition" // *Cause: A ADD/DROP VALUES operation is being done on the default // subpartition // *Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition 14618, 00000, "cannot drop the last value of subpartition" // *Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition // *Action: Cannot execute the command, unless two or more values exist for subpartition 14619, 00000, "resulting List subpartition(s) must contain at least 1 value" // *Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting // subpartition(as applicable) must contain at least 1 value // *Action: Ensure that each of the resulting subpartitions contains atleast // 1 value 14620, 00000, "DEFAULT subpartition already exists" // *Cause: A subpartition already exists with DEFAULT value // *Action: Remove the DEFAULT value from the list specified 14621, 00000, "cannot add subpartition when DEFAULT subpartition exists" // *Cause: An ADD SUBPARTITION operation cannot be executed when a // subpartition with DEFAULT values exists // *Action: Issue a SPLIT of the DEFAULT subpartition instead 14622, 00000, "Value %s already exists in subpartition %s" // *Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES // statement already exists in another subpartition // *Action: Remove the duplicate value from the statement and try again 14623, 00000, "Value %s does not exist in subpartition %s" // *Cause: One of the list values in the SPLIT PARTITION or DROP VALUES // statement does not exist in the subpartition // *Action: Remove the value from the statement and try again 14624, 00000, "DEFAULT subpartition must be last subpartition specified" // *Cause: A subpartition description follows the one describing the default // subpartition // *Action: Ensure that the DEFAULT subpartition is the last subpartition // description 14625, 00000, "subpartition contains rows corresponding to values being dropped" // *Cause: table subpartition contains rows for the values being dropped. // *Action: DELETE all rows for the values being dropped and reissue statement 14626, 00000, "values being added already exist in DEFAULT subpartition" // *Cause: An ADD VALUE operation cannot be executed because the values // being added exist in the DEFAULT subpartition // *Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split // subpartition into the subpartition to which values need to be added 14627, 00000, "Invalid operation was specified on a GLOBAL partitioned index" // *Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION // was specified on the global index // *Action: Ensure that subpartition level operations are not specified on a // GLOBAL index, since these are only RANGE partitioned 14628, 00000, "specification of bounds is inconsistent with LIST method" // *Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified // bounds that were inconsistent with List subpartitioning method // *Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD // of List subpartitions 14629, 00000, "cannot drop the only subpartition of a partition" // *Cause: A drop subpartition command is being executed when there // is only one subpartition in the partition 14630, 00000, "subpartition 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. 14631, 00000, "the partition bounds do not match the subpartition bounds of the partition" // *Cause: When exchanging a partitioned table with a composite partition // the bounds that describe the partitions of the table must match // the bounds that describe the subpartitions of the composite // partition. // *Action: Ensure that the bounds describing partitions in the partitioned // table is the same as the bounds of the subpartitions in the // the composite partition. 14632, 00000, "cannot specify PARALLEL clause when adding a List subpartition" // *Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL // clause for a List subpartition of a Range/List partitioned object // which is illegal // *Action: Remove the PARALLEL clause. 14633, 00000, "Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table" // *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for // ADD hash subpartition to a composite partitioned table. // *Action:Remove clause and reissue operation 14634, 00000, "Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table" // *Cause: During a split or a merge of a partition of a range list // partitioned table you cannot specify any subpartitioning // information for the resulting partition (s) // *Action: Remove all subpartitioning information from the DDL. 14635, 00000, "only one resulting subpartition can be specified for MERGE SUBPARTITIONS" // *Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting // subpartition for the MERGE // *Action: Ensure that the statement describes exactly one subpartition // as the target that need to be MERGEd 14636, 00000, "only 2 resulting subpartition can be specified for SPLIT SUBPARTITION" // *Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting // subpartition for the SPLIT // *Action: Ensure that the statement describes exactly 2 subpartitions // as the target of the SPLIT operation 14637, 00000, "cannot merge a subpartition with itself" // *Cause: The same subpartition name was specified twice for the merge // operation // *Action: Re-submit operation with 2 distinct subpartition names within the // same composite partition 14638, 00000, "cannot MERGE subpartitions in different Range Composite partitions" // *Cause: Attempted to MERGE subpartitions in different Range Composite // partitions // *Action: Reissue the command after ensuring that the 2 subpartitions being // merged lie in the same composite partition 14639, 00000, "SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition" // *Cause: Attempted to specify SUBPARTITIONS clause on table that is not // partitioned by the Composite Range-Hash method // *Action: Reissue the command after ensuring that the SUBPARTITIONS clause is // not specified, to specify a template for a Composite Range List // object use the SUBPARTITION TEMPLATE clause 14640, 00000, "add/coalesce index partition operation is valid only for hash partitioned global indexes" // *Cause: User attempted to add or coalesce an index partition of a global // index not partitioned by hash method. // *Action: Issue the statement on a global index partitioned by hash method. // or if the index is partitioned by range method consider using // split/drop instead of add/coalesce. 14641, 00000, "STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition" // *Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed" // *Action: Re-issue the stament after removing the STORE-IN clause 14642, 00000, "Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION" // *Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the // INCLUDING INDEXES option has been specified and the tables have // different hakan factors. // *Action: Perform the exchange with the EXCLUDING INDEXES option or alter the // bitmap indexes to be unusable. 14643, 00000, "Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION" // *Cause: Either records_per_block has been minimized for one of the tables to be // exchanged, but not the other, or the hakan factors for the tables to be // exchanged are not equal. // *Action: If records_per_block has been minimized for one of the tables, but not // the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK // option for both tables, or perform alter table with the MINIMIZE // RECORDS_PER_BLOCK for both tables. If the hakan factors do not match // perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option // for both tables. 14644, 00000, "table is not subpartitioned by Hash method" // *Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY // PARTITION COALESCE SUBPARTITION can only be performed on Hash // subpartitioned objects // *Action: Re-issue the command against a Hash subpartitioned object. 14645, 00000, "STORE IN clause cannot be specified for Range List objects" // *Cause: A STORE IN clause was specified for Range List partitioned object // *Action: Re-issue the command after removng the STORE IN clause 14646, 00000, "Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes" // *Cause: The first time a table is altered to include compression, it // cannot have a usable bitmap index (partition). Subsequent alter table // statements involving compression do not have this same restriction. // *Action: A) Drop any bitmap indexes defined on the table, and re-create them // once the operation is complete or, B) Mark all index fragments of // all bitmap indexes defined on the table UNUSABLE and rebuild them // once the operation is complete. /============================================================================ / 14650 - 14699 reserved for reference-partitioning project / / Begin messages for reference-partitioning changes /============================================================================ / 14650, 00000, "operation not supported for reference-partitioned tables" // *Cause: Attempted to perform an operation on a // reference-partitioned table that was not supported. // *Action: Do not perform the unsupported operation. / 14651, 00000, "reference partitioning constraint is not supported" // *Cause: The specified partitioning constraint was not supported // for reference-partitioned tables. The partitioning // constraint must be enabled, validated, and not deferrable. // The partitioning constraint must not have ON DELETE SET // NULL semantics. //* Action: Correct the statement to specify a supported // partitioning constraint. / 14652, 00000, "reference partitioning foreign key is not supported" // *Cause: The specified partitioning foreign key was not supported // for reference-partitioned tables. All columns of the // partitioning foreign key must be constrained NOT NULL with // enabled, validated, and not deferrable constraints. Furthermore, // a virtual column cannot be part of the partitioning foreign key. //* Action: Correct the statement to specify a supported // partitioning foreign key. / 14653, 00000, "parent table of a reference-partitioned table must be partitioned" // *Cause: Attempted to create a reference-partitioned table with a // non-partitioned parent table. // *Action: Correct the statement and reenter. / 14654, 00000, "number of partitions of reference-partitioned table must equal that of the parent table" // *Cause: Attempted to create a reference-partitioned table with a // number of partitions which was different from that of the // parent table. //* Action: Correct the CREATE TABLE statement to specify a correct // number of partitions. / 14655, 00000, "reference partitioning constraint not found" // *Cause: Partitioning constraint specified in CREATE TABLE ... // PARTITION BY REFERENCE was not one of the referential // constraints on the table being created. // *Action: Ensure that the specified partitioning constraint is one // of the referential constraints on the table being created. / 14656, 00000, "cannot drop the parent of a reference-partitioned table" // *Cause: Attempted to drop the parent of a reference-partitioned table. // *Action: Drop all reference-partitioned child tables before dropping the // parent table. / 14657, 00000, "cannot cascade row migration to reference-partitioned child table" // *Cause: Update of a parent key may require migration of rows in // reference-partitioned child tables, however this is not // supported because the parent key was not suitably indexed. // *Action: Replace the existing index on the parent key with a unique index // that does not contain any columns in addition to the parent key. / 14658, 00000, "specified dependent table is not affected by this operation" // *Cause: A table has been specified in the DEPENDENT TABLES clause that // is not a reference-partitioned table affected by the operation. // *Action: Correct the statement and reenter. / 14659, 00000, "Partitioning method of the parent table is not supported" // *Cause: An attempt was made to create a reference-partitioned table with an // interval partitioned parent table. // *Action: Do not create a reference-partitioned table with an interval // partitioned parent table. / 14660, 00000, "parent table of a reference-partitioned table cannot be index-organized" // *Cause: Attempted to create a reference-partitioned table with a // index-organized parent table. // *Action: Correct the statement and reenter. / 14661, 00000, "row movement must be enabled" // *Cause: Attempted to disable row movement for a reference-partitioned // table, although row movement was enabled for its parent table. // *Action: Disable row movement for parent table before disabling row // movement for the reference-partitioned table. / 14662, 00000, "row movement cannot be enabled" // *Cause: Attempted to enable row movement for a partitioned table, // although row movement was disabled for a reference-partitioned // child table. // *Action: Enable row movement for reference-partitioned child tables // before enabling row movement for the parent table. / 14663, 00000, "reference partitioning parent key is not supported" // *Cause: Parent key of the reference-partitioned table's // partitioning constraint contained virtual columns. // *Action: Correct the statement to specify a partitioning // constraint with supported parent key and reenter. / 14664, 00000, "Cannot use PL/SQL expressions in reference partitioning parent key" // *Cause: Parent key of the reference partitioned table's // partitioning constraint contained a virtual column // that referenced a PL/SQL expression. // *Action: Correct the statement to specify a partitioning // constraint with supported parent key and reenter. / 14665, 00000, "Cannot use expressions involving ROWID data type in reference partitioning parent key" // *Cause: Parent key of the reference partitioned table's // partitioning constraint contained a virtual column // that involved the ROWID data type. // *Action: Correct the statement to specify a partitioning // constraint with supported parent key and reenter. / 14666, 00000, "Cannot use expressions involving BLOB or CLOB data types in reference partitioning parent key" // *Cause: Parent key of the reference partitioned table's // partitioning constraint contained a virtual column // that involved a BLOB or CLOB data type. // *Action: Correct the statement to specify a partitioning // constraint with supported parent key and reenter. / 14667, 00000, "Cannot use expressions involving object data types in reference partitioning parent key" // *Cause: Parent key of the reference partitioned table's // partitioning constraint contained a virtual column // that involved an object data type (object, REF, nested // table, array). // *Action: Correct the statement to specify a partitioning // constraint with supported parent key and reenter. / 14668, 00000, "Cannot drop a unique or primary key referenced by the partitioning constraint of a reference-partitioned table." // *Cause: An attempt was made to drop a unique or primary key referenced // by the partitioning constraint of a reference-partitioned table. // *Action: Drop all reference-partitioned child tables before dropping the // unique or primary key of the parent table. / 14700, 00000, "Object(s) owned by SYS cannot be locked by non-SYS user" // *Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) // by a non-SYS user, user should minimally have DML privileges // *Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML // privileges on object, or non-SYS user should connect as SYS // 14701, 00000, "partition-extended name or bind variable must be used for DMLs on tables partitioned by the System method" // *Cause: User attempted not to use partition-extended syntax // for a table partitioned by the System method // *Action: Must use of partition-extended syntax in contexts mentioned above. 14702, 00000, "The partition number is invalid or out-of-range" // *Cause: Attempted to use nonnumerical value or the number was out of range // of the partitions. // *Action: Use a valid partition number. 14703, 00000, "The AFTER clause can be used to ADD PARTITION only to a System Partitioned table." // *Cause: The table is not partitioned by the System method // *Action: Skip the AFTER clause. // 14704, 00000, "Create table as select disallowed for SYSTEM patitioned tables" // *Cause: User attempted to create a SYSTEM partitioned table by doing a // create table as select. // *Action: Do a create table followed by an insert as select into each // partition. /============================================================================ / 14750 - 14799 reserved for interval-partitioning project / / Begin messages for interval-partitioning changes /============================================================================ 14750, 00000, "Range partitioned table with INTERVAL clause has more than one column" // *Cause: You attempted to create an interval partitioned table with more // than one partitioning column. // *Action: Use a single partitioning column. // 14751, 00000, "Invalid data type for partitioning column of an interval partitioned table" // *Cause: You attempted to use interval partitioning on a table partitioned // on a column of data type other than number or date/time. // *Action: Use only number or date/time columns as partitioning columns for // interval partitioned tables. 14752, 00000, "Interval expression is not a constant of the correct type" // *Cause: You attempted to use either a nonconstant interval or an interval // whose data type does not correspond to the partitioning column // *Action: Use only constant expressions for the interval. If the data type of // partitioning column is numeric, the interval must be a numeric // constant. If the data type is of type date/time, the interval must // be a constant of interval type 14753, 00000, "Interval cannot be zero" // *Cause: The interval mapped to zero. // *Action: You must use a nonzero interval. 14754, 00000, "Interval string is too long" // *Cause: The interval string was too long // *Action: Specify interval using a shorter string 14755, 00000, "Invalid partition specification for FOR VALUES clause." // *Cause: The [SUB]PARTITION FOR VALUES (...) clause can only take constants. // In addition it takes as many arguments as there are // partitioning columns and the values must be coercible to the // partitioning columns. // *Action: Specify a valid FOR VALUES clause. 14756, 00000, "Table is not partitioned by Interval method." // *Cause: The table was not partitioned by Interval method. // *Action: ALTER TABLE SET STORE IN is only valid for Interval partitioned // tables. Ensure that the table by Interval. 14757, 00000, "Table is already a range partitioned table" // *Cause: SET INTERVAL () is used to convert an interval partitioned table to // a range partitioned table. It is not legal on a range partitioned // table // *Action: Use SET INTERVAL () only on an interval partitioned table. 14758, 00000, "Last partition in the range section cannot be dropped" // *Cause: An attempt was made to drop the last range partition of an interval // partitioned table. // *Action: Do not attempt to drop this partition. 14759, 00000, "SET INTERVAL is not legal on this table." // *Cause: SET INTERVAL clause was specified. ALTER TABLE SET INTERVAL is // only legal on a range partitioned table with a single partitioning // column. Additionally, this table cannot have a maxvalue partition // and cannot be the parent table for any reference partitioned tables. // *Action: Use SET INTERVAL only on a valid table. 14760, 00000, "ADD PARTITION is not permitted on Interval partitioned objects" // *Cause: ALTER TABLE ADD PARTITION was attempted on an Interval // partitioned object. // *Action: Do not perform the operation on an Interval partitioned object. // Insert a row to create the new partition. 14761, 00000, "MAXVALUE partition cannot be specified for Interval partitioned objects" // *Cause: An attempt was made to create a partition with a MAXVALUE highbound // on an Interval partitioned object. // *Action: Do not create a partition with a MAXVALUE highbound. 14762, 00000, "Domain index creation on interval partitioned tables is not permitted" // *Cause: An attempt was made to create a domain index on an interval // partitioned table. // *Action: Do not create a domain index on an interval partitioned table. 14763, 00000, "Unable to resolve FOR VALUES clause to a partition number" // *Cause: Could not determine the partition corresponding to the FOR VALUES // clause. // *Action: Remove bind variables and dependencies on session parameters // from the values specified in the FOR VALUES clause. 14764, 00000, "FOR VALUES clause cannot be specified for only one partition" // *Cause: An attempt was made to specify the FOR VALUES clause for only one // of the two partitions being merged. // *Action: Specify a FOR VALUES clause for each of the two partitions being // merged or do not specify the FOR VALUES clause for either. 14765, 00000, "Cannot create a partition while doing a create index" // *Cause: An attempt was made to create a partition concurrently with index // creation. // *Action: Retry the statement after the index build is finished. 14766, 00000, "Unable to obtain a stable metadata snapshot" // *Cause: This operation was not able to obtain a stable snapshot of the // interval partitioning metadata. // *Action: Retry the statement. 14767, 00000, "Cannot specify this interval with existing high bounds" // *Cause: The interval specified conflicts with the existing high bound for // the last partition. The combination might lead to invalid dates // for high bounds in the future. // *Action: If this is a CREATE TABLE, try specifying a different high bound // value for the last partition, or a different interval. If this // is an ALTER TABLE SET INTERVAL, please choose either a different // interval, or, modify the table to change the high bound for the // last partition. 14768, 00000, "Error Loading Versioned object" // *Document: NO // *Cause: Internal Error. Should never be returned to user // *Action: If seen by user report to Oracle support. 14799, 00000, "Temporary interval error %s, %s" // *Document: NO // *Cause: Ignore // *Action: Ignore /============================================================================ / 14800 - 14849 Reserved for composite list/* partitioning / / Begin messages for composite list/* partitioning /============================================================================ 14801, 00000, "Hash composite partitioning is not supported" // *Cause: An attempt was made to partition a table using a Hash composite // method. // *Action: Do not partition the table by a Hash composite method. 14802, 00000, "Specified operation is not permitted on Hash composite partitioned objects" // *Cause: An unsupported operation was attempted on a Hash composite // partitioned object. // *Action: Do not perform the operation on a Hash composite partitioned object. 14803, 00000, "partition bound may not be specified for hash subpartitioned tables" // *Cause: A VALUES LESS THAN or VALUES clause was specified with a subpartition // description. // *Action: Remove the VALUES LESS THAN or VALUES clause from the // subpartition description. / /============================================================================ / 15000 - 15499 Reserved for Automatic Storage Management / / Begin messages for Automatic Storage Management /============================================================================ / /============================================================================ / 15000 - 15099 Used for ASM run-time errors /============================================================================ / 15000, 00000, "command disallowed by current instance type" // *Cause: The user has issued a command to a conventional RDBMS instance // that is only appropriate for an ASM instance. Alternatively, the // user has issued a command to an ASM instance that is only // appropriate for an RDBMS instance. // *Action: Connect to the correct instance type and re-issue the command. // 15001, 00000, "diskgroup \"%s\" does not exist or is not mounted" // *Cause: An operation failed because the diskgroup specified does not // exist or is not mounted by the current ASM instance. // *Action: Verify that the diskgroup name used is valid, that the // diskgroup exists, and that the diskgroup is mounted by // the current ASM instance. // 15002, 00000, "parameter LOCK_NAME_SPACE exceeds limit of %s characters" // *Cause: The LOCK_NAME_SPACE initialization parameter contained a // value that is too long. // *Action: Correct the LOCK_NAME_SPACE initialization parameter. // 15003, 00000, "diskgroup \"%s\" already mounted in another lock name space" // *Cause: The diskgroup could not be mounted by the ASM instance because // it was operating in a lockspace different than another existing // ASM instance which had already mounted the diskgroup. // *Action: Check the LOCK_NAME_SPACE initialization parameter value, or // dismount the diskgroup from the other ASM instances. // 15004, 00000, "alias \"%s\" does not exist" // *Cause: The specified alias did not exist within the diskgroup. // *Action: Check the alias name and diskgroup name. // 15005, 00000, "name \"%s\" is already used by an existing alias" // *Cause: An existing alias in the diskgroup used the same name. // *Action: Select another alias name, or drop the existing alias. // 15006, 00000, "template \"%s\" does not exist" // *Cause: The specified template did not exist within the diskgroup. // *Action: Check the template name and diskgroup name. // 15007, 00000, "name is already used by an existing template" // *Cause: A template with the same name already exists. // *Action: Select another template name, or drop the existing template. // 15008, 00000, "cannot drop system template" // *Cause: The specified template was created by the system and must // always exist for proper operation. // *Action: Select another template name. // 15009, 00000, "ASM disk \"%s\" does not exist" // *Cause: The specified ASM disk was not found. // *Action: Check the ASM disk name. // 15010, 00000, "name '%s' is already used by an existing ASM disk" // *Cause: The specified name was already used in this diskgroup. // *Action: Specify a different ASM disk name. // 15011, 00000, "failure group \"%s\" does not exist in diskgroup \"%s\"" // *Cause: The specified name did not match the failure group of any // disks in the diskgroup. This usually indicates that the failure // group name was specified incorrectly. // *Action: Check the failure group name. // 15012, 00000, "ASM file '%s' does not exist" // *Cause: The ASM file was not found. // *Action: Check the ASM file name. // 15013, 00000, "diskgroup \"%s\" is already mounted" // *Cause: An ALTER DISKGROUP MOUNT command specified the name of a diskgroup // which is already mounted by the current ASM instance. // *Action: Check the name of the diskgroup. // 15014, 00000, "path '%s' is not in the discovery set" // *Cause: The operating system path specified was outside the set of disks // that are discovered by the instance. // *Action: Specify a operating system path within the set of disks that are // discovered based upon the ASM_DISKSTRING parameter. Alternatively, // check the setting of the ASM_DISKSTRING parameter. // 15015, 00000, "Specified path '%s' conflicts with path '%s'" // *Cause: The ASM instance previously discovered specified disk with an ASM // library using a different path. // *Action: Use the discovery string of the ASM library to add the disk. // 15016, 00000, "inconsistent respecification of path '%s'" // *Cause: The specified path was provided more than once with different // properties. // *Action: Do not provide a path more than once. Alternatively, provide // consistent properties. // 15017, 00000, "diskgroup \"%s\" cannot be mounted" // *Cause: The disk group could not be mounted by the ASM instance either // of an IO error or due to other reasons explained in alert log or // trace files. // *Action: Check for additional errors reported. Correct the error and // retry the operation. // 15018, 00000, "diskgroup cannot be created" // *Cause: The specified diskgroup could not be created. // *Action: Check for additional errors reported. // 15019, 00000, "discovered duplicate path '%s' for '%s'" // *Cause: The discovery encountered multiple paths to the same disk. // *Action: Check that the ASM_DISKSTRING parameter specifies only a // single path for each disk. // 15020, 00000, "discovered duplicate ASM disk \"%s\"" // *Cause: The discovery encountered two disks claiming to be the same // named ASM disk. // *Action: Check that the ASM_DISKSTRING parameter specifies only a // single path for each disk. // 15021, 00000, "parameter \"%s\" is not valid in %s instance" // *Cause: The specified parameter was not supported when starting an // instance of this type. // *Action: Delete the specified parameter from the INIT.ORA file. / 15023, 00000, "reached maximum allowable number of disks %s" // *Cause: An attempt was made to add another disk to a diskgroup // which already contains the maximum number of disks allowed. // *Action: Consider dropping existing disks from the diskgroup before // adding additional ones, or create a new diskgroup. // 15024, 00000, "discovered duplicately numbered ASM disk %s" // *Cause: The discovery encountered two disks claiming to have the same // ASM disk number. // *Action: Check that the ASM_DISKSTRING parameter specifies only a // single path for each disk. // 15025, 00000, "could not open disk \"%s\"" // *Cause: The specified disk could not be opened. If the database instance // is running as an Operating System (OS) user different from that // of the ASM instance, then the permissions on the database oracle // binary may be incorrect. // *Action: Check the additional error messages, if any. If the database // instance is running as an OS user different from that of the // ASM instance, use the "srvctl" command to stop and restart // the database to fix the permissions. // 15026, 00000, "disk '%s' is not an ASM disk" // *Cause: The disk did not contain a valid ASM disk header. // *Action: Check to see if the data on the disk has been changed // by some system administrator action. // 15027, 00000, "active use of diskgroup \"%s\" precludes its dismount" // *Cause: An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup // which had clients with open files in the diskgroup. Diskgroups // cannot be dismounted until all open files in the diskgroup // are closed. // *Action: Stop all clients that are using this diskgroup and retry // the ALTER DISKGROUP ... DISMOUNT command. Query the V$ASM_CLIENT // fixed view in an ASM instance or use ASMCMD LSOF to list active // clients. // 15028, 00000, "ASM file '%s' not dropped; currently being accessed" // *Cause: An attempt was made to drop an ASM file, but the file was // being accessed by one or more clients and therefore could // not be dropped. // *Action: Stop all clients that are using this file and retry the drop // command. Query the V$ASM_CLIENT fixed view in an ASM instance // or use ASMCMD LSOF to list active clients. // 15029, 00000, "disk '%s' is already mounted by this instance" // *Cause: An attempt was made to add to a diskgroup a disk that // was already mounted by the current instance as part of // some (possibly other) diskgroup. // *Action: Specify a different disk in the command. Note that not // even the FORCE option can be used to correct the situation // until the diskgroup containing the disk becomes dismounted // by this instance. // 15030, 00000, "diskgroup name \"%s\" is in use by another diskgroup" // *Cause: A CREATE DISKGROUP command specfied a diskgroup name that // was already assigned to another diskgroup. // *Action: Select a different name for the diskgroup. // 15031, 00000, "disk specification '%s' matches no disks" // *Cause: The device specification string to a CREATE DISKGROUP command // did not match any devices which could be discovered. // *Action: Check the device specification string matches a disk on the // system. // 15032, 00000, "not all alterations performed" // *Cause: At least one ALTER DISKGROUP action failed. // *Action: Check the other messages issued along with this summary error. // 15033, 00000, "disk '%s' belongs to diskgroup \"%s\"" // *Cause: An attempt was made to ADD to a diskgroup a disk that was // already part of another diskgroup, or an attempt was made to // DROP / OFFLINE / ONLINE / CHECK a disk that was not part of // the specified diskgroup. // *Action: For ADD, check the path specifier for the disk. If it is certain // that the disk is not in use by another diskgroup, the FORCE option // may be used to override this check. For the other commands, check // the name of the specified disk. // 15034, 00000, "disk '%s' does not require the FORCE option" // *Cause: An attempt was made to add the disk to the diskgroup using // the FORCE option. The disk was not found to be in use at the // present time, so the FORCE option was not permitted. // *Action: Avoid gratuitous use of the FORCE option. // 15035, 00000, "no disks belong to diskgroup \"%s\"" // *Cause: An attempt was made to mount a diskgroup for which no // member disks were discovered. // *Action: Specify a valid diskgroup name that contains disks. // 15036, 00000, "disk '%s' is truncated" // *Cause: The size of the disk, as reported by the operating // system, was smaller than the size of the disk as recorded in // the disk header block on the disk. // *Action: Check if the system configuration has changed. // 15037, 00000, "disk '%s' is smaller than mimimum of %s MBs" // *Cause: The size of the disk, as reported by the operating // system, was too small to allow the disk to become part of // the diskgroup. // *Action: Check if the system configuration is correct. // 15038, 00000, "disk '%s' mismatch on '%s' with target disk group [%s] [%s]" // *Cause: An attempt was made to mount into a disk group a disk whose // recorded allocation unit size, metadata block size, physical // sector size, or creation time stamp was inconsistent with the other // disk group members. // *Action: Check if the system configuration has changed. Verify disk // discovery string. // 15039, 00000, "diskgroup not dropped" // *Cause: An attempt to drop a diskgroup failed. // *Action: See the associated messages for details about why the drop // was not successful. // 15040, 00000, "diskgroup is incomplete" // *Cause: Some of the disks comprising a diskgroup were not present. // *Action: Check the hardware to ensure that all disks are functional. Also // check that the setting of the ASM_DISKSTRING initialization // parameter has not changed. Alternatively, for normal or high // redundancy diskgroups, use MOUNT FORCE to offline missing disks // as part of mounting the diskgroup. // 15041, 00000, "diskgroup \"%s\" space exhausted" // *Cause: The diskgroup ran out of space. // *Action: Add more disks to the diskgroup, or delete some existing files. // 15042, 00000, "ASM disk \"%s\" is missing from group number \"%s\" " // *Cause: The specified disk, which is a necessary part of a diskgroup, // could not be found on the system. // *Action: Check the hardware configuration. // 15043, 00000, "ASM disk \"%s\" is not a diskgroup member" // *Cause: The specified disk has been removed from the diskgroup, but // a disk matching its name was found. // *Action: Check the hardware configuration. // 15044, 00000, "ASM disk '%s' is incorrectly named" // *Cause: Either the specified disk had its contents changed such that // it no longer contained an ASM disk name in its header that matches // the diskgroup information or its FAILGROUP information // may have become inconsistent. // *Action: Drop the disk from the diskgroup. // 15045, 00000, "ASM file name '%s' is not in reference form" // *Cause: The ASM file name was not in a form that can be used to reference // an existing file because a file/incarnation number or an // alias name was not present or a template name was included. // *Action: Correct the specified ASM file name. // 15046, 00000, "ASM file name '%s' is not in single-file creation form" // *Cause: The ASM file name was not in a form that can be used to create // an single file because a file/incarnation number was present. // *Action: Correct the specified ASM file name. // 15047, 00000, "ASM file name '%s' is not in multiple-file creation form" // *Cause: The ASM file name was not in a form that can be used to create // multiple files because either a fully-qualified file name or an // alias name was present. // *Action: Correct the specified ASM file name. // 15048, 00000, "ASM internal files cannot be deleted" // *Cause: An attempt was made to delete a metadata file used by ASM // to manage the diskgroup. // *Action: Check the specified ASM file name. // 15049, 00000, "diskgroup \"%s\" contains %s error(s)" // *Cause: Errors were discovered by the ALTER DISKGROUP CHECK command. // *Action: See the alert log for details of the errors. // 15050, 00000, "disk \"%s\" contains %s error(s)" // *Cause: Errors were discovered by the ALTER DISKGROUP CHECK DISK command. // *Action: See the alert log for details of the errors. // 15051, 00000, "file '%s' contains %s error(s)" // *Cause: Errors were discovered by the ALTER DISKGROUP CHECK FILE command. // *Action: See the alert log for details of the errors. // 15052, 00000, "ASM file name '%s' is not in diskgroup \"%s\"" // *Cause: The ASM file name did not contain a diskgroup name that specified // the correct diskgroup as implied by the other arguments to // the command. // *Action: Correct the specified ASM file name or diskgroup name. // 15053, 00000, "diskgroup \"%s\" contains existing files" // *Cause: An attempt was made to drop a diskgroup that still contains // existing files. // *Action: Specify the INCLUDING CONTENTS option to drop the diskgroup // and all of its existing files. // 15054, 00000, "disk \"%s\" does not exist in diskgroup \"%s\"" // *Cause: An attempt was made to DROP (or CHECK) a disk that is not part of // the specified diskgroup. // *Action: Check the name of the specified disk and the specified // diskgroup. // 15055, 00000, "unable to connect to ASM instance" // *Cause: The RDBMS instance was unable to connect to the required ASM // instance when accessing a disk group. // *Action: Check the additional error messages. May need to configure // correct ASM sid or make sure the RDBMS instance has OS // privileges for ASM SYSDBA. // 15056, 00000, "additional error message" // *Cause: An operating system error occured. // *Action: Correct the operating system error and retry the operation. // 15057, 00000, "specified size of %s MB is larger than actual size of %s MB" // *Cause: A disk size expression exceeded the amount of storage actually // availalable, as reported by the operating system. // *Action: Specify a valid size. // 15058, 00000, "disk '%s' belongs to an incompatible diskgroup" // *Cause: An attempt was made to ADD to a diskgroup a disk which was // already part of another diskgroup. The other diskgroup was // written by a more recent software release. // *Action: Check the path specifier for the disk. If it is certain that // the disk is not in use by another diskgroup, the FORCE option // may be used to override this check. // 15059, 00000, "invalid device type for ASM disk" // *Cause: The device type of the discovered disk was not valid for use as // an ASM disk. // *Action: Check the file path and retry or exclude it from the discovery // set. See the accompanying operating system error for additional // information. // 15060, 00000, "template \"%s\" does not exist" // *Cause: A command specified a template name, either directly or // as part of an ASM file name, which did not exist. // *Action: Check the template specifier in the command. // 15061, 00000, "ASM operation not supported [%s]" // *Cause: An ASM operation was attempted that is invalid or not supported // by this version of the ASM instance. // *Action: This is an internal error code that is used for maintaining // compatibility between software versions and should never be // visible to the user; contact Oracle support Services. // 15062, 00000, "ASM disk is globally closed" // *Cause: The disk to which the I/O request was issued has gone offline or // has been globally closed by the background process. Check other // messages in the trace files for more information. // *Action: Bring the disk online for I/Os to get through. // 15063, 00000, "ASM discovered an insufficient number of disks for diskgroup \"%s\"" // *Cause: ASM was unable to find a sufficient number of disks belonging to the // diskgroup to continue the operation. // *Action: Check that the disks in the diskgroup are present and functioning, // that the owner of the ORACLE binary has read/write permission to // the disks, and that the ASM_DISKSTRING initialization parameter // has been set correctly. Verify that ASM discovers the appropriate // disks by querying V$ASM_DISK from the ASM instance. // 15064, 00000, "communication failure with ASM instance" // *Cause: There was a failure to communicate with the ASM instance, most // likely because the connection went down. // *Action: Check the accompanying error messages for more information on the // reason for the failure. Note that database instances will always // return this error when the ASM instance is terminated abnormally. // 15065, 00000, "hash collision for diskgroup names '%s' and '%s'" // *Cause: There was a collision in the group name used for the diskgroup. // The diskgroup(s) cannot be mounted using colliding names. // *Action: Use a different diskgroup name and also report to Oracle Support // Services the two diskgroup names which collided. // 15066, 00000, "offlining disk \"%s\" in group \"%s\" may result in a data loss" // *Cause: Following I/O failures, the disks holding all copies of a data // block were attempted to be taken offline. // *Action: Check the accompanying error messages for more information on the // reason for the disk I/O failures. // 15067, 00000, "command or option incompatible with diskgroup redundancy" // *Cause: An attempt was made to use a feature which is not // permitted by the diskgroup's redundancy policy. Common examples // are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, // using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, // or using invalid template attributes. // *Action: Omit the option from the command. // 15068, 00000, "maximum number of diskgroups %s already mounted" // *Cause: An attempt was made to mount more diskgroups than the // instance is capable of mounting at one time. // *Action: Dismount a mounted diskgroup and retry the command. // 15069, 00000, "ASM file '%s' not accessible; timed out waiting for lock" // *Cause: An attempt was made to access an ASM file, but the file is // currently being created, resized, or deleted and therefore // cannot be accessed. // *Action: No action required, or try again later, after the create or // resize has completed. // 15070, 00000, "maximum number of files %s exceeded in diskgroup \"%s\"" // *Cause: The diskgroup ran out of space. // *Action: Delete some existing ASM files or create files in a new diskgroup. // 15071, 00000, "ASM disk \"%s\" is already being dropped" // *Cause: An attempt was made to drop a disk from a diskgroup that was // already in the process of being dropped from the diskgroup. // Alternatively, an attempt was made to forcibly drop a disk from // a diskgroup using the FORCE option that was already being // forcibly dropped from the diskgroup. // *Action: Check the ASM disk name and FORCE option as specified in // the command. // 15072, 00000, "command requires at least %s regular failure groups, discovered only %s" // *Cause: An attempt was made to create either a normal redundancy diskgroup // for which fewer than two regular failure groups were both specified // and discovered, or a high redundancy diskgroup for which fewer than // three regular failure groups were both specified and discovered, or // an external redundancy diskgroup for which only quorum disks were // both specified and discovered. // *Action: Check the that the command does specify the required number of // failure groups, and that all of the specified disks are discovered // by ASM. A query of the V$ASM_DISK fixed view will show which disks // are discovered by ASM. Note that a quorum failure group will not be // used as a regular failure group. An external redundancy diskgroup // requires at least one regular disk. // 15073, 00000, "diskgroup %s is mounted by another ASM instance" // *Cause: An attempt was made to drop a diskgroup that is still // mounted somewhere in the cluster by another instance. // *Action: dismount the diskgroup from all nodes except the one // performing the drop diskgroup command. // 15074, 00000, "diskgroup %s requires rebalance completion" // *Cause: An attempt was made to repeatedly add or drop disks from a // diskgroup. ASM could not perform the operation given the // current state of the diskgroup. // *Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow // the rebalance to run to completion. Alternatively, invoke the // ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to // run to completion. After the rebalance has completed, retry the // operation. // 15075, 00000, "disk(s) are not visible cluster-wide" // *Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could // not be discovered by one or more nodes in a RAC cluster // configuration. // *Action: Determine which disks are causing the problem from the // GV$ASM_DISK fixed view. Check operating system permissions // for the device and the storage sub-system configuration on // each node in a RAC cluster that cannot identify the disk. // 15076, 00000, "Emulating I/O errors on the OSM disk" // *Cause: The disk to which the I/O request was issued is in an error // emulation mode. // *Action: Bring the disk online for I/Os to get through. // 15077, 00000, "could not locate ASM instance serving a required diskgroup" // *Cause: The instance failed to perform the specified operation because it // could not locate a required ASM instance. // *Action: If you want to start a database instance, start an ASM instance // and mount the required diskgroup. If you want to start an ASM // instance, relink the ORACLE binary with ASM_ON or explicitly set // INSTANCE_TYPE initialization parameter to ASM. // 15078, 00000, "ASM diskgroup was forcibly dismounted" // *Cause: The diskgroup to which the I/O request was issued was forcibly // dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so // that it could not be accessed. // *Action: Mount the diskgroup to allow access again. // 15079, 00000, "ASM file is closed" // *Cause: The file to which the I/O request was issued was closed. This // could have been a consequence of the diskgroup being dismounted. // *Action: Make sure the diskgroup is mounted and the file is open. // 15080, 00000, "synchronous I/O operation to a disk failed" // *Cause: A synchronous I/O operation invoked on a disk has failed. // *Action: Make sure that all the disks are operational. // 15081, 00000, "failed to submit an I/O operation to a disk" // *Cause: A submission of an I/O operation to a disk has failed. // *Action: Make sure that all the disks are operational. // 15082, 00000, "ASM failed to communicate with client" // *Cause: There was a failure or time out when ASM tried to communicate with // a connected RDBMS or ADVM client. // *Action: Check the accompanying error messages and alert logs // for more information on the reason for the failure. // Check system specific logs (/var/adm/messages on Linux, // Event Log on Windows) for ADVM messages. // 15083, 00000, "failed to communicate with ASMB background process" // *Cause: A database instance failed to communicate with its ASMB background // process when attempting to access an ASM file. // *Action: Check the alert log for more information on the reason for the // failure. // 15084, 00000, "ASM disk \"%s\" is offline and cannot be dropped." // *Cause: An attempt was made to drop a disk that is offline. // *Action: Check the ASM disk name as specified in the command; or, // if needed, use the DROP DISK FORCE option. // 15085, 00000, "ASM disk \"%s\" has inconsistent sector size." // *Cause: An attempt to mount a diskgroup failed because a disk reported // inconsistent sector size value. // *Action: Use disks with sector size consistent with Diskgroup sector size, // or make sure the operating system can accurately report the disk // sector size. // 15086, 00000, "Diskgroup sector size must be specified." // *Cause: The _disk_sector_size_override parameter was used but the // sector disk value was not specified in the command. // *Action: Specify the sector size value, or do not set (or do not set to // TRUE) the _disk_sector_size_override parameter. // 15087, 00000, "disk '%s' is formatted as an ext2/ext3 or OCFS2 file system." // *Cause: A signature was found on the specified disk indicating that // it is in use by an existing ext2/ext3 or OCFS2 file system. // *Action: Adjust discovery string and device permissions to exclude // previously formatted disks from discovery. // 15088, 00000, "diskgroup creation incomplete" // *Cause: A previous failure during diskgroup creation left the diskgroup // in an inconsistent state. // *Action: Issue DROP DISKGROUP ... FORCE INCLUDING CONTENTS to clean up // the failed creation, then re-create the diskgroup. // 15089, 00000, "Extent %s of ASM file %s cannot be relocated" // *Document: NO // *Cause: The specified extent could not be relocated because of a disk online // that was in progress. // *Action: No action needs to be taken. This error is caught by ASM and handled // internally. // 15090, 00000, "handle %s is not a valid descriptor" // *Cause: The file handle was not valid in this session. // *Action: Submit a handle obtained from a successful call to // DBMS_DISKGROUP.OPEN(). // 15091, 00000, "operation incompatible with open handle in this session" // *Cause: The current session contained an open handle from the // DBMS_DISKGROUP PL/SQL package which precluded performing // the command. // *Action: Execute the command in a different session. // 15092, 00000, "I/O request size %s is not a multiple of logical block size %s" // *Cause: The length of the request was not a multiple of logical block size. // *Action: Correct the error and retry the operation. // 15093, 00000, "buffer only contains %s bytes, I/O requested is %s bytes" // *Cause: The buffer supplied for write was too small to satisfy the request. // *Action: Correct the error and retry the operation. // 15094, 00000, "attempted to write to file opened in read only mode" // *Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have // write privileges. // *Action: Obtain a file handle in read-write mode and retry the write // operation. // 15095, 00000, "reached maximum ASM file size (%s GB)\n" // *Cause: An ASM file creation or file resize operation exceeded the // maximum file size permitted by ASM. // *Action: Use smaller files. 15096, 0000, "lost disk write detected" // *Cause: A failure either by disk hardware or disk software caused a disk // write to to be lost, even though ASM received acknowledgement that // the write completed. Alternatively, a clustering hardware failure // or a clustering software failure resulted in an ASM instance // believing that another ASM instance had crashed, when in fact it // was still active. // *Action: The disk group is corrupt and cannot be recovered. The disk group // must be recreated, and its contents restored from backups. // 15097, 00000, "cannot SHUTDOWN ASM instance with connected client (process %s)" // *Cause: A SHUTDOWN command was issued to an ASM instance that had one or // more connected clients. // *Action: Stop all clients that are using this ASM instance and retry the // SHUTDOWN command. Alternatively, use the SHUTDOWN ABORT command. // Note that issuing the SHUTDOWN ABORT command to an ASM instance // results in abormal termination of all RDBMS instances connected // to that ASM instance. One of the active clients has been listed // in the error message. Query the V$ASM_CLIENT fixed view in an // ASM instance or use ASMCMD LSOF to list all active clients. // 15098, 00000, "file type not recognized by ASM instance" // *Cause: An attempt was made by DB instance to create a file for a file // type that is not recognized by current version of ASM instance. // *Action: Upgrade ASM to higher version that recognizes this file type. // 15099, 00000, "disk '%s' is larger than maximum size of %s MBs" // *Cause: The specified size of the disk was too big to allow the // disk to become part of the diskgroup. // *Action: Specify a smaller disk size than the maximum allowed size. // / /============================================================================ / 15100 - 15179 Used for ASM SQL usage errors /============================================================================ / 15100, 00000, "invalid or missing diskgroup name" // *Cause: The command did not specify a valid diskgroup name. // *Action: Specify a valid diskgroup name. // 15101, 00000, "no action specified" // *Cause: The ALTER DISKGROUP command did not specify any alterations. // *Action: Specify at least one operation clause. // 15102, 00000, "invalid POWER expression" // *Cause: The syntax of the POWER expression was invalid. // *Action: Specify a valid POWER expression. // 15103, 00000, "conflicting or duplicate REPAIR options" // *Cause: The command specified conflicting or duplicate REPAIR keywords. // *Action: Specify only one REPAIR action. // 15104, 00000, "conflicting CONTENTS options" // *Cause: The command specified conflicting or duplicate INCLUDING CONTENTS // or EXCLUDING CONTENTS options. // *Action: Specify only one option. // 15105, 00000, "missing or invalid FAILGROUP name" // *Cause: The command did not specify a valid failure group name. // *Action: Specify a valid failure group name. // 15106, 00000, "missing or invalid operating system disk locator string" // *Cause: The command did not specify a valid operating system path // for the device as a string. // *Action: Specify a valid operating system path for the device. // 15107, 00000, "missing or invalid ASM disk name" // *Cause: The command did not specify a valid ASM disk name identifier. // *Action: Specify a valid ASM disk name identifier. // 15108, 00000, "missing or invalid template name" // *Cause: The command did not specify a valid template name identifier. // *Action: Specify a valid template name identifier. // 15109, 00000, "conflicting protection attributes specified" // *Cause: The command contained an invalid combination of the UNPROTECTED, // MIRROR, or PARITY keywords. // *Action: Specify only one keyword. // 15110, 00000, "no diskgroups mounted" // *Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so // instance startup or the ALTER DISKGROUP ALL MOUNT command did not // mount any diskgroups. // *Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore // the error. // 15111, 00000, "conflicting or duplicate STRIPE options" // *Cause: The command contained both a FINE and COARSE keyword, or // contained the FINE keyword more than once, or contained the // COARSE keyword more than once. // *Action: Specify only one keyword. // 15112, 00000, "no diskgroups currently mounted" // *Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups // upon which to operate. Either instance shutdown or an ALTER // DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, // or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop // any disks. // *Action: Mount the diskgroups on which you wish to operate or ignore // the error. // 15113, 00000, "alias name '%s' refers to a directory" // *Cause: The name specified referred to a directory in the alias directory // and not a valid alias entry. // *Action: Check the alias name and retry. // 15114, 00000, "missing or invalid ASM file name" // *Cause: The command did not specify a valid ASM file name identifier. // *Action: Specify a valid ASM file name identifier. // 15115, 00000, "missing or invalid ASM disk size specifier" // *Cause: The command did not specify a valid ASM disk size. // *Action: Specify a valid ASM disk size. // 15116, 00000, "invalid combination of ALTER DISKGROUP options" // *Cause: The ALTER DISKGROUP options may not be combined in this manner. // *Action: Issue separate ALTER DISKGROUP commands to accomplish the // desired action. // 15117, 00000, "command only operates on one diskgroup" // *Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command // specified a list of diskgroups or the keyword ALL in a context // where only a single diskgroup was permitted. // *Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP // DISKGROUP commands to accomplish the desired action. // 15120, 00000, "ASM file name '%s' does not begin with the ASM prefix character" // *Cause: A file name was specified to ASM which did not begin with the // ASM prefix character (currently '+'). ASM uses the prefix to // determine that a file specification is in fact an ASM file. // *Action: Correct the file name specification. // 15121, 00000, "ASM file name '%s' contains an invalid diskgroup name" // *Cause: A file name was specified that did not contain a valid // diskgroup name. The diskgroup name follows immediately after // the ASM prefix character. It must start with an alphabetic // character, and consist of up to 30 characters which are // alphabetic, numeric, or the characters '$' and '_'. // *Action: Correct the file name specification. // 15122, 00000, "ASM file name '%s' contains an invalid file number" // *Cause: A numeric file name was specified which did not contain a // valid ASM file number. The ASM file number follows immediately // after the diskgroup name. It must be preceeded by a '.' character, // and contain only numeric characters. // *Action: Correct the file name specification. // 15123, 00000, "ASM file name '%s' contains an invalid incarnation number" // *Cause: A numeric file name was specified which did not contain a // valid ASM incarnation number. The ASM incarnation number follows // immediately after the ASM file number. It must be preceeded by // a '.' character, and contain only numeric characters. // *Action: Correct the file name specification. // 15124, 00000, "ASM file name '%s' contains an invalid alias name" // *Cause: A file name was specified which did not contain a valid // ASM alias name. The ASM alias name, if present, follows // immediately after the diskgroup name, in place of the ASM // file number. It must be preceeded by a slash, start with an // alphabetic character, and consist of up to 48 characters which // are alphabetic, numeric, or the characters '$', '_', '-', or '#". // A space can separate two parts of an alias name. // *Action: Correct the file name specification. // 15125, 00000, "ASM file name '%s' contains an invalid template name" // *Cause: A file name was specified to ASM which did not contain a valid // template name. The template name, if present, follows // immediately after the ASM incarnation number or the ASM alias // name, if such is used in place of the ASM file number. It must // be enclosed in parenthesis, start with an alphabetic character, // and consist of up to 30 characters which are alphabetic, numeric, // or the characters '$' and '_'. // *Action: Correct the file name specification. // 15126, 00000, "component within ASM file name '%s' exceeds maximum length" // *Cause: The maximum identifier length of 48 characters was exceeded for // the diskgroup name, template name, or alias name field within the // ASM file name. // *Action: Correct the file name specification. // 15127, 00000, "ASM file name '%s' cannot use templates" // *Cause: A fully qualified ASM file name was specified. Such a // specification does not permit the inclusion of a template name // in the ASM file name. // *Action: Correct the file name specification. // 15128, 00000, "ASM file name '%s' exceeds maximum length %s" // *Cause: The maximum ASM file name length of 256 characters was exceeded for // the combination of diskgroup name, file number, template name, // alias name plus punctuation within the ASM file name. // *Action: Correct the file name specification. // 15129, 00000, "entry '%s' does not refer to a valid directory" // *Cause: The entry indicated did not refer to a directory. Attempt was // made to access the contents of this directory. // *Action: Correct the error and try again. // 15130, 00000, "diskgroup \"%s\" is being dismounted" // *Cause: The diskgroup is being dismounted by request or because an I/O // error was encountered that could not be handled by taking the // disks offline. A disk cannot be offlined whenever doing so // could result in all copies of a redundant extent being unavailable. // *Action: Repair the hardware problem and re-mount the diskgroup. // Refer to the alert log to determine which disks have failed. // 15131, 00000, "block %s of file %s in diskgroup %s could not be read" // *Cause: A block could not be read because the disk containing the block // is either offline or an I/O error occured while reading the block. // If this is mirrored file, then all disks that contain a copy // of the block are either offline or received errors. // *Action: Repair the affected disk and bring it back online. Refer to // accompanying error messages to determine which disk has failed. // 15132, 00000, "block %s of file %s in diskgroup %s could not be written" // *Cause: A block could not be written because the disk containing the block // is either offline or an I/O error occured while writing the block. // If this is mirrored file, then insufficient disks which contain a // copy of the block are either offline or received errors. // *Action: Repair the affected disk and bring it back online. Refer to // accompanying error messages to determine which disk has failed. // 15133, 00000, "instance recovery required for diskgroup %s" // *Cause: An instance in the cluster crashed making instance recovery // necessary. // *Action: None. This error should not normally be seen by an ASM client. // ASM will trap this error and retry the operation after doing // instance recovery automatically. Otherwise, manually retry the // operation. // 15134, 00000, "mirror resilvering not supported for %s" // *Cause: The specified device requires oracle to take mirror resilvering // responsiblity. ASM does not resilver logical volume manager (lvm) // based mirrors. // *Action: Disable lvm-based mirroring or set the parameter // _asm_allow_lvm_resilvering to TRUE. One might experience // performance degradation when lvm-based resilvering is enabled // with ASM. // 15149, 00000, "another ASM instance found running on the host" // *Cause: Another ASM instance found on the host. Only one ASM instance is // supported on a host. // *Action: Shut down the other instance before starting this ASM // instance. 15150, 00000, "instance lock mode '%s' conflicts with other ASM instance(s)" // *Cause: Some other ASM instance used the lock name space in a conflicting // mode. // *Action: Shut down the other instance or start up in compatible mode. // Alternatively, set the DB_UNIQUE_NAME initialization parameter // to avoid the conflict. // 15151, 00000, "missing or invalid version number for rolling migration" // *Cause: The command did not sepcify a valid version number. // *Action: Correct the version number in the command. It should be of the // form v#.#.#.#.# or other forms with fewer numbers delimited by // a period. The version number must be different from the current // software version of the instance. // 15152, 00000, "cluster in rolling upgrade" // *Cause: The cluster was already in the middle of rolling upgrade. // *Action: Rolling upgrade needs to be stopped before attempting to start // again. // 15153, 00000, "cluster is not in the rolling upgrade to %s" // *Cause: The cluster was not in the rolling upgrade. // *Action: Start the rolling upgrade using the ALTER SYSTEM START ROLLING // MIGRATION command from another ASM instance and restart this // instance. // 15154, 00000, "cluster rolling upgrade incomplete" // *Cause: The cluster was still performing rolling upgrade. // *Action: Ensure that all the instances in the cluster are upgraded before // retrying the command. // 15155, 00000, "version incompatible with the cluster" // *Cause: The current software version of the instance was incompatible with // the other members of the cluster. // *Action: Make sure that all the members of the cluster are at the same // version. If you are attempting to perform rolling upgrade, execute // ALTER SYSTEM START ROLLING command. Ensure that the version being // upgraded to is compatible with the existing version of the // cluster. // 15156, 00000, "cluster in rolling upgrade from version [%s] to [%s]" // *Cause: The current software version of the instance was incompatible with // the rolling upgrade operation of the cluster. // *Action: The version number of new member instance must be one of the two // versions involved in the rolling upgrade. // 15157, 00000, "rolling migration is not allowed" // *Cause: The cluster was not capable of handling ASM rolling migration. // *Action: The Oracle Cluster Services is using vendor clusterware. Oracle // cannot perform rolling upgrade or downgrade using vendor cluster // ware. Restart ASM instances using Oracle cluster ware and retry // the operation. // 15158, 00000, "rolling upgrade prevented by %s" // *Cause: One or more instances were blocking the rolling upgrade. // *Action: Terminate or wait until the reported operation is complete before // attempting the rolling upgrade to the cluster. // 15159, 00000, "Internal testing event" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: Traces execution of rolling upgrade. Level indicates verbosity of // tracing. // // 15160, 00000, "rolling migration internal fatal error in module %s,%s" // *Cause: Rolling migration experienced a fatal error. // *Action: Please contact Oracle support services. // 15161, 00000, "invalid SYS_CLUSTER_PROPERTIES parameter" // *Cause: The parameter passed in for SYS_CLUSTER_PROPERTIES is invalid // *Action: Pass in the correct parameter, refer to user documentation for // a list of allowed parameter values. // 15162, 00000, "cluster in rolling downgrade" // *Cause: The cluster was already in the middle of rolling downgrade. // *Action: Rolling downgrade needs to be stopped before attempting to start // again. // 15163, 00000, "cluster is not in the rolling downgrade to %s" // *Cause: The cluster was not in the rolling downgrade. // *Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING // MIGRATION command from another ASM instance and restart this // instance. // 15164, 00000, "cluster rolling downgrade incomplete" // *Cause: The cluster was still performing rolling downgrade. // *Action: Ensure that all the instances in the cluster are downgraded before // retrying the command. // 15166, 00000, "cluster in rolling downgrade from version [%s] to [%s]" // *Cause: The current software version of the instance was incompatible with // the rolling downgrade operation of the cluster. // *Action: The version number of new member instance must be one of the two // versions involved in the rolling downgrade. // 15168, 00000, "rolling downgrade prevented by %s" // *Cause: One or more instances were blocking the rolling downgrade. // *Action: Terminate or wait until the reported operation is complete before // attempting the rolling downgrade to the cluster. // 15169, 00000, "destination '%s' is a subdirectory of '%s'" // *Cause: Attempt to rename directory failed because the new directory name // was a subdirectory of the original directory. // *Action: Correct the path of the destination and try again. // 15170, 00000, "cannot add entry '%s' in directory '%s'" // *Cause: Other errors prevented directory/alias creation. // *Action: Correct the errors and try again. // 15171, 00000, "invalid syntax in the alias path after '%s'" // *Cause: An invalid alias/directory name syntax was specified. // *Action: Correct the alias path and try again. // 15173, 00000, "entry '%s' does not exist in directory '%s'" // *Cause: The specified alias did not exist in the given directory. // *Action: Correct the alias path and try again. // 15175, 00000, "cannot create alias for diskgroup metadata file '%s'" // *Cause: An attempt was made to create an alias for a diskgroup // metadata file. // *Action: Correct the alias path and try again. // 15176, 00000, "file '%s' already has an alias associated with it" // *Cause: An attempt was made to create an alias for a file that already had // an existing alias. // *Action: Correct the file name and try again or drop existing alias. // 15177, 00000, "cannot operate on system aliases" // *Cause: An attempt was made to modify a system alias. // *Action: Correct the alias name and try again. // 15178, 00000, "directory '%s' is not empty; cannot drop this directory" // *Cause: An attempt was made to drop a directory that contained valid // entries. // *Action: Correct the directory path or specify the FORCE option to drop a // directory that is not empty. // 15179, 00000, "missing or invalid alias name" // *Cause: The command did not specify a valid alias identifier. // *Action: Specify a valid alias identifier. // /============================================================================ / 15180 - 15189 Used for ASMLIB related error messages /============================================================================ / 15180, 00000, "could not open dynamic library %s, error [%s]" // *Cause: The library was not accessible // *Action: Correct the permissions of the library and try again. // 15181, 00000, "symbol [%s] not found in library %s, error [%s]" // *Cause: An error was encountered while loading the specified ASMLIB symbol. // *Action: Correct the error reported and try again. // 15182, 00000, "ASMLIB [%s] version mismatch, ORACLE version [%s]" // *Cause: The ASMLIB version reported is not supported by the ORACLE binary. // *Action: Install the correct library and try again. // 15183, 00000, "ASMLIB initialization error [%s]" // *Cause: Unable to initialize the ASMLIB in ORACLE. // *Action: Contact ASMLIB library vendor support with the error details. // 15184, 00000, "ASMLIB error could not be determined [%s] [%s]" // *Cause: An error was encountered which cannot be diagnosed further. // *Action: Contact ASMLIB libary vendor for support. / 15185, 00000, "could not close dynamic library %s, error [%s]" // *Cause: Could not close the dynamic library. // *Action: Contact ASMLIB libary vendor for support. // 15186, 00000, "ASMLIB error function = [%s], error = [%s], mesg = [%s]" // *Cause: An error occured during a call to function listed in the error. // *Action: The detailed message associated with the error is listed along with // the error. Correct the error and try again or contact ASMLIB // library vendor for support. 15187, 00000, "Incompatible RDBMS operation [%s] pushed to storage" // *Cause: RDBMS to storage version mismatched with incompatibility operation. // *Action: Upgrade RDBMS to match storage version. // /============================================================================ / 15190 - 15099 Used for ASM tracing and testing errors /============================================================================ / 15190, 00000, "Internal ASM testing event number 15190" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: The level controls which ASM disks encounter rebalance IO errors. // 15191, 00000, "Internal ASM testing event number 15191" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: The level controls which ASM errors are emulated. // 15192, 00000, "invalid ASM disk header [%s] [%s] [%s] [%s] [%s]" // *Cause: ASM encountered an invalid disk header. // *Action: Contact Oracle Support Services. // 15193, 00000, "Internal ASM tracing event number 15193" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: None. // 15194, 00000, "Internal ASM-DB interaction testing event number 15194" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: The level controls which ASM-DB operation is interuppted. // 15195, 00000, "Internal ASM testing event number 15195" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: The level controls which ASM errors are simulated. // 15196, 00000, "invalid ASM block header [%s:%s] [%s] [%s] [%s] [%s != %s]" // *Cause: ASM encountered an invalid metadata block. // *Action: Contact Oracle Support Services. // 15197, 00000, "suppressing %s additional ASM messages" // *Cause: The ASM command generated so many erorrs that this summary // message was reported in place of many individual messages. // *Action: If the command contained multiple actions, try separating // each action into its own command and executing each command // by itself. Otherwise, try not to generate so many errors. // 15198, 00000, "operation %s is not yet available" // *Cause: An unimplemented operation was attempted. // *Action: Consider upgrading to later releases as they become available. // 15199, 00000, "Internal ASM tracing event number 15199" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: Traces execution of ASM. Level indicates verbosity of tracing. // /============================================================================ / 15200 - 15206 ASM messages added in 10.2 /============================================================================ / 15200, 00000, "initialization parameter %s (%s) is not a power of two" // *Cause: The value specified for this initialization parameter was // not a power of two. // *Action: Correct the initialization parameter value and restart // the instance. // 15201, 00000, "disk %s contains a valid RDBMS file" // *Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ... // ADD DISK command appeared to contain a file from an existing // database. By default, ASM will not allow a diskgroup to be // created using this disk, as a safeguard against damaging an // existing database. // *Action: Check that the ASM disk specification is correct. Otherwise, // when storage from a defunct database is reused as part of an // ASM diskgroup, specify the FORCE option to the ASM SQL command. // 15202, 00000, "cannot create additional ASM internal change segment" // *Cause: The mount of a diskgroup by an additional instance in a RAC // cluster required more space for internal use by ASM than was // available in the diskgroup. // *Action: Delete unused files from the diskgroup or add additional disks // to the diskgroup and retry the operation. 15203, 00000, "diskgroup %s contains disks from an incompatible version of ASM" // *Cause: Diskgroup was created by an ASM instance with a higher // compatibility setting. // *Action: Use an ASM instance with the appropriate software version to mount // the diskgroup. 15204, 00000, "database version %s is incompatible with diskgroup %s" // *Cause: The database compatibility of the diskgroup was advanced to a later // version. // *Action: Upgrade the database instance to appropriate version of ORACLE. // 15205, 00000, "requested mirror side unavailable" // *Cause: The requested mirror side of a block is either unallocated or // allocated on a disk that has been dropped from the diskgroup. // *Action: Resubmit the request or try another mirror side. // 15206, 00000, "duplicate diskgroup %s specified" // *Cause: A command specified the same diskgroup twice. // *Action: Specify each diskgroup only once. // 15207, 00000, "Internal ASM testing event number 15207" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: The level controls which ASM errors are simulated. // 15208, 00000, "Internal ASM testing event number 15208" // *Document: NO // *Cause: Set this event only under the supervision of Oracle development. // *Action: The level controls which ASM errors are simulated. // 15209, 00000, "invalid block type read from disk" // *Document: NO // *Cause: ASM read a block whose block type was KFBTYP_INVALID. // *Action: None. This error is trapped and handled internally and will not // be exposed to end users. // /============================================================================ / 15210 - 15220 ASM SQL parsing messages added in 11.1 /============================================================================ 15210, 00000, "conflicting or duplicate PERMISSION options" // *Cause: The PERMISSION clause contained the USER, GROUP, or OTHER // keyword more than once. // *Action: Specify each keyword, at most, once. // 15211, 00000, "conflicting or duplicate OWNERSHIP options" // *Cause: The OWNERSHIP clause contained either the OWNER or the // GROUP keyword more than once. // *Action: Specify each keyword, at most, once. // 15212, 00000, "missing or invalid OWNER or GROUP name" // *Cause: The command did not specify a valid name for either the OWNER // or the GROUP keyword. // *Action: Specify a valid name for either the OWNER or the GROUP // keyword. // 15213, 00000, "command operates on only one attribute" // *Cause: More than one disk group attribute was specified in the // ALTER DISKGROUP statement. // *Action: Specify only one disk group attribute per ALTER DISKGROUP // statement. // 15214, 00000, "missing or invalid attribute specification" // *Cause: The command did not specify a valid attribute name // or a valid attribute value. // *Action: Specify a valid attribute name and value pair. // 15215, 00000, "missing or invalid user name" // *Cause: The command did not specify a valid user name. // *Action: Specify a valid user name. // 15216, 00000, "missing or invalid user group name" // *Cause: The command did not specify a valid user group name. // *Action: Specify a valid user group name. // 15217, 00000, "missing or invalid timeout value after DROP AFTER" // *Cause: The command did not specify a valid timeout value after // the DROP AFTER clause. // *Action: Specify a valid timeout value after the DROP AFTER clause. // 15218, 00000, "timeout value exceeded range" // *Cause: The OFFLINE timeout value exceeded the range of 0-136 // years, inclusive. 136 years are 49674 days, 1192176 // hours, and 71530560 minutes. // *Action: Specify a timeout value within the range of 0-136 // years, inclusive. // 15219, 00000, "conflicting or duplicate disk region options" // *Cause: The command contained one or more of the following: // - both the HOT and the COLD keywords // - both the MIRRORHOT and the MIRRORCOLD keywords // - the HOT keyword more than once // - the COLD keyword more than once // - the MIRRORHOT keyword more than once // - the MIRRORCOLD keyword more than once // *Action: Specify either the HOT or the COLD keyword and either the // MIRRORHOT or the MIRRORCOLD keyword, at most, once. // 15220, 00000, "invalid file attribute specification" // *Cause: The keyword UNPROTECTED, MIRROR, HIGH, FINE, or COARSE // was specified in a MODIFY FILE clause. These file attributes // are immutable once a file is created. // *Action: Specify a disk region keyword; for example, HOT, COLD, MIRRORHOT, // or MIRRORCOLD. // 15221, 00000, "ASM operation requires compatible.asm of %s or higher" // *Cause: The ASM operation specified requires a higher disk group // attribute value for compatible.asm. // *Action: Set the disk group attribute compatible.asm to or above the // requested version. // /============================================================================ / 15230 - 15250 ASM runtime error messages added in 11.1 /============================================================================ 15230, 00000, "diskgroup '%s' does not require the FORCE option" // *Cause: An attempt was made to MOUNT or DROP a disk group with the FORCE // option. // *Action: MOUNT and DROP diskgroup with the FORCE option are only // permitted if the diskgroup cannot be mounted normally. // 15231, 00000, "advancing diskgroup compatibility would exclude connected clients" // *Cause: Disk group compatibility could not be advanced because // connected clients were at a lower compatibility than // the target value. // *Action: Make sure all connected clients are at target compatibility // level or higher. // 15232, 00000, "cannot advance diskgroup compatibility due to offline disks" // *Cause: Disk group compatibilty could not be advanced because some // disks are offline. // *Action: Retry the command after offline disks are dropped. // 15233, 00000, "cannot advance diskgroup compatibility due to [%s]" // *Cause: Disk group compatibilty could not be advanced because of errors. // *Action: Check the alert log for more information on the reason for the // failure. // 15234, 00000, "target RDBMS compatibility (%s) exceeds ASM compatibility (%s)" // *Cause: An attempt was made to advance RDBMS compatibility beyond // the disk group's ASM compatibility. // *Action: Advance ASM compatibility before advancing RDBMS compatibility. // 15235, 00000, "diskgroup %s mount mode conflicts with existing mount" // *Cause: The mode specified in the diskgroup mount command conflicted with // the mode in which it was mounted on some other instance. // *Action: Specify a compatible mode in the diskgroup mount command. // 15236, 00000, "diskgroup %s mounted in restricted mode" // *Cause: The specified diskgroup was mounted in restricted mode prohibiting // client access. // *Action: Dismount the diskgroup and remount it in appropriate mode. // 15237, 00000, "attribute %s cannot be set in CREATE DISKGROUP" // *Cause: The specified attribute may not be set with the CREATE DISKGROUP // command. // *Action: Check the attribute name or use ALTER DISKGROUP SET ATTRIBUTE. // 15238, 00000, "%s is not a valid value for attribute %s" // *Cause: The specified value was not valid for the attribute. // *Action: Check the attribute name and value. // 15239, 00000, "allocation unit size higher than %s requires RDBMS compatibility %s" // *Cause: The allocation unit size requested exceeded the limit // imposed by the RDBMS compatibility setting. // *Action: Use a smaller allocation unit size or specify a // higher RDBMS compatibility setting. // 15240, 00000, "attribute name %s is invalid" // *Cause: The attribute name was not valid or was not recognized. // *Action: Check the attribute name. // 15241, 00000, "attribute %s is read only" // *Cause: The attribute value is read-only and cannot be changed. // *Action: None. The attribute value cannot be changed. // 15242, 00000, "could not set attribute %s" // *Cause: An error occurred while setting the attribute. // *Action: Look at the underlying error(s) on the error stack. // 15243, 00000, "%s is not a valid version number" // *Cause: The given version number was invalid, or not valid in this context. // *Action: Verify that the version number is valid and is appropriate // for this command. Check for additional errors reported. // 15244, 00000, "new compatibility setting less than current [%s]" // *Cause: The compatibility setting was invalid. The compatibility // setting can only be advanced. // *Action: Check the version number. // 15245, 00000, "ASM disk %s is already being brought online" // *Cause: An attempt was made to bring online a disk that is already // being brought online. // *Action: Change the ONLINE statement to exclude the disk. // 15246, 00000, "cannot bring ASM disk %s both online and then offline in the same statement" // *Cause: An attempt was made to bring the specified disk both online and // offline in the same statement. // *Action: Revise the statement to either bring the disk online or take the // disk offline. // 15247, 00000, "cannot specify both WAIT and NOWAIT options in the same statement" // *Cause: An attempt was made to specify both WAIT and NOWAIT options in the // same statement. // *Action: Revise the statement and include at most one option. // 15248, 00000, "ASM attributes feature not enabled" // *Cause: The ASM attributes feature was not enabled. // *Action: Advance disk group ASM compatibility to version 11.1.0 or newer. // 15249, 00000, "could not locate ASM attribute %s" // *Cause: The specified attribute could not be accessed. // *Action: Check the attribute name and examine underlying // error(s) on the error stack. // 15250, 0000, "insufficient diskgroup space for rebalance completion" // *Cause: The command attempted to reduce the available diskgroup space // below the current space used. // *Action: Consult V$ASM_DISK to determine the space requirements for the // diskgroup contents, and repeat the command after making the // required storage available. // 15251, 00000, "only restricted mount is allowed in the ASM instance" // *Cause: The ASM instance was started in restricted mode, and an attempt was // made to mount a diskgroup in non-restricted mode. // *Action: Start the ASM instance in non-restricted mode and mount the // diskgroup again, or mount the diskgroup in restricted mode. // // 15252, 00000, "user name '%s' does not exist in OS user dictionary" // *Cause: The specified user name was not a valid operating system user. // *Action: Specify a valid operating system user. // 15253, 00000, "user group name '%s' exceeds limit of %s characters" // *Cause: The length of the specified user group name exceeded the // maximum limit. // *Action: Reduce the length of the user group name to a value within // the limit. // 15254, 00000, "user group '%s' already exists in disk group" // *Cause: The specified user group name already existed in the disk group. // *Action: Specify a different user group name. // 15255, 00000, "user group '%s' does not exist in disk group '%s'" // *Cause: The specified user group name did not exist in the disk group. // *Action: Specify a valid user group name. // 15256, 00000, "user '%s' is already a member of user group '%s'" // *Cause: The specified user was already a member of the specified // user group. // *Action: Specify either an alternate user or an alternate user group. // 15257, 00000, "exceeded %s number of members per user group" // *Cause: The maximum number of members per user group was exceeded. // *Action: Delete existing members of the user group to create space. // 15258, 00000, "user group entry number must be between %s and %s, inclusive" // *Cause: The specified user group entry number was beyond the // acceptable range. // *Action: Specify a valid value for the user group entry number. // 15259, 00000, "user '%s' is not a member of user group '%s'" // *Cause: The specified user was not a member of the specified user group. // *Action: Specify either an alternate user or an alternate user group. // 15260, 00000, "permission denied on ASM disk group" // *Cause: An attempt was made to perform an operation on an ASM disk // group without the appropriate privileges. // // *Action: Ask the ASM administrator to perform the operation or grant // the required privileges. // 15261, 00000, "user '%s' already exists in disk group '%s'" // *Cause: The specified UID already existed in the disk group. // *Action: Specify a different UID. // 15262, 00000, "user '%s' does not exist in disk group '%s'" // *Cause: The specified UID did not exist in the disk group. // *Action: Specify a user with a valid UID. // 15263, 00000, "user name '%s' exceeds limit of %s characters" // *Cause: The length of the specified user name exceeded the // maximum limit. // *Action: Reduce the length of the user name to a value within // the limit. // 15264, 00000, "Operating system function returned error %s" // *Cause: An operating system error occurred. // *Action: Correct the operating system error and retry the operation. // 15265, 00000, "user identification number not in range of [%s,%s]" // *Cause: The operating system user identification number exceeded // the maximum value. // *Action: Change the user identification number to a value within // the accepted range. // 15266, 00000, "user identification number '%s' is not allowed" // *Cause: This user identification number is used internally by ASM. // *Action: Please choose a different user identification number. // 15267, 00000, "Internal ASM event number 15267" // *Document: NO // *Cause: Do not set this event. Used internally by Oracle. // *Action: None. // 15268, 00000, "internal Oracle file %s already exists." // *Cause: File was already in existence. // *Action: This is an internal error. Contact Oracle Support Services. // 15269, 00000, "group identification number not in range of [%s,%s]" // *Cause: The operating system group identification number exceeded // the maximum value. // *Action: Change the group identification number to a value within // the accepted range. // 15270, 00000, "disk %s is not a quorum disk" // *Cause: The specified disk was not a quorum disk. // *Action: Retry the operation without the quorum attribute for the disk. // 15271, 00000, "failgroup %s is a quorum failgroup" // *Cause: The specified failgroup was a quorum failgroup. // *Action: Retry the operation with the quorum attribute for the failgroup. // 15272, 00000, "failgroup %s is not a quorum failgroup" // *Cause: The specified failgroup was not a quorum failgroup. // *Action: Retry the operation without the quorum attribute for the failgroup. // 15273, 00000, "Could not create the required number of voting files." // *Cause: The required number of voting files could not be created. See // accompanying messages for possible causes. // *Action: See accompanying messages for possible actions. // 15274, 00000, "Not enough failgroups (%s) to create voting files" // *Cause: The number of failgroups required for this redundancy were not // present in the diskgroup to create voting files. // *Action: Retry the operation after creating new failgroup(s). // 15275, 00000, "Not enough contiguous space (%s AUs) in disk %s to allocate a voting file" // *Cause: The specified disk did not have enough space to allocate a voting // file on it. // *Action: Ensure that there is at least 1 disk with the required space in // atleast the required number of failgroups for the diskgroup. // 15276, 00000, "ASM diskgroup %s has cluster voting files" // *Cause: An attempt was made to drop a diskgroup that contained cluster // voting files. // *Action: Move the cluster voting files out of the diskgroup and retry the // operation. // 15277, 00000, "disk %s is a quorum disk" // *Cause: The specified disk was a quorum disk. // *Action: Retry the operation with the quorum attribute for the disk. // 15278, 00000, "external redundancy diskgroup requires at least one regular disk" // *Cause: An attempt was made to create an external redundancy diskgroup // with only quorum disks. // *Action: Specify atleast one regular disk to create an external redundancy // diskgroup. // 15279, 00000, "user '%s' is currently being deleted" // *Cause: The specified user was in the process of being deleted and // could not be used. // *Action: Either abandon this operation or specify a different user. // 15280, 00000, "user '%s' owns existing files" // *Cause: An attempt was made to drop a user that still owns existing // files. // *Action: Specify the INCLUDING CONTENTS option to drop the user and // all of the owned files. // /============================================================================ / 15252 - 15280 Reserved for TrailBlazer /============================================================================ 15281, 00000, "not all specified disks were brought ONLINE" // *Cause: Some of the disks specified either experienced // I/O errors while being brought ONLINE, or were simultaneously // brought OFFLINE or dropped in another session, or were full. // *Action: Query V$ASM_DISK or use ASMCMD LSDSK to determine which disks were // not brought ONLINE. Inspect any additional error messages and // the alert log to determine the exact cause. If some of the disks // failed, either fix the cause of the failures or drop the disks. // If some of the disks are full, either free space in the disk group // or add new disks to the diskgroup. // 15282, 00000, "ASM disk \"%s\" is not visible cluster-wide" // *Cause: An ALTER DISKGROUP ONLINE command specified a disk that could not // be discovered by one or more nodes in a RAC cluster configuration. // *Action: Check operating system permissions for the device and the storage // sub-system configuration on each node in the RAC cluster that // cannot identify the disk. // 15283, 00000, "ASM operation requires compatible.rdbms of %s or higher" // *Cause: The ASM operation specified requires a higher disk group // attribute value for compatible.rdbms. // *Action: Set the disk group attribute compatible.rdbms to or above the // requested version. // 15284, 00000, "ASM terminated ALTER DISKGROUP ONLINE" // *Cause: None of the disks specified by ALTER DISKGROUP ONLINE could be // brought ONLINE. // *Action: Inspect additional error messages and the alert log to determine // why the specified disks cannot be brought ONLINE. // 15285, 00000, "disk '%s' violates disk group attribute %s" // *Cause: Including the specifed disk would violate a restriction imposed by // the specified disk group attribute. // *Action: Retry the operation while omitting the offending disk or // change the attribute. // 15286, 00000, "could not set disk group attribute %s due to offline disks" // *Cause: The specified disk group attribute could not be set because // the disk group includes offline disks. // *Action: Retry the operation after the offline disks in this disk group // are dropped or brought online. // 15287, 00000, "could not set disk group attribute %s due to incompatible disks" // *Cause: The specified disk group attribute could not be set because // the disk group includes disks that conflict with the new value. // *Action: Retry the operation after dropping the conflicting disks // in this disk group. // 15288, 00000, "disk(s) require disk group attribute %s clause" // *Cause: Some of the disks specified by the command also require the // specified disk group attribute to be stated. // *Action: Retry the command including an ATTRIBUTE clause for the // required disk group attribute. Alternatively, omit the disks // that require setting the disk group attribue. See the alert log // for additional information on the disks that require setting // the disk group attribute. 15289, 00000, "ASM disk %s cannot be resized beyond %s M" // *Cause: A resize disk command specified a size beyond the maximum allowed // for this disk. // *Action: Check alert logs from all ASM instances to identify the reason // for the size limitation. If there are any 10g database instances // using this disk group, shut down those instances and retry the // resize operation. 15290, 00000, "operation not permitted on offline disk %s" // *Cause: An attempt was made to specify an operation that is only permitted // on disks that are online. The specified disk was not online. // *Action: Online the disk or wait for online to complete before retrying the // operation. 15291, 00000, "ASM could not add disk \"%s\" to disk group \"%s\"" // *Cause: An attempt was made to add a disk to a disk group while the // distribution of disks in failure groups was too uneven. // *Action: Add or drop disks to or from failure groups to balance their // distribution in all failure groups and retry the operation. 15292, 00000, "Disk name %s is being used by another disk" // *Cause: The specified disk name could not be reused because an 11.1.0.6.0 // or earlier database instance had it cached in memory. // *Action: Do one of the following // - Specify a different name for the disk. // - Wait for the rebalance to complete successfully. // - Identify the database instance with the problem and shut it down // before retrying the command. // 15293, 00000, "operation disallowed by ASM_POWER_LIMIT" // Cause: This operation required data movement in order to complete // successfully. However, ASM_POWER_LIMIT was set to zero, // thereby preventing this operation. // Action: Repeat the operation after setting ASM_POWER_LIMIT to a // non-zero value. // 15294, 00000, "SYSASM privilege not allowed on database instance" // Cause: The SYSASM privilege was not allowed on this database instance; // it is allowed only on an ASM instance. // Action: Use either the SYSDBA or the SYSOPER privilege. // 15295, 00000, "ASM instance software version %s less than client version %s" // Cause: The ASM instance software version was less than the client version. // Action: Upgrade the ASM instance software. Check the alert log for // more information on the reason for the failure. // 15296, 00000, "POWER disallowed by diskgroup compatibility" // *Document: NO // *Cause: The rebalance power was not allowed due to the diskgroup // compatiblity. // *Action: None. // 15297, 00000, "extent pointer %s for file %s block %s%s does not exist" // Document: NO // Cause: This is an internal error in ASM. End users will never see this // error. It is raised when kfcInitPba attempts to extract the // extent pointers from a locator block and finds they are KFXP_NODISK // or KFXP_NOEXT. An external error is used because sometimes this // error needs to be caught and ignored. // Action: None. End users will not see this error. // 15298, 00000, "possible lost disk write detected during crash recovery" // Cause: ASM crash recovery read a block who's version was older than // expected. // Action: None. End users will not see this error. ASM automatically // traps this error and attempts a fallback recovery. // 15299, 00000, "FINE striping not allowed for the Staleness Registry" // Cause: An SQL command attempted to set the striping attribute of the // ASM_STALE template to FINE striping. // Action: Do not modify the striping attribute of the ASM_STALE template. // 15300, 00000, "File %s is incompatible with this operation" // Cause: The file type was incompatible with the operation. // Action: Use another file of the correct type. // 15301, 00000, "cannot change %s of the open file '%s'" // *Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on // an open file. // *Action: Close the file and retry the SQL command. // 15302, 00000, "active use of files owned by user '%s' precludes its drop" // *Cause: A DROP USER command specified a user owning files that // were in use. // *Action: Close all files owned by this user. // 15303, 00000, "Voting files could not be created in diskgroup %s due to small Allocation Unit size" // *Cause: An attempt was made to create voting files in a diskgroup with a // small Allocation Unit size. // *Action: Create voting files in a different diskgroup whose Allocation Unit // size is at least 1 mega byte. 15304, 00000, "operation requires ACCESS_CONTROL.ENABLED attribute to be TRUE" // *Cause: An attempt was made to run an operation that required the // ACCESS_CONTROL.ENABLED attribute to be set to TRUE, but its // existing state was FALSE. // *Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE and retry // the operation. // 15305, 00000, "cannot operate on ASM internal files" // *Cause: An attempt was made to operate on Automatic Storage Management // (ASM) metadata used to manage the diskgroup. // *Action: Check the specified ASM file name. // 15306, 00000, "ASM password file update failed on at least one node" // *Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE // command failed on at least one node of the Automatic Storage // Management (ASM) cluster. // *Action: Check the ASM alert logs for more information. // 15307, 00000, "disk %s not discoverable by CSS; diskgroup %s has CSS voting files" // *Cause: An attempt was made to add a disk which cannot be discovered by // Cluster Synchronization Services (CSS). // CSS has voting files in the disk group and will not be able // to use the new disk if CSS cannot discover the disks. // *Action: Update the Automatic Storage Management (ASM) disk string in the // Grid Plug and Play (GPnP) profile to include the // specified disk and retry the operation. Alternatively, // migrate the CSS voting files out of the diskgroup and retry // the operation 15308, 00000, "could not access ASM SPFILE in RDBMS instance" // *Cause: A relational database management system (RDBMS) instance // attempted to access an Automatic Storage Management (ASM) SPFILE. // *Action: Connect to an ASM instance and reissue the command. // Alternatively, specify an RDBMS SPFILE. 15309, 00000, "could not access database SPFILE in ASM instance" // *Cause: An Automatic Storage Management (ASM) instance attempted to access // a relational database management system (RDBMS) SPFILE. // *Action: Connect to an RDBMS instance and reissue the command. // Alternatively, specify an ASM SPFILE. // 15310, 00000, "process terminated due to signal" // *Cause: A process was terminated as a result of a signal in the I/O path. // *Action: Reconnect to the database or the ASM instance. If the process // termination resulted in instance termination, restart the // instance. // 15311, 00000, "process terminated due to fenced I/O" // *Cause: A process was terminated because it was fenced from doing // any more I/Os. // *Action: Reconnect to the database or the ASM instance. If the process // termination resulted in instance termination, restart the // instance. // 15312, 00000, "invalid file type" // *Cause: Automatic Storage Management (ASM) could not determine the // type of file. // *Action: The file specified is not supported with Automatic Storage // Management (ASM). Specify a supported file type for the // operation. // 15314, 00000, "Internal ASM event number 15314" // *Document: NO // *Cause: Do not set this event. Used internally by Oracle. // *Action: None. // 15315, 00000, "Write errors in disk group %s could lead to inconsistent ASM metadata." // *Cause: One or more failures occurred while writing ASM metadata to disk. // *Action: Repair the hardware problem and remount the disk group. // Check the accompanying errors and alert log for the // disks which reported the error. 15318, 00000, "disks in disk group %s cannot be resized" // *Cause: Execution of ASM Storage Reclamation Utility script was incomplete // on the specified disk group. // *Action: Execute ASM Storage Reclamation utility on the disk group to // complete the operation. // /============================================================================ / 15400 - 15449 ASM appliance error messages /============================================================================ 15400, 00000, "not running on supported ASM appliance" // *Cause: An attempt was made to initialize the server code as an appliance // when it was not running a supported appliance configuration. // *Action: Check the appliance configuration and retry the operation. // 15401, 00000, "command not supported on ASM appliance '%s'" // *Cause: An attempt was made to run an operation that is not supported by // the specified appliance. // *Action: Check the documentation to see which operations are allowed or // disallowed for the specified appliance. // 15402, 00000, "insufficient number of disks to support ASM appliance '%s'" // *Cause: An attempt was made to do an operation that resulted in insufficient // number of disks required for the specified appliance. // *Action: Check the appliance configuration and retry the operation after // inserting disks in the appropriate slots. // 15403, 00000, "unable to read an ASM appliance configuration file" // *Cause: Oracle ASM was unable to read an appliance configuration file. // *Action: Check the operating system error messages to determine the // identity of the configuration file. Then, fix the // configuration file. // 15404, 00000, "Oracle ASM could not add disk \"%s\" to disk group \"%s\" on appliance %s" // *Cause: There were too many dropping or offline disks in the specified // disk group. // *Action: Wait for the drop and rebalance operations to complete, or // online the offline disks and wait for the online to complete. // Then, retry the operation. // 15405, 00000, "Slot %s in Oracle ASM appliance '%s' contains more than one disk" // *Cause: An attempt was made to add a disk to a slot in the ASM appliance that // already had a disk (possibly OFFLINE) associated with it. // *Action: Use FORCE to drop the disk that exists in the specified slot. Then, // retry the operation. // /============================================================================ / 15450 - 15499 ASM Volume Messages /============================================================================ 15450, 00000, "invalid volume name specifier" // *Cause: The volume name specified was invalid // *Action: Specify a valid volume name. // 15451, 00000, "missing or invalid volume size specifier" // *Cause: The volume size specified was invalid. // *Action: Specify a valid volume size. // 15452, 00000, "missing or invalid stripe width specifier" // *Cause: The volume stripe width specified was invalid. // *Action: Specify a valid volume stripe width. // 15453, 00000, "invalid STRIPE_COLUMNS specifier" // *Cause: An ADD VOLUME command did not specify a valid number of stripe // columns. // *Action: Specify a valid number of stripe columns. // 15454, 00000, "ALTER DISKGROUP ALL cannot use single volume names" // *Cause: An ALTER DISKGROUP ALL command specified a single volume or // a list of volumes // *Action: Use the ALL keyword when specifying volumes on multiple diskgroups. // 15455, 00000, "FORCE option cannot be used when specifying ALL volumes" // *Cause: The FORCE option was used to disable ALL volumes. // *Action: Use FORCE option to disable one volume at a time. // 15456, 00000, "missing or invalid volume usage specifier" // *Cause: The command did not specify a valid volume usage string. // *Action: Specify a valid volume usage string with alphanumeric characters. // 15457, 00000, "first letter of the volume name is not alphabetic" // *Cause: A volume name was specified with a nonalphabetic first character. // *Action: Set the first character of the volume name to be alphabetic. // 15458, 00000, "invalid character in volume name" // *Cause: A volume name was specified with an invalid character. // *Action: Use a volume name with only alphanumeric characters. // 15459, 00000, "STRIPE_WIDTH of %s is not a power of two" // *Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was not // a power of two. // *Action: Select a STRIPE_WIDTH that is a power of two; for example, // 4K, 8K, etc. // 15460, 00000, "volume name '%s' is already in use" // *Cause: An ADD VOLUME command specified a volume name that // was already used by another volume. // *Action: Select a different name for the volume. // 15461, 00000, "STRIPE_WIDTH of %s bytes is less than the minimum of %s bytes" // *Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too // small. // *Action: Select a larger STRIPE_WIDTH. // 15462, 00000, "STRIPE_WIDTH of %s bytes is greater than the maximum of %s bytes" // *Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too // large. // *Action: Select a smaller STRIPE_WIDTH. // 15463, 00000, "volume size of %sK is less than the minimum of %sM" // *Cause: The volume size specified was too small. // *Action: Select a larger volume size. // 15464, 00000, "STRIPE_COLUMNS of %s is greater than the maximum of %s" // *Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was that // was too large. // *Action: Select a smaller STRIPE_COLUMNS value. // 15465, 00000, "STRIPE_COLUMNS of %s is less than the minimum of %s" // *Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was too // small. // *Action: Select a larger STRIPE_COLUMNS value. // 15466, 00000, "volume name '%s' does not exist" // *Cause: The command specified a volume name that does not exist. // *Action: Ensure a valid volume name is used. // 15467, 00000, "volume operation is already in progress" // *Cause: Another command was currently operating on a volume. // *Action: Wait a short time before retrying the command. // 15468, 00000, "volume '%s' in diskgroup '%s' is currently being accessed" // *Cause: An attempt was made to communicate with the volume driver. // The volume was being accessed by another application and, // therefore, could not be changed. // *Action: Shut down all applications that might be accessing // this volume and then retry the command. // 15469, 00000, "VBG process terminated with error" // *Cause: A volume background process terminated with error. // *Action: Wait for process to restart. // 15470, 00000, "VDBG process terminated with error" // *Cause: The volume driver background process terminated with error. // *Action: Warm start instance. // 15471, 00000, "volume redundancy incompatible with diskgroup redundancy" // *Cause: An ADD VOLUME command specified a volume redundancy that was // incompatible with the diskgroups redundancy. // *Action: Specify a valid volume redundancy. A volume cannot have external // redundancy with a high redundancy diskgroup. Also, a volume // cannot have high redundancy with an external redundancy diskgroup. // 15472, 00000, "volume library cannot be loaded. Platform may not support volume creation." // *Cause: The volume library could not be loaded. Either the platform // does not support volume operations, or there is a problem with // the library. // *Action: Ensure that the platform supports volumes. If the platform does // support volumes, check the alert log for library loading failure // information. // 15473, 00000, "access to a volume's storage through an unsupported interface" // *Cause: An attempt was made to access or modify a volume's storage through // an unsupported interface. // *Action: Use supported interfaces for access to volume devices. // 15474, 00000, "volume name is greater than %s characters" // *Cause: An ADD VOLUME command specified a volume name that was too long. // *Action: Select a smaller volume name. // 15475, 00000, "usage string is greater than %s characters" // *Cause: The usage string specified was too long. // *Action: Select a smaller usage string. // 15476, 00000, "ACFS volumes must be resized with the 'acfsutil size' operating system command." // *Cause: An attempt was made using SQL to resize an ADVM volume that // contains an ACFS file system. // *Action: Use the 'acfsutil size' operating system command to resize // the volume. // 15477, 00000, "cannot communicate with the volume driver" // *Cause: An attempt was made to communicate with the volume driver. // *Action: Check that the ASM volume driver is loaded. If so, check the alert // log to identify the reason for failure and take necessary action // to prevent such failures in the future. // 15478, 00000, "ACFS process terminated with error" // *Cause: The ACFS background process terminated with error // *Action: Wait for process restart // 15479, 00000, "ASM diskgroup does not support volumes" // *Cause: Volumes were not supported. A common example // is having disks, such as NFS, in the diskgroup that are not // supported by volumes. // *Action: Remove unsupported disks in the diskgroup. // 15480, 00000, "error reported in the ASM volume driver" // *Cause: An error was reported in the ASM volume driver. // *Action: Check the operating system log files to identify the reason for // the failure and take necessary action to prevent such failures // in the future. // 15481, 00000, "missing or invalid volume mountpath specifier" // *Cause: A invalid volume mountpath string was specified. // *Action: Specify a valid volume mountpath string with alphanumeric characters. // 15482, 00000, "failed to create/remove device file for volume %s on diskgroup %s" // *Cause: Improper driver installation. // *Action: Check the alert log for device file creation failure information. // Reload the driver using the supported installation method. // 15483, 00000, "volume driver version is not compatible with the ASM instance" // *Cause: The version of the ASM volume driver was not supported by ASM. // *Action: Update the volume driver or the ASM instance. // 15484, 00000, "volume '%s' contains %s error(s)" // *Cause: Errors were returned by the ALTER DISKGROUP CHECK VOLUME command. // *Action: See the alert log for details of the errors. // 15485, 00000, "number of volumes in diskgroup exceeds the maximum of %s" // *Cause: A volume was added on a diskgroup that already contained the maximum number allowed. // *Action: Remove volumes on the diskgroup. // 15486, 00000, "internal error while altering volume" // *Cause: An internal ASM error occurred while altering a volume. // *Action: See the alert log for details of the error. // 15487, 00000, "cannot shutdown the ASM instance with an open ASM volume" // *Cause: One or more ASM volumes were found to be open during shutdown. // *Action: Close the ASM volume and retry the shutdown. // 15488, 00000, "volume %s is open on instance %s" // *Cause: ASM volume was not closed prior to instance termination // on node specified. // *Action: Close the ASM volume either via unmount or node restart and // retry the operation // 15489, 00000, "conflicting volume already open on this node" // *Cause: An ASM volume was not closed prior to instance shutdown // on node specified. It is conflicting with the volume that // is to be enabled. // *Action: Close the ASM volume either via unmount or node restart and // retry the operation. // 15490, 00000, "not all instances could add/drop the volume" // *Cause: The ASM volume cannot be added/dropped on all instances. // *Action: See the alert log for the reason the volume could not be // added/droped. // 15491, 00000, "volume redundancy conflicts with disk region options" // *Cause: Non-mirrored volumes erroneously contained the MIRRORHOT or // MIRRORCOLD keyword. // *Action: Remove the MIRRORHOT or MIRRORCOLD keywords from non-mirrored // volumes. 15492, 00000, "command or option incompatible with ASM volumes" // *Cause: An attempt was made to use a feature which is not // compatible with existing ASM volumes. A common example is // adding a disk to the diskgroup that is unsupported by ASM // volumes. // *Action: Omit the option from the command. 15493, 00000, "target ADVM compatibility (%s) exceeds ASM compatibility (%s)" // *Cause: An attempt was made to advance ADVM compatibility beyond // the disk group's ASM compatibility. // *Action: Advance ASM compatibility before advancing ADVM compatibility. 15494, 00000, "compatible.advm must be %s or higher" // *Cause: An attempt was made to set the ADVM compatibility to a version // that was lower than the minimum supported. // *Action: Set ADVM compatibility to at least the minimum supported // version. 15495, 00000, "ASM operation requires compatible.advm of %s or higher" // *Cause: The ASM operation specified required a higher disk group // attribute value for compatible.advm. // *Action: Set the disk group attribute compatible.advm to or above the // requested version. 15496, 00000, "volume size is greater than the maximum of %sT" // *Cause: The volume size specified was too large. // *Action: Select a smaller volume size. 15497, 00000, "diskgroup uses a sector size that is incompatible with volumes" // *Cause: The diskgroup used a sector size that was not 512 bytes. // *Action: Create the volume in a diskgroup with a sector size of 512 bytes. 15498, 00000, "Volume name '%s' would collide with existing volume(s) '%s %s'." // *Cause: A volume name was specified that would conflict with existing // volume device(s). A volume '-' is the name of the // block device. Additionally, a raw device named // 'r-' is also created. Since that name already // existed, a name collision occurred. // *Action: Choose another name for the volume (no leading 'r' is recommended). /=============================================================================== / 15500 - 15999 Reserved for Server Manageability Layer / / 15500-15599 Reserved for Workload Capture and Replay (KEC) / 15600-15649 Reserved for Automated Maintenance Tasks (KET) / 15650-15699 Reserved for Direct Access to Fixed Tables / 15700-15749 Reserved for SQL Tuning Advisor, SQL Tuning Set and SQL / Performance Analyzer (STA/STS/SPA) /=============================================================================== / / 15500 - 15599 reserved for Workload Capture and Replay (KEC) / 15500, 00000, "Reserved for Workload Capture and Replay tracing" // *Document: NO // *Cause: // *Action: // 15501, 00000, "cannot start workload capture on instance %s" // *Cause: Given instance encountered unexpected errors while trying // to start the workload capture. // *Action: Check the alert log and other diagnostics in the given // instance to diagnose the problem. // 15502, 00000, "cannot stop workload capture on instance %s" // *Cause: Given instance encountered unexpected errors while trying // to stop the workload capture. // *Action: Check the alert log and other diagnostics in the given // instance to diagnose the problem. // 15503, 00000, "cannot startup instance when procedures in \"DBMS_WORKLOAD_CAPTURE\" or \"DBMS_WORKLOAD_REPLAY\" are in the middle of their execution" // *Cause: The new instance could not be started because the database // was executing a procedure in either the DBMS_WORKLOAD_CAPTURE // or DBMS_WORKLOAD_REPLAY package. // *Action: Start the new instance after such procedures in the // given packages have finished execution. // 15504, 00000, "cannot start workload capture because instance %s not present in RESTRICTED SESSION mode" // *Cause: The NO_RESTART_MODE option in DBMS_WORKLOAD_CAPTURE.START_CAPTURE // was FALSE, therefore all the active instances were expected to be // in the RESTRICTED SESSION mode. // *Action: Start all instances using STARTUP RESTRICT or // execute ALTER SYSTEM ENABLE RESTRICTED SESSION on all active // instances before issuing DBMS_WORKLOAD_CAPTURE.START_CAPTURE. // 15505, 00000, "cannot start workload capture because instance %s encountered errors while accessing directory \"%s\"" // *Cause: Given instance could not access the specified CAPTURE directory // or the specified CAPTURE directory already had a workload capture // in it. // *Action: Provide a directory object that is valid, empty and // accessible from all the instances in the database cluster. // 15506, 00000, "cannot prepare instance %s for replay" // *Cause: Given instance encountered unexpected errors while trying // to prepare for a workload replay. // *Action: Check the alert log and other diagnostics in the given // instance to diagnose the problem. // 15507, 00000, "cannot start workload replay on instance %s" // *Cause: Given instance encountered unexpected errors while trying // to start a workload replay. // *Action: Check the alert log and other diagnostics in the given // instance to diagnose the problem. // 15508, 00000, "cannot cancel workload replay on instance %s" // *Cause: Given instance encountered unexpected errors while trying // to cancel a workload replay. // *Action: Check the alert log and other diagnostics in the given // instance to diagnose the problem. // 15509, 00000, "workload replay has been cancelled" // *Cause: Workload replay was cancelled. // *Action: Restart the workload replay. // 15510, 00000, "cannot perform operation when \"STATISTICS_LEVEL\" is \"BASIC\"" // *Cause: The STATISTICS_LEVEL initialization parameter was set to BASIC. // *Action: Change the STATISTICS_LEVEL initialization parameter setting to either TYPICAL or ALL. // 15511, 00000, "cannot process workload capture because no user sessions were recorded" // *Cause: No user sessions were recorded in the given workload capture. // Processing this capture failed because no user workload was // captured. // *Action: Capture a workload in which at least one user session connects and // performs some operations. // 15512, 00000, "directory \"%s\" does not contain a valid processed workload capture" // *Cause: One or more files created by DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE // were missing. // *Action: Process the workload capture using DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE // and then retry the command. // 15513, 00000, "cannot access the input directory" // *Cause: Given input directory is either invalid or inaccessible. // *Action: Verify that the input directory is valid and accessible // and then retry the command. // 15514, 00000, "cannot find a match for the remote procedure call during replay" // *Cause: The corresponding PL/SQL program was either dropped or modified. // *Action: Verify that the corresponding PL/SQL program is defined the same // way during replay as it was defined during workload capture. // 15515, 00000, "error while replaying remote procedure call: \"%s.%s.%s\"" // *Cause: Error encountered during the replay of a remote procedure call. // *Action: Correct the cause of the preceding error and restart workload replay. // 15516, 00000, "parallel preprocessing worker hit error ORA-%s" // *Cause: One of the parallel preprocessing workers died unexpectedly while // processing the workload. // *Action: Find the root cause or simply preprocess the workload using only // one process. // 15517, 00000, "cannot start parallel preprocessing worker" // *Cause: One of the parallel preprocessing workers could not be started. // *Action: Find the root cause or simply preprocess the workload using only // one process. // 15518, 00000, "parallel preprocessing encountered an unexpected error" // *Cause: An unexpected error occured during parallel preprocessing. // *Action: Find the root cause or simply preprocess the workload using only // one process. // 15519, 00000, "cannot access database link \"%s\" because it is disabled" // *Cause: For security considerations, access to external databases via // database links were disabled during workload replay. // *Action: Use advanced parameter for Database Replay to enable // database links during workload replay. // 15520, 00000, "Directory is corrupted. Two WMD files are found at \"%s\" and \"%s\"" // *Cause: Two WMD files were found in the directory. // *Action: Check that the WMD files in capture directory were not modified, // moved, duplicated or deleted. // 15521, 00000, "failed to create file \"%s\" during workload processing" // *Cause: An attempt was made to create a file during workload processing // without the proper file permissions. // *Action: Correct the file permissions and try again. // 15551, 00000, "workload replay client cannot connect to database server" // *Cause: The server connection identifier was invalid. // *Action: Restart the client with correct server connection identifier. // 15552, 00000, "workload replay client cannot login to database server" // *Cause: 1) the replay client used an invalid username or password; // 2) the replay user does not have the privilege to switch user; // 3) the recorded username does not exist in the replay database. // *Action: 1) restart replay client with correct username and password // 2) grant user switching prvilege to the replay user // 3) verify whether the replay database was restored properly // 15553, 00000, "workload replay client cannot execute the DBMS_WORKLOAD_REPLAY package" // *Cause: Workload Replay Client's replay user did not have EXECUTE // permission on the DBMS_WORKLOAD_REPLAY package. // *Action: Grant execute permission on the DBMS_WORKLOAD_REPLAY package // to replay user and restart the Workload Replay Client. // 15554, 00000, "cannot start workload replay client because the database server is not in PREPARE mode" // *Cause: The Workload Replay Client could not connect to the database // server because the database server was not in the PREPARE mode. // *Action: Put the database in PREPARE mode by using // DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY, and restart the // Workload Replay Client. // 15555, 00000, "workload replay client encountered unexpected error: \"%s\"" // *Cause: Workload Replay Client encountered an unexpected error. // *Action: Check the Workload Replay Client's log files and the database // server alert log to diagnose the problem. // 15556, 00000, "invalid input specified to the workload replay client" // *Cause: Invalid input was specified. // *Action: Use the Workload Replay Client's HELP=Y option to know more about // valid input options. // 15557, 00000, "workload replay client cannot access the replay directory or the database version do not match the preprocessing one" // *Cause: The Workload Replay Client could not access the directory that // contained the workload to be replayed, or the workload was // preprocessed by a different version of the database. // *Action: Restart the workload replay after specifying the correct // replay directory, or preprocess it with the correct database. // 15558, 00000, "replay thread encountered unexpected error" // *Cause: A single replay thread got disconnected from the server due to an unexpected error. // *Action: Check the Workload Replay Client's log files and the database // server alert log to diagnose the problem. // 15559, 00000, "workload replay client cannot open workload capture file" // *Cause: The Workload Replay Client could not access one or more workload // capture files from the replay directory. // *Action: Restart the workload replay after copying all the workload // capture files to the replay directory. // 15560, 00000, "workload replay client cannot access the work directory" // *Cause: The Workload Replay Client could not access the work directory to // write log files for debug information. // *Action: Restart the Workload Replay Client after specifying the correct // work directory. 15561, 00000, "workload replay client cannot connect to the remapped connection with conn_id : %s" // *Cause: The specified connection is invalid or the specified host // is inaccessible. // *Action: Test the specified connection using other methods and redefine // the connection remapping, if necessary. Consult the view // DBA_WORKLOAD_CONNECTION_MAP to inspect connection remappings. // 15562, 00000, "workload replay client cannot read the DBA_WORKLOAD_CONNECTION_MAP view" // *Cause: The DBA_WORKLOAD_CONNECTION_MAP view did not exist or // was not accessible. // *Action: Re-create the workload capture and replay views. For additional // information, see the documentation. // 15563, 00000, "workload replay client cannot spawn new threads" // *Cause: The Workload Replay Client does not have enough resource (CPU or memory) // to spawn new threads. // *Action: Restart the workload replay after allocating more resource // (CPU and memory) to the Workload Replay Client or use // more hosts as replay clients to drive the workload. // 15564, 00000, "contents of the replay directory provided to the workload replay client do not match with the replay directory provided to the database server" // *Cause: The processed workload capture files given to the workload replay // client directory did not match the contents of the replay directory // given as input to DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY. // *Action: Provide the same processed workload capture files to both the // database server and all the workload replay clients and restart the // replay. If the same workload capture files were processed more // than once, provide a copy of the latest processed workload // capture files to all the workload replay clients and the // database server. // 15566, 00000, "workload replay client cannot replay user call in the current version" // *Cause: The workload replay client encountered a user call in the // captured workload that was not supported for replay in the current version. // *Action: Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details about the call // that encountered this error. Refer to the documentation for more // details on the types of workload that are not supported in the // current version. // 15567, 00000, "replay user %s encountered an error during a sanity check" // *Cause: The replay user encountered an error when accessing internal objects // for Database Replay or switching user. // *Action: Set up the replay user appropriately at the replay database. Make sure // the replay user can access SYS-owned objects and has BECOME USER privilege. // 15568, 00000, "login of user %s during workload replay failed with ORA-%s" // *Cause: The recorded user did not exist in the replay database or encountered // other problems during log in. // *Action: Check the returned error number and set up the recorded user // appropriately at the replay database. // 15569, 00000, "timeout encountered during the replay of a recorded user call" // *Cause: The replay of a recorded user call was terminated since it was // significantly slower than the workload capture. // *Action: Find the root cause for the performance issue. Or, use // DBMS_WORKLOAD_REPLAY API to disable the timeout check if the // replay is expected to be slower. // 15590, 00000, "encountered incomplete workload capture files" // *Cause: The captured workload contained one or more incomplete recording // files. This can happen when the original workload capture's // FINISH_CAPTURE command timed out while waiting for all the active // sessions to close their workload capture files. // *Action: Incomplete capture files will not interfere with the processing // and replaying of the captured workload. This is simply a warning // message to point out that some database calls might not have been // recorded due to FINISH_CAPTURE command timing out. For a list // of the incomplete files, check the alert log for lines containing // DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing. // 15591, 00000, "encountered corrupt workload capture files" // *Cause: The captured workload contained one or more corrupt recording // files. // *Action: For a list of the incomplete files, check the alert log for // lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after // capture processing. The corrupt files will be replayed up to the // point of the corruption. Alternatively, it is possible to // remove the corrupt files and run // DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE again. In this case, no // workload from the corrupt files will be replayed. // 15599, 00000, "Last message reserved for WCR (KEC)" // *Document: NO // *Cause: // *Action: // / / 15600 - 15649 reserved for Automated Maintenance Tasks (KET) / 15600, 00000, "Reserved for Automated Maintenance Tasks" // *Document: NO // *Cause: // *Action: // / 15601, 00000, "Invalid value specified for parameter \"%s\"" // *Cause: An invalid value was specified for the given parameter. // *Action: Correct the value being specified for the parameter. / 15602, 00000, "Parameter \"%s\" cannot be NULL." // *Cause: An attempt was made to call a procedure without a // required parameter. // *Action: Specify a valid value for this parameter. / 15603, 00000, "Action cannot be performed when database is in read-only mode." // *Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database // was open in read-only mode. // *Action: Retry when database is open in read/write mode. / 15604, 00000, "Initialization parameters prevent client from being enabled." // *Cause: An attempt was made to enable a client that was disabled // for automatic execution by an initialization parameter. // *Action: Check the related client parameters and try again. / 15605, 00000, "\"%s\" is not a Maintenance Window" // *Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of // the MAINTENANCE_WINDOW_GROUP. // *Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call. / 15649, 00000, "Last message reserved for Automated Maintenance Tasks (KET)." // *Document: NO // *Cause: // *Action: // / / / 15650 - 15699 reserved for Direct Access to Fixed Tables / 15650, 00000, "invalid DIRECT_ACCESS command" // *Document: NO // *Cause: // *Action: / 15651, 00000, "invalid option \"%s\" for \"%s\" in DIRECT_ACCESS command" // *Document: NO // *Cause: // *Action: / 15652, 00000, "Fixed table \"%s\" does not exist." // *Document: NO // *Cause: // *Action: / 15653, 00000, "Fixed table \"%s\" is not supported by DIRECT_ACCESS." // *Document: NO // *Cause: // *Action: / 15654, 00000, "No more than %s columns can be specified in a DIRECT_ACCESS SELECT query." // *Document: NO // *Cause: // *Action: / 15655, 00000, "Fixed table \"%s\" cannot be accessed safely in prelim connection." // *Document: NO // *Cause: // *Action: Run ORADEBUG DIRECT_ACCESS SET MODE=UNSAFE and query again. / 15656, 00000, "DIRECT_ACCESS statement is too long." // *Document: NO // *Cause: // *Action: / 15657, 00000, "Column \"%s\" does not have a fixed index defined." // *Document: NO // *Cause: // *Action: / 15658, 00000, "Type is not supported type for DIRECT_ACCESS filters." // *Document: NO // *Cause: // *Action: / 15659, 00000, "Multi-column indexes not supported for DIRECT_ACCESS filters." // *Document: NO // *Cause: // *Action: / 15699, 00000, "last message reserved for DIRECT_ACCESS" // *Document: NO // *Cause: // *Action: // / / / 15700-15749 Reserved for SQL Tuning Advisor, SQL Tuning Set and SQL / Performance Analyzer (STA/STS/SPA). We have reserved the / last ten error codes for SPA. / 15700, 00000, "SQL limit already reached by prior task execution" // *Cause: An attempt was made to resume the execution of a task when // the prior execution already reached the SQL limit. // *Action: Task execution is complete. Examine the report to review // Advisor's recommendations. / 15701, 00000, "All \"SQL Tuning Set(s)\" with name like \"%s\" and owner like \"%s\" are empty" // *Cause: An attempt was made to pack one or more SQL Tuning Sets, none // * of which contained any statements. // *Action: Check the input and try again. / 15702, 00000, "duplicate values for plan line ID in input collection" // *Cause: An invalid input was provided containing duplicate values for // plan line IDs causing the load of the statement to fail. // *Action: Check the input and try again. / 15703, 00000, "invalid version number \"%d\" for SQL tuning set staging table" // *Cause: An invalid version number was provided for a staging table used // to pack a SQL tuning set. // *Action: Check the input and try again. / 15739, 00000, "invalid name \"%s\" for SQL Performance Analyzer task" // *Cause: An invalid SQL Performance Analyzer task name was used. // *Action: Check the name of the SQL Performance Analyzer task to ensure // that it is correct. / 15740, 00000, "parameter \"%s\" not set for SQL Performance Analyzer task \"%s\"" // *Cause: Could not find the specified parameter name for the SQL Performance Analyzer task. // *Action: Check that the specified parameter exists for the SQL Performance // Analyzer task so that the parameter is set. / 15741, 00000, "no COMPARE_PERFORMANCE execution exists for SQL Performance Analyzer task \"%s\"" // *Cause: Could not find an execution of type COMPARE_PERFORMANCE for // specified SQL Performance Analyzer task. // *Action: Ensure that the given SQL Performance Analyzer task has at least one // execution of type COMPARE_PERFORMANCE. / 15742, 00000, "specified execution name \"%s\" is not a valid COMPARE_PERFORMANCE execution for SQL Performance Analyzer task \"%s\"." // *Cause: The specified execution name was not a valid execution of type // COMPARE_PERFORMANCE for the SQL Performance Analyzer task. // *Action: Ensure that a valid COMPARE_PERFORMANCE execution name is used for // the SQL Performance Analyzer task. / 15743, 00000, "need to specify the object ID if the tuning task is on a SQL set." // *Cause: There could be multiple objects in the SQL tuning task. Specify which one. // *Action: Add object ID to the interface. / 15744, 00000, "The directory name is null." // *Cause: The directory name for finding the SQL traces was null. // *Action: Create the directory. / 15745, 00000, "The plan type is not valid." // *Cause: The specified plan type was not valid // *Action: Check the existing plan types and specify the right one. / 15746, 00000, "Missing EXECUTE privilege on DBMS_AUTO_SQLTUNE." // *Cause: The current user was missing the necessary privileges to execute // the API. // *Action: Grant the privilege and try again. / 15749, 00000, "last message reserved for SQL tuning" // *Document: NO // *Cause: // *Action: // / /============================================================================== / 16000 - 16499 Reserved for ORACLE HOT STANDBY / / Begin messages for ORACLE Managed (aka Hot aka Automated) Standby /============================================================================== / 16000, 00000, "database open for read-only access" // *Cause: The database was opened for read-only access. Attempts to // modify the database using DML or DDL statements generate this // error. // *Action: In order to modify the database, it must first be shut down and // reopened 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 shut down and reopened 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 shut down and reopened for read/write access. 16003, 00000, "standby database is restricted to read-only access" // *Cause: An attempt was made to open a physical standby database in // read/write mode. // *Action: Reissue the ALTER DATABASE OPEN specifying READ ONLY. // 16004, 00000, "backup database required recovery" // *Cause: The database could not be opened for read-only access by this // instance because it requires recovery. // *Action: Perform the necessary recovery and reopen 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 reopen for read-only access. // 16006, 00000, "unused" // *Document: NO // *Cause: unused // *Action: unused // 16007, 00000, "invalid backup control file checkpoint" // *Cause: The database could not be opened for read-only access because its // control file did not contain a valid control file checkpoint. // *Action: Open the database for read/write access to create a valid control // file checkpoint. The database can then be opened for read-only // access. 16008, 00000, "indeterminate control file checkpoint" // *Cause: The control file for the database being opened for read-only access // was created using the CREATE CONTROLFILE statement. Therefore, a // control file checkpoint could not be calculated and the database // could not be opened for read-only access. // *Action: First, open the database for read/write access. This creates // a valid control file checkpoint. Then, reopen the database for // read-only access. 16009, 00000, "invalid redo transport destination" // *Cause: The redo transport destination could not accept redo data because // it was not a valid redo transport destination type. // *Action: Verify that all redo transport destinations are either standby // databases or downstream capture databases. 16010, 00000, "disable stale RFS process extermination" // *Document: NO // *Cause: Disables the termination of RFS processes waiting for // tcp_keepalive_interval to expire. // *Action: No action is required. 16011, 00000, "Remote File Server process is in Error state." // *Cause: The Remote File Server (RFS) process at the specified redo // transport destination experienced an unrecoverable error and // was unable to receive further redo data. // *Action: Correct the problem at the redo transport destination. 16012, 00000, "database identifier mismatch" // *Cause: The database identifier of a physical standby database did not // match that of the primary database. // *Action: Ensure that the database identifier of each physical standby // database matches that of the primary database. 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 archival failed because there were no archive log // destinations specified, or all destinations are in an error state. // *Action: Verify that archive log destinations are specified or // take the necessary step to correct any errors that may have // occurred. 16015, 00000, "Log %s sequence# %s was not archived." // *Cause: An attempt was made to archive the named log to a destination, but // the operation did not succeed because the destination was not in // ARCHIVELOG mode. // *Action: Enable ARCHIVELOG mode at all destinations and retry. 16016, 00000, "archived log for thread %s sequence# %s unavailable" // *Cause: Redo apply timed out waiting for the requested archived log // file. // *Action: Verify that the primary database is still archiving redo data to // the standby database and reissue the RECOVER STANDBY DATABASE // 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 or DB_RECOVERY_FILE_DEST" // *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...31) 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. // 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt // was made to use an ALTER SYSTEM or ALTER SESSION command to // define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST. // *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...31) or // DB_RECOVERY_FILE_DEST 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 or DB_RECOVERY_FILE_DEST 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, "fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST" // *Cause: The number of archive log destinations that could be used was less // than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value. // *Action: Either adjust 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...31) 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 indicated LOG_ARCHIVE_DEST_n (n = 1...31) // parameter could not be parsed. Common causes for this error are a // misplaced equal sign, an unrecognized attribute, or an attribute // that is missing a required value. // *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. 16025, 00000, "parameter %s contains repeated or conflicting attributes" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31) // parameter contained either repeated attributes or attributes that // conflicted with each other. // *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. 16026, 00000, "parameter %s contains an invalid attribute value" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31) // parameter contained an attribute with an invalid value. // *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. 16027, 00000, "parameter %s is missing a destination option" // *Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...31) // parameter failed to include a destination option. A destination // option is specified using either the LOCATION or SERVICE attrbute. // *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. 16028, 00000, "new %s causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires" // *Cause: An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or // LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...31) 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...31). Then, change the value of parameter // LOG_ARCHIVE_MIN_SUCCEED_DEST. 16030, 00000, "session specific change to the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter 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...31) 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, "Recovery could not be started." // *Cause: Database recovery could not be started because the FROM and MANAGED // STANDBY DATABASE clauses were both specifed when attempting to // start recovery. // *Action: Retry the command with either the FROM or MANAGED STANDBY DATABASE // clause, but not both. 16035, 00000, "missing required keyword %s" // *Cause: The indicated keyword is required but was not specified. // *Action: Correct the syntax and retry the command. 16036, 00000, "invalid CANCEL option" // *Cause: A mode other than IMMEDIATE followed 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 redo transport destination // failed because of an Oracle software version mismatch at the // destination. // *Action: Verify that a compatible version of Oracle software is running at // the redo transport destination. 16040, 00000, "Destination archive log file is locked." // *Cause: The target archive log file was locked. This indicates that the // file is being archived to another Remote File Server (RFS) process. // *Action: Ensure that each remote redo transport destination uses a unique // network service name. 16041, 00000, "Remote File Server fatal error" // *Cause: The Remote File Server (RFS) process at a redo transport // destination encountered a fatal error and was no longer // available. Further redo transmission to this destination may not be // possible. // *Action: Refer to the appropriate RFS trace file located at the redo // transport destination for details regarding the error encountered // and take corrective action. 16042, 00000, "user requested cancel immediate of redo apply" // *Cause: Redo apply was canceled immediately per user request. Processing of // the current archive log file has been interrupted and, therefore, // the database is in an inconsistent state. // *Action: No action is required. 16043, 00000, "Redo apply has been canceled." // *Cause: Redo apply was 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 attempt was made to modify a redo transport destination // attribute using the ALTER SESSION command. // *Action: Use the ALTER SYSTEM command to modify the destination attribute. 16045, 00000, "circular redo transport destination dependency chain" // *Cause: An attempt was made to make a redo transport destination dependent // on a redo transport destination that was dependent on it. // *Action: Ensure that no redo transport destination is dependent on any // destination that is dependent on it. 16046, 00000, "Redo transport destination failed due to failed dependent destination." // *Cause: The redo transport destination was dependent upon another // destination, which failed. Therefore, this destination failed. // *Action: No action required. 16047, 00000, "DGID mismatch between destination setting and target database" // *Cause: The DB_UNIQUE_NAME specified for the destination did not match // the DB_UNIQUE_NAME at the target database. // *Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n // parameter matches the DB_UNIQUE_NAME parameter defined at the // destination. 16048, 00000, "enable simulated error on archive log write" // *Document: NO // *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 archive log write" // *Document: NO // *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 archive log was attempted to be created in a destination with // a specified maximum quota size. The creation of the archive log // 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...31) // parameter contained a DELAY attribute with an invalid numeric // value. The valid range is 0-5760 (in minutes). // *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. 16052, 00000, "DB_UNIQUE_NAME attribute is required." // *Cause: DB_UNIQUE_NAME attribute was not specified. The value of the // LOG_ARCHIVE_DEST_n parameter for each remote redo transport // destination must contain the DB_UNIQUE_NAME attribute if the // LOG_ARCHIVE_CONFIG parameter value contains the DG_CONFIG // attribute. // *Action: Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME for // the destination. 16053, 00000, "DB_UNIQUE_NAME %s is not in the Data Guard Configuration" // *Cause: The specified DB_UNIQUE_NAME is not in the Data Guard // Configuration. // *Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter // is enabled, you must specify a valid DB_UNIQUE_NAME. The list // of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG // view. This problem can also occur when specifying a non-standby // destination with an DB_UNIQUE_NAME attribute that does not match // the DB_UNIQUE_NAME initialization parameter for the current // instance. 16054, 0000, "Event for automatic RFS gap sequence detection" // *Document: NO // *Cause: This is an 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 an Oracle internal event code. 16055, 0000, "FAL request rejected" // *Cause: Fetch archive log (FAL) server rejected a redo gap fetch request // from the client. This may have various causes. // *Action: Check the alert log on the primary database. Take the appropriate // action to solve the problem. 16056, 00000, "Backup control file archival requires proper syntax." // *Cause: An attempt was made to perform an online log file archival using // a backup control file. However, the USING BACKUP CONTROLFILE syntax // was not specified. // *Action: Use the USING BACKUP CONTROLFILE clause to perform an online log // file archival using a backup control file. 16057, 00000, "server not in Data Guard configuration" // *Cause: The primary database or fetch archive log (FAL) server was not // found in the Data Guard configuration of the standby database. // *Action: Add the database unique name of the primary database or FAL server // to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database // initialization parameter. 16058, 00000, "standby database instance is not mounted" // *Cause: The Remote File Server (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, "empty log file or invalid next available block" // *Cause: An attempt was made to archive an empty or invalid log file. // *Action: No action is required. 16060, 00000, "Log file is current." // *Cause: An attempt was made to archive current log file. // *Action: No action is required. 16061, 00000, "Log file status has changed." // *Cause: The online log file was reclaimed as a new log file either before // archival started or during the archival operation. // *Action: No action is required. 16062, 00000, "standby database not in Data Guard configuration" // *Cause: The standby database was not found in the Data Guard configuration // of the server. // *Action: Add the database unique name of the standby database to the // DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database // initialization parameter. 16063, 00000, "unused" // *Document: NO // *Cause: unused // *Action: unused 16064, 00000, "unused" // *Document: NO // *Cause: unused // *Action: unused 16065, 00000, "remote archival disabled at standby destination" // *Cause: Receipt of remote archived REDO log files has been disabled // at the associated standby destination host database. // *Action: If appropriate change the associated archive log parameter to // specify a local destination with the LOCATION keyword or defer // the associated archive log destination. Or, if possible, set the // standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the // RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart // the standby database instance before further REDO log file // archivals occur. 16066, 00000, "remote archival disabled" // *Cause: An archive log destination parameter has specified a remote // destination with the SERVICE keyword. Remote archival of REDO // log files has been disabled for this database. The associated // archive log destination has been disabled. // *Action: If appropriate change the archive log parameter to specify a // local destination with the LOCATION keyword or (if appropriate) // set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the // SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart // the database instance before further REDO log file 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 cannot 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, "activation identifier mismatch" // *Cause: Redo transport failed because the activation identifier of the // primary and physical standby databases did not match. This can // happen if the physical standby database was not created from a // backup of the primary database. // *Action: Create a valid configuration and re-try the failed operation. 16070, 00000, "parameter %s contains an invalid REGISTER attribute value" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31) // parameter contained a REGISTER attribute that specified an // invalid file name template string. If specified, the REGISTER // file name template string must indicate an O/S-specific file // path name 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, "Archived log file %s was not found at dependency destination." // *Cause: The specified archived log file was not found at a redo tranpsort // destination on which other destinations are dependent. // *Action: Verify that all redo transport destinations that are dependent upon // another destination or upon which other destinations are dependent // are configured correctly. 16072, 00000, "a minimum of one standby database destination is required" // *Cause: No standby database archive log destinations were specified. // *Action: Specify a standby archive log destination in the initialization // parameter file. 16073, 00000, "archiving must be enabled" // *Cause: Online log file archiving is disabled. // *Action: Enable log file archiving. 16074, 00000, "No ARCH processes are active." // *Cause: All ARCH processes have stopped. // *Action: Restart the instance. 16075, 00000, "standby database destination mismatch" // *Cause: Another instance had access to a standby database destination // that this instance did not. If the initialization parameter // LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this // may be due to a standby database becoming unavailable recently. // *Action: Ensure that at each instance the set of standby databases referred // to by LOG_ARCHIVE_DEST_n initialization parameters is the same // and define a DG_CONFIG at each instance to identify those databases // explicitly. 16076, 00000, "unknown standby database destination" // *Cause: A standby database destination was specified that was not accessed // by another instance. If the initialization parameter // LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this mismatch // may be due to a standby database having been restarted recently. // *Action: Ensure that at each instance the set of standby databases referred // to by LOG_ARCHIVE_DEST_n initialization parameters is the same // and define a DG_CONFIG at each instance to identify those databases // explicitly. 16077, 00000, "simulate network transmission error" // *Document: NO // *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 did not have archival enabled. // *Action: In order to allow the standby database to access the standby // log files, the standby database must be in ARCHIVELOG mode. 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 // or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS // view. 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: Shut down the previous apply engine before starting a new one. 16085, 00000, "apply engine related event" // *Document: NO // *Cause: // *Action: 16086, 0000, "Redo data cannot be written to the standby redo log" // *Cause: The primary database was in MAXIMUM PROTECTION or MAXIMUM // AVAILABILITY mode, but redo data could not be written to the // standby redo log at the standby database(s). // *Action: Check the Remote File Server (RFS) trace file for specific errors // and reconfigure the standby redo log as appropriate. 16087, 0000, "Switchover requires standby or current control file." // *Cause: An attempt was made to perform a switchover operation using a // backup or clone control file. // *Action: Convert the backup control file into a current control file prior // to attempting a switchover operation. A clone control file cannot // be used for a switchover operation. 16088, 0000, "archive log has not been completely archived" // *Cause: An attempt was made to register an archive log that has not been // completely archived. The specified archive log may be a "current" // log file. // *Action: Specify a completed archive log. 16089, 0000, "archive log has already been registered" // *Cause: An attempt was made to register an archive log that already has // a corresponding thread# and sequence# entry in the standby database // control file. Duplicate information is not permitted. // *Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log // information. 16090, 0000, "archive log to be replaced not created by managed standby process" // *Cause: An attempt was made to replace an archive log entry that was not // originally created by the managed standby operation. // *Action: No user action required. 16091, 00000, "dependent archive log destination already archived" // *Cause: An archive log destination contains a dependency to another // archive log destination that has previously been archived. // *Action: The parent archive log destination cannot be dependent on another // archive log destination. Use the ALTER SYSTEM command to remove // one of the dependency attributes. 16092, 00000, "dependent archive log destination is not active" // *Cause: An archive log destination contains a dependency to another // archive log destination that is not active" // *Action: The child archive log destination cannot be dependent on another // invalid archive log destination. Use the ALTER SYSTEM command to // remove one of the dependency attributes. 16093, 00000, "dependent archive log destination is not LGWR-enabled" // *Cause: An archive log destination contains a dependency to another // archive log destination that is not enabled for the LGWR process" // *Action: The child archive log destination cannot be dependent on another // archive log destination not archived by the LGWR. Use the // ALTER SYSTEM command to change the parent archive log to specify // the LGWR process. 16094, 00000, "Database shut down during archival operation." // *Cause: The database was shut down while an online log file archival was // active. // *Action: None required. 16095, 00000, "Dependent destination removal for inactivation" // *Cause: A dependent archive log destination was inactivated due to the // parent archive log 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 COMMIT TO SWITCHOVER TO PHYSICAL STANDBY" // *Cause: None // *Action: Specify this command to switch the primary database to the physical // standby role. 16097, 00000, "ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY" // *Cause: None // *Action: Specify this command to switch the physical standby database to the // primary role. 16098, 00000, "Primary database has been shut down to prevent data loss." // *Cause: The primary database was shut down because it was operating // in maximum protection mode and no suitable standby databases // were available to protect the primary database from data loss. // *Action: Diagnose and correct whatever errors exist in the configuration // or configure the primary database for maximum availability or // maximum performance mode. 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 - 16130 Reserved for Logical Standby / 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 has not completed generating the necessary // information for the standby to begin consuming its 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 parameter" // *Cause: The specified parameter is not valid. // *Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package // documentation for the correct statement syntax. 16105, 00000, "Logical Standby is already running in background" // *Cause: A Logical Standby apply operation is already running. // *Action: none 16106, 0000, "loading previously applied transaction information" // *Cause: Logical Standby coordinator was performing a scan to identify // previously applied transactions. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. 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 COMMIT 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 COMMIT 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 COMMIT 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, reissue 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 %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, "%s\% of LogMiner dictionary loading is done" // *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, "processing" // *Cause: The process is performing its primary function and is not // waiting on any significant event. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16118, 00000, "enable RFS wait event threshold identification" // *Document: NO // *Cause: Specifies the maximum time, in hundreths of seconds, that an RFS // operation can take. Any RFS operation that exceeds this threshold // logs a message with the operation duration to the RFS trace file. // The value "100" is "1" second. // *Action: No action is required. 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, "dependencies being computed for transaction at SCN %s" // *Cause: The transaction committed at the given SCN is being // analyzed for dependencies. // *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. 16123, 00000, "transaction %s %s %s is waiting for commit approval" // *Cause: The apply process is waiting for approval to commit a // transaction. This transaction may depend on another or other // synchronization activity may delay the committing of a transaction. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16124, 00000, "transaction %s %s %s is waiting on another transaction" // *Cause: The apply process is waiting to apply additional changes. // This transaction likely depends on another. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16125, 00000, "large transaction %s %s %s is waiting for more data" // *Cause: The apply process is waiting until additional changes for a // large transaction are retrieved from the log stream. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16126, 00000, "loading table or sequence %s" // *Cause: Information on the given table or sequence is being loaded // into an in memory cache for future use. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16127, 00000, "stalled waiting for additional transactions to be applied" // *Cause: This process is waiting for additional memory before continuing. // Additional log information cannot be read into memory until more // transactions have been applied to the database, thus freeing up // additional memory. // *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. 16128, 00000, "User initiated stop apply successfully completed" // *Cause: Logical standby was shutdown in an orderly fashion. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16129, 00000, "unsupported DML encountered" // *Cause: One or more DMLs to an unsupported table were encountered // and skipped. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. // Optionally, check the DBA_LOGSTDBY_EVENTS view for more // information including the impacted table owner and name. 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, "Invalid LOG_ARCHIVE_CONFIG modification while in protected mode" // *Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any // RAC instance is open in either maximum protection or maximum // availability mode. Also, the parameter can not be modified in such // way that would cause all destinations to fail while in maximum // protection mode. // *Action: Make the modification before the database is opened by any // instance. 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. 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: An error has occurred while performing a switchover. // *Action: If you were switching a primary database to the standby role, the // conversion was successful, but one or more errors occurred after // the conversion completed. See the alert log for more information. // You can proceed with switching the target standby database to the // primary role, but you must address the errors reported at the old // primary database before it can protect the new primary database. // // If you encountered this error while switching a physical standby // database to the primary role, the switchover did not succeed // because additional redo must be applied. Verify that redo apply is // active and wait until the SWITCHOVER_STATUS column of the // V$DATABASE dynamic performance view reports TO_PRIMARY or // SESSIONS_ACTIVE before retrying the switchover. 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 // reissue 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 archive log error" // *Document: NO // *Cause: Causes an error to be signalled during the archival operation. // *Action: No action is required. 16142, 00000, "simulated archive log error" // *Document: NO // *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: An attempt was made, by an RFS process, to access a standby online // log file 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" // *Document: NO // *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, "%scontrol file enqueue unavailable" // *Cause: The control file enqueue is currently unavailable. // *Action: No Action is required. We will try to re-fetch it at a later time. 16147, 00000, "standby database referenced by multiple archive log destinations" // *Cause: Multiple archive log destinations reference the same standby // database, using different service names. This is not allowed. // *Action: Remove one of the duplicate archive log 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" // *Document: NO // *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 archive log containing a FINISH recovery indicator was received // by a standby database that has received archive logs in the future // of the received archive log. Because of the possibility that these // future archive logs have been applied to this standby database, // the received archive log must be rejected. // *Action: No action is required. 16151, 00000, "Managed Standby Recovery not available" // *Cause: The attempted operation failed because of a pending CANCEL of the // managed standby recovery operation. // *Action: Wait for the managed standby recovery session to end. Then retry // the operation. 16152, 00000, "standby database is in 'no-data-loss' protected mode" // *Cause: The attempted database operation is not allowed while the // standby database is in 'no-data-loss' protected mode. // *Action: Verify that the attempted database operation is warranted, // ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue // the statement. 16153, 00000, "enable ARCH Physical RFS client debugging" // *Document: NO // *Cause: Enables the ARCH physical RFS client callback. // *Action: No action is required. 16154, 00000, "suspect attribute: %s" // *Cause: Use of the indicated attribute is illegal in the given context. // *Action: Make the appropriate changes and reissue the statement. 16155, 00000, "enable arch procs to not exceed log_archive_max_processes" // *Document: NO // *Cause: disallow arch processes to exceed log_archive_max_processes // in releases prior to 9i. Note that in 9i and subsequent // releases this event is not required. We reserve this event for 9i // and subsequent releases to allow us to backport the new // log_arch_max_processes behavior for earlier releases. // *Action: No action is required. 16156, 00000, "LGWR archive log dependency not allowed if database is standby protected" // *Cause: The use of a LGWR archive log dependency is not allowed when the // primary is protected by a standby database, as this requires use // of the standby redo log files. // *Action: Remove the LGWR archive log dependency and use normal LGWR archival // instead. 16157, 00000, "media recovery not allowed following successful FINISH recovery" // *Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously // completed successfully. Another media recovery is not allowed. // *Action: Issue one of these operations following a FINISH recocvery: // ALTER DATABASE OPEN READ ONLY or // ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY. 16158, 00000, "simulated failure during terminal recovery" // *Document: NO // *Cause: Causes an error to be signalled during terminal recovery. // *Action: No action is required. 16159, 00000, "Cannot change protected standby destination attributes" // *Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes // for a destination that is participating in the standby protection // mode of the database. // *Action: No action is required. 16160, 00000, "Cannot change protected standby database configuration" // *Cause: An attempt was made to change the standby database configuration // when the primary database is in standby protected mode. // *Action: The standby database must be added to the configuration before // the primary database is opened. 16161, 00000, "Cannot mix standby and online redo log file members for group %s" // *Cause: An attempt was made to add a log file member that did not match // the other member types. This problem typically occurs when adding // a standby log file member to an online redo log file group, or adding // an online redo log file member to a standby redo log file group. // *Action: Verify the log file group type using the TYPE column of the V$LOG // fixed view. 16162, 00000, "Cannot add new standby databases to protected configuration" // *Cause: An attempt was made to enable a new standby database destination // when the primary database is in standby protected mode. // *Action: The standby database must be added to the configuration before // the primary database is opened. 16163, 00000, "LGWR network server host attach error" // *Cause: The LGWR network server could not attach to remote host // *Action: The alert log contains more problem-specific information 16164, 00000, "LGWR network server host detach error" // *Cause: The LGWR network server could not detach from remote host // *Action: The alert log contains more problem-specific information 16165, 00000, "LGWR failed to hear from network server" // *Cause: The LGWR lost its connection to the network server // *Action: The alert log contains more problem-specific information 16166, 00000, "LGWR network server failed to send remote message" // *Cause: The LGWR network server could not communicate with the remote host // *Action: The alert log contains more problem-specific information 16167, 00000, "LGWR network server could not switch to non-blocking mode" // *Cause: The LGWR network server could not switch to non-blocking mode // *Action: The alert log contains more problem-specific information 16168, 00000, "LGWR network server could not switch to blocking mode" // *Cause: The LGWR network server could not switch to blocking mode // *Action: The alert log contains more problem-specific information 16169, 00000, "LGWR network server invalid parameters" // *Cause: The LGWR network server could not switch to blocking mode // *Action: The alert log contains more problem-specific information 16170, 00000, "Terminal recovery may have left the database in an inconsistent state" // *Cause: When terminal recovery is invoked in a standby database // without synchronous log shipping, in the rare case of the // recovery session being in an unrecoverable state, terminal // recovery cannot bring the standby database to a consistent // SCN boundary if the primary database continues to have redo // thread(s) open. // *Action: Continue standby recovery with additional log shipping from // primary. 16171, 00000, "RECOVER...FINISH not allowed due to gap for thr %s, seq %s-%s" // *Cause: See alert log for more details // *Action: Copy missing archived logs from primary or another standby. // Register the logs and reissue the RECOVER...FINISH command. // If the logs are not available, issue the ALTER DATABASE // RECOVER MANAGED STANDBY SKIP command to ignore the standby // redo log files. 16172, 00000, "archive logs detected beyond Terminal End-Of-Redo" // *Cause: An attempt to archive a Terminal End-Of-Redo archive log to a // remote destination failed due the existence, at the remote site, // of archive logs containing REDO in the future of the Terminal EOR. // *Action: 16173, 00000, "incompatible archival network connections active" // *Cause: One of two situations can cause this error: // 1) An attempt to start a Terminal Incomplete Recovery operation // failed due to an active Remote File Server process detected. // 2) An attempt to archive a Terminal End-Of-Redo archive log // to a remote destination failed due to an active Remote File Server // process at the remote site. // An active Remote File Server (RFS) process implies connectivity // with the primary database which may indicate that a Terminal // Incomplete Recovery operation is not warrented. // *Action: Verify the Managed Standby environment and re-evaluate the // necessity of a Terminal Incomplete Recovery operation. 16174, 00000, "user requested thread/sequence termination of managed recovery" // *Cause: The managed standby database recovery operation has been // terminated per user specified THROUGH THREAD/SEQUENCE option of // the RECOVER MANAGED STANDBY DATABASE statement. // *Action: No action is required. 16175, 00000, "cannot shut down database when media recovery is active" // *Cause: An attempt was made to shut down a standby database while media // recovery was active. // *Action: Cancel media recovery to proceed with the shutdown. 16176, 00000, "background dictionary build cannot be running" // *Cause: The background process dedicated to dictionary build is active. // *Action: wait and try it later. 16177, 00000, "media recovery is not required" // *Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER // MANAGED STANDBY DATABASE was specified and the database has been // recovered to the most recent End-Of-Redo marker. All known archived // logs have been applied. Managed 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. 16178, 00000, "Cannot specify remote destinations in manual archiving mode" // *Cause: The database is operating in manual archiving mode. // Remote archivelog destinations are not allowed in this mode. // *Action: Use the ALTER DATABASE ARCHIVELOG command to place the database // in automatic ARCHIVELOG mode, or defer the archivelog destinations // that specify the SERVICE= attribute. 16179, 00000, "incremental changes to \"%s\" not allowed with SPFILE" // *Cause: Incremental changes to a log_archive_dest_n parameter cannot // be made when using an SPFILE. // *Action: Specify either LOCATION or SERVICE plus all other attributes // to be set in one ALTER SYSTEM/SESSION SET command. 16180, 00000, "number of processes specified is too large" // *Cause: The number of server processes available for Logical Standby is // currently limited to 1024 LogMiner processes and 1024 apply // processes or a total of 2048. // *Action: Retry with a lower value. / 16181, 00000, "SGA specified for Logical Standby is too large" // *Cause: MAX_SGA is larger than 75% of the larger of initialization // parameters SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET. // *Action: Specify the value of MAX_SGA to be less than 75% of the maximum of // SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET. 16182, 00000, "Internal error on internal channel during remote archival" // *Cause: An internal error was encountered on the internal channel between // LGWR and Network Server. // *Action: No action is required, as an attempt will be made to re-archive the // file that had this failure during archival. 16183, 00000, "Internal event for testing purposes" // *Document: NO // *Cause: This is an internal event used for testing purposes // *Action: No action is necessary. 16184, 00000, "DB_UNIQUE_NAME %s hashes to the same value as DB_UNIQUE_NAME %s" // *Cause: The internal hash value generated for one DB_UNIQUE_NAME collided // with the hash value of another DB_UNIQUE_NAME. // *Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a // different value. 16185, 00000, "REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive" // *Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters // are defined in the initialization file and they are mutually // exclusive. // *Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use // only the LOG_ARCHIVE_CONFIG parameter. 16186, 00000, "Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier" // *Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly // the same on all RAC instances so the SID='*' qualifier is required. // *Action: Re-enter the command using the SID='*' qualifier. 16187, 00000, "LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes" // *Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, // conflicting or invalid attributes. // *Action: Check the documentation regarding the correct specification of the // LOG_ARCHIVE_CONFIG parameter. 16188, 00000, "LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance" // *Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent // with the settings of a previously started instance. The settings // for this parameter must be exactly the same for all instances. // *Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG // settings. 16189, 00000, "Internal event for testing RTA purposes" // *Document: NO // *Cause: This is an internal event used for testing purposes // *Action: No action is necessary. 16190, 00000, "Internal event for RFS Auth testing purposes" // *Document: NO // *Cause: This is an internal event used for testing purposes // *Action: No action is necessary. 16191, 0000, "Primary log shipping client not logged on standby" // *Cause: An attempt to ship redo to standby without logging on // to standby or with invalid user credentials. // *Action: Check that primary and standby are using password files and that // both primary and standby have the same SYS password. // Restart primary and/or standby after ensuring that // password file is accessible and REMOTE_LOGIN_PASSWORDFILE // initialization parameter is set to SHARED or EXCLUSIVE. / 16192, 0000, "Primary and standby network integrity mismatch" // *Cause: Standby wants sqlnet network integrity for redo shipment // which is not configured properly at the primary. // *Action: Check sqlnet.ora documentation regarding how to setup // network integrity and set it up identically on both // primary and standby. Restart primary and/or standby. / 16193, 0000, "Primary and standby network encryption mismatch" // *Cause: Standby wants sqlnet network encryption for redo shipment // which is not configured properly at the primary. // *Action: Check sqlnet.ora documentation regarding how to setup // network encryption and set it up identically on both // primary and standby. Restart primary and/or standby. / 16194, 00000, "Modifying DB_UNIQUE_NAME requires SID='*' qualifier" // *Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the // same on all RAC instances so the SID='*' qualifier is required. // *Action: Re-enter the command using the SID='*' qualifier. 16195, 00000, "DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined" // *Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can // only be used if the DB_UNIQUE_NAME parameter has been explicitly // defined. // *Action: Explicitly define a valid DB_UNIQUE_NAME. 16196, 00000, "database has been previously opened and closed" // *Cause: The instance has already opened and closed the database, // which is allowed only once in its lifetime. // *Action: Shut down the instance. 16197, 00000, "Invalid DB_UNIQUE_NAME parameter specification" // *Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The // DB_UNIQUE_NAME parameter has a maximum length of 30 characters // and the only characters allowed are alpha-numeric characters and // "_", "$" and "#". // *Action: Check the documentation and re-enter the parameter. 16198, 00000, "Timeout incurred on internal channel during remote archival" // *Cause: A timeout was incurred during remote archival. // *Action: No action is required, as an attempt will be made to re-archive the // file that had this failure during archival. 16199, 00000, "Terminal recovery failed to recover to a consistent point" // *Cause: See alert log for more details // *Action: Try to resolve the problem. Retry terminal recovery. // If the problem occurs repeatedly and cannot be resolved, // call Oracle support. / / 16200 - 16399 Reserved for Logical Standby / 16200, 00000, "Skip procedure requested to skip statement" // *Cause: Logical standby called a skip procedure that requested for // a particular statement not to be applied. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16201, 00000, "Skip procedure requested to apply statement" // *Cause: Logical standby called a skip procedure that requested for // a particular statement to be applied. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16202, 00000, "Skip procedure requested to replace statement" // *Cause: Logical standby called a skip procedure that requested for // a particular statement to be replaced with a new statement. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16203, 00000, "Unable to interpret skip procedure return values" // *Cause: The skip procedure returned conflicting or invalid values. // *Action: Ensure that the new_statement output parameter is non-NULL when // returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. // Also ensure SKIP_ACTION is specified correctly. / 16204, 00000, "DDL successfully applied" // *Cause: A DDL statement has successfully commited on the logical // standby database. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16205, 00000, "DDL skipped due to skip setting" // *Cause: A setting in the logical standby skip table indicates // that this type of DDL should always be skipped. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16206, 00000, "database already configured as Logical Standby database" // *Cause: This database has been previously configured as a Logical Standby // database. A Logical Standby database is not capable of processing // the requested operation. // *Action: Ensure that you entered the command on the correct database as // this database is a Logical Standby and is not capable of // servicing the request. / 16207, 00000, "Logical standby dictionary build not permitted." // *Cause: A dictionary build is currently in progress. Only one build can be // active at a time. // *Action: Wait for the active build to complete before invoking a new build. / 16208, 00000, "Logical standby dictionary build failed to start." // *Cause: Failure to start the logical standby dictionary build process (LSP1) // *Action: Check the accompanying messages, and the background process trace // file. Correct the problem mentioned in the messages. Then shut down // and restart the instance. If the trace file mentions any other // background process messages, check the trace file for the mentioned // process until the root message is found. / 16209, 00000, "Logical standby dictionary build failed to complete." // *Cause: The logical standby dictionary build process terminated abnormally. // *Action: Check the accompanying messages, and the background process trace // file. Correct the problem mentioned in the messages. Then shut down // and restart the instance. If the trace file mentions any other // background process messages, check the trace file for the mentioned // process until the root message is found. / 16210, 00000, "Logical standby coordinator process terminated with error" // *Cause: The logical standby coordinator process terminated abnormally. // *Action: Check the accompanying messages, and the background process trace // file. Correct the problem mentioned in the messages. Then shut // down and restart the instance. If the trace file mentions any other // background process messages, check the trace file for the mentioned // process until the root message is found. / 16211, 00000, "unsupported record found in the archived redo log" // *Cause: Log apply services encountered a record in the archived redo log // that could not be interpreted. // *Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table // on the standby database or simply drop the table if // it's unimportant. // 2. ALTER DATABASE START LOGICAL STANDBY APPLY; // 3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view // to determine which log file contains the unsupported record. // 4. Provide the log file to Oracle Support Services. / 16212, 00000, "number of processes specified for SQL Apply is too great" // *Cause: Logical standby apply engine was started with more processes // requested than are available. // *Action: Adjust the values of the initialization parameters PROCESSES // or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS // view. If you did not specify MAX_SERVERS, but instead specified // PREPARE_SERVERS and APPLY_SERVERS through the // dbms_logstdby.apply_set procedure, you will need to decrease either // one or both of them. / 16213, 00000, "ddl encountered, stopping apply engine" // *Cause: stop_on_ddl callout specified and DDL was encountered. // *Action: Either disable stop_on_ddl callout or remove DDL. / 16214, 00000, "apply stalled for apply delay" // *Cause: A delay has been specified on the primary database for this // destination. // *Action: Either turn off the delay on the primary or use // DBMS_LOGSTDBY.APPLY_UNSET('APPLY_DELAY'); to override. / 16215, 00000, "history metadata inconsistency" // *Cause: internal error. // *Action: This is an internal error. Contact Oracle support. / 16216, 00000, "Log stream sequence error" // *Cause: The log stream being processed did not follow the last // processed stream. // *Action: If the database is in an active configuration, issue an // ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command // to synchronize log stream data with the current primary database. // If the database is not in an active configuration, manually add // the next dictionary-begin log file that followed the previous // log stream. / 16217, 00000, "prepare to switchover has not completed" // *Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but // the prepare activity did not complete. // *Action: Verify that the standby was prepared properly. You may cancel // the prepare and perform an unprepared switchover which requires // a database link to complete. Or reissue the prepare operation // on the standby. / 16218, 00000, "This database is already preparing to switch over." // *Cause: The database was already preparing to switch over and was not // able to accomodate another prepare attempt. // *Action: Cancel the current prepare attempt with the ALTER DATABASE // PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare // request. / 16219, 00000, "This database is not preparing to switch over." // *Cause: The database was not preparing to switch over. Therefore, it was not // possible to cancel the SWITCHOVER command. // *Action: Preparing for the SWITCHOVER command can be accomplished with the // ALTER DATABASE PREPARE TO SWITCHOVER command. / 16220, 00000, "no failed transaction found" // *Cause: No failed transaction was found. // *Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command // without the SKIP FAILED TRANSACTION option. / 16221, 00000, "history table synchronization error" // *Cause: internal error. // *Action: This is an internal error. Contact Oracle support. / 16222, 00000, "automatic Logical Standby retry of last action" // *Cause: A failure occurred while running Logical Standby apply. // A new attempt is automatically being made by Logical Standby apply. // *Action: No action is necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16223, 00000, "DDL skipped, unsupported in current version" // *Cause: The given DDL statement was not supported in the current version of // Logical Standby and was skipped. // *Action: No action is necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16224, 00000, "Database Guard is enabled" // *Cause: Operation could not be performed because database guard is enabled // *Action: Verify operation is correct and disable database guard / 16225, 00000, "Missing LogMiner session name for Streams" // *Cause: An attempt was made to register the log file for Streams without // a specified LogMiner session name. // *Action: Specify a valid LogMiner session name to which the log file will // be registered. / 16226, 00000, "DDL skipped due to lack of support" // *Cause: Logical Standby does not support this type of DDL // in this version, so the DDL is skipped. // *Action: The DBA may apply the DDL explicitly at a later time or // a procedure to handle this type of DDL can be created. // see DBMS_LOGSTDBY.SKIP procedure for details. / 16227, 00000, "DDL skipped due to missing object" // *Cause: A table or other database object upon which this DDL depends // is not defined on the Logical Standby database. // *Action: No action is necessary, this infomational statement is provided // to record the event for diagnostic purposes. / 16228, 00000, "Insufficient recovery for logical standby" // *Cause: Insufficient amount of recovery was run for logical standby // instantiation. // *Action: Continue to recover the database using // ALTER DATABASE RECOVER MANAGED STANDBY DATABASE. / 16229, 00000, "PDML child %s %s %s for parent %s %s %s cannot be skipped." // *Cause: A request was made to skip a parallel DML child transaction id. // This is not supported. // *Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove // the child transaction id, then specify the parent transaction id // using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate. / 16230, 00000, "committing transaction %s %s %s" // *Cause: Logical Standby apply was committing changes for the given // transaction. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16232, 00000, "adding Logical Standby skip entry for table %s.%s" // *Cause: Table was previously unsupported due to datatype or storage // attribute definitions. Table is now capable of being supported. // *Action: To have Logical Standby maintain the table, import that table // directly from the primary. / 16233, 00000, "The table %s.%s is unsupported now" // *Cause: Table was previously supported but now is unsupported due to // altered datatype or storage attribute definitions. // *Action: None. / 16234, 00000, "restarting to reset Logical Standby apply" // *Cause: Logical Standby encountered a work load that required a restart // to properly reschedule. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16235, 00000, "DDL skipped because import has occurred" // *Cause: An object was exported from the primary database and imported // into the Logical Standby database. This DDL occurred before the // export. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16236, 00000, "Logical Standby metadata operation in progress" // *Cause: The requested operation failed because an incompatible // Logical Standby metadata operation such as // DBMS_LOGSTDBY.SET_TABLESPACE, DBMS_LOGSTDBY.APPLY_SET or // DBMS_LOGSTDBY.INSTANTIATE_TABLE was still running. // *Action: Wait for the incompatible Logical Standby metadata operation to // finish, then reenter or respecify the operation. / 16237, 00000, "SGA specified for Logical Standby is too small" // *Cause: MAX_SGA must be at least 10 Megabytes for proper functioning // of Logical Standby. // *Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. // Alternatively, increase the shared_pool_size/sga_target so that 1/4 // of it will amount to 10 Megabytes. / 16238, 00000, "attempt to use version 9 log" // *Cause: Version 9 log files are not supported. // *Action: Use log files of a supported version. / 16239, 00000, "IMMEDIATE option not available without standby redo logs" // *Cause: The IMMEDIATE option cannot be used without standby redo logs. // *Action: Do not specify the IMMEDIATE option unless standby redo logs are // being used. / 16240, 00000, "Waiting for log file (thread# %s, sequence# %s)" // *Cause: Process is idle waiting for additional log file to be available. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16241, 00000, "Waiting for gap log file (thread# %s, sequence# %s)" // *Cause: Reader process was idle waiting for the log file to fill the log // sequence gap. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16242, 00000, "Processing log file (thread# %s, sequence# %s)" // *Cause: Reader process was processing the log file. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16243, 00000, "paging out %s bytes of memory to disk" // *Cause: Builder process is paging out momery to free up space in lcr // cache. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16245, 00000, "change db_name to %s in the server-side parameter file (SPFILE)" // *Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname // command was successfully executed without a modifiable server // parameter file (SPFILE). // *Action: The server-side parameter file must be modified so that db_name // is set to the given name before mounting the database again. // You must do this by executing CREATE PFILE FROM SPFILE, editing the // resulting text parameter file, and then executing CREATE SPFILE // FROM PFILE. / 16246, 00000, "User initiated abort apply successfully completed" // *Cause: SQL Apply was stopped using the abort option. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16247, 00000, "DDL skipped on internal schema" // *Cause: Logical Standby ignores DDLs on internal schemas such as // SYS and SYSTEM. For a complete list of internal schemas ignored // by Logical Standby perform the following query: // SELECT owner FROM dba_logstdby_skip // WHERE statement_opt = 'INTERNAL SCHEMA'. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16248, 00000, "RFS connections not permitted during Terminal Apply" // *Cause: Writes by RFS are not permitted while Logical Standby is // performing Terminal Apply. // *Action: Permit any outstanding Logical Standby operations to complete. / 16249, 00000, "Terminal apply failed to complete during failover" // *Cause: The logical standby coordinator process terminated abnormally." // *Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the // abnormal shutdown, and resolve accordingly. Once the problem has // been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY // DATABASE command to complete the failover. / 16250, 00000, "Failed to acquire starting scn of new log stream" // *Cause: The starting SCN for the new log stream could not be determined. // *Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command. / 16251, 00000, "LSP1 Background Build not permitted" // *Cause: The LSP1 background process is not permitted to start because // it had previously been attempted. // *Action: This is an internal error. Contact Oracle support. / 16252, 00000, "Rebuild operation not permitted" // *Cause: The REBUILD operation is not permitted. // *Action: Only on a primary database that has failed to complete the LogMiner // dictionary build may the REBUILD operation take place. Reissue // the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed // to complete. / 16253, 00000, "Logical standby cannot start due to a prior, incomplete operation" // *Cause: A failure during a prior failover or configuration-related operation // left the logical standby in an inconsistent state. // *Action: Identify and reissue the operation before attempting to restart the // logical standby apply engine. / 16254, 00000, "change db_name to %s in the client-side parameter file (pfile)" // *Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname // command was successfully executed without a server parameter // file (spfile). // *Action: The client-side parameter file must be edited so that db_name // is set to the given name before mounting the database again. / 16255, 00000, "Log Auto Delete conflicts with another LogMiner session" // *Cause: Log Auto Delete cannot be on while another LogMiner // session is running on the same database. // *Action: Start Logical Standby without Log Auto Delete or destroy // other LogMiner sessions first. / 16256, 00000, "Failure to complete standby redo log file archival after failover" // *Cause: The standby redo log files processed during the failover of a // logical standby were not archived. // *Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival. / 16257, 00000, "Switchover initiated stop apply successfully completed" // *Cause: SQL Apply was stopped because of a switchover. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16258, 00000, "marking index unusable due to a constraint violation" // *Cause: A constraint violation occurred during the apply of a // direct path load. The index will be marked unusable and the // apply will be restarted. // *Action: No action necessary. See alert log for index schema and name. / 16259, 00000, "Switchover to logical standby requires a log archive destination" // *Cause: A valid log archive destination was not found to which the local // system could archive the end of redo (EOR) log file. A minimum of // one destination is required. // *Action: Ensure all log archive destinations are properly configured and, // if applicable, have network connectivity before reissuing the // ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL // operation. / 16260, 00000, "Waiting to replace partial or corrupt log file (thread# %s, sequence# %s)" // *Cause: LogMiner Reader process reached the end of a partial log file or // encountered a corrupted block. It is now waiting for the log file // to be recovered and reregistered. // *Action: No action necessary. Once the fetch archive log (FAL) archiver // replaces the log file, standby will automatically restart to // process the replaced file. / 16261, 00000, "Identification key mismatch for table \"%s\".\"%s\"." // *Cause: Internal error in SQL Apply. // *Action: Contact Oracle Support Services. / 16262, 00000, "Invalid value specified for Logical Standby parameter" // *Cause: The value specified in APPLY_SET is invalid for the parameter. // *Action: Specify correct parameter value. Please refer to documentation on // DBMS_LOGSTDBY PL/SQL package for details. / 16263, 00000, "Dynamic parameters can only be set on SQL apply instance" // *Cause: Attempt to set a Logical standby dynamic parameter on an instacne // other than where SQL apply coordinator is running. // *Action: Connect to the instance where SQL apply coordinator is running and // reissue the statement. / 16264, 00000, "invalid value for PREPARE_SERVERS parameter" // *Cause: attempt to set PREPARE_SERVERS parameter to zero or to a // value which would require MAX_SERVERS to be increased. // *Action: set PREPARE_SERVERS parameter to a non zero value and or // increase MAX_SERVERS parameter accordingly. / 16265, 00000, "Unsupported PL/SQL procedure encountered" // *Cause: Apply encountered an unsupported procedure from an Oracle // supplied PL/SQL package that is otherwise supported // *Action: Either add a skip rule for this procedure or manually apply the // procedure and restart apply skipping the failed transaction // Please refer to documentation on the PL/SQL package for details. / 16266, 00000, "Cannot instantiate a Logical Standby from another Logical Standby" // *Cause: An instantiation of a Logical Standby has been attempted for // another database with the Logical Standby role, which is not // supported. // *Action: Instantiate a Logical Standby database only from a Primary // Database. / 16267, 00000, "Cannot instantiate a Logical Standby during a switchover" // *Cause: An instantiation of a Logical Standby has been attempted for // a primary database that is in the middle of a switchover. // *Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel // the switchover, and attempt the instantiation again. / 16268, 00000, "user procedure processing of logical standby apply PL/SQL" // *Cause: A user-provided stored procedure was called to inspect a // PL/SQL statement prior to the statement 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. / 16269, 00000, "PL/SQL procedure skipped due to failure on primary database" // *Cause: Because the PL/SQL procedure failed when executed on the // primary database, it could not be executed on the standby database. // *Action: This informational statement is provided to record the event for // diagnostic purposes. The failed PL/SQL procedure needs to be // investigated to ensure it did not commit interesting data // before it failed. / 16270, 00000, "PL/SQL procedure skipped due to unmaintained standby objects" // *Cause: Because the PL/SQL procedure manipulated objects not being // maintained by the standby database, it was skipped. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16271, 00000, "PL/SQL successfully applied" // *Cause: A PL/SQL procedure was successfully applied on the logical // standby database. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16272, 00000, "PL/SQL procedure skipped due to skip setting" // *Cause: A setting in the logical standby skip table indicated // that this PL/SQL procedure should always be skipped. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. / 16273, 00000, "invalid value for APPLY_SERVERS parameter" // *Cause: attempt to set APPLY_SERVERS parameter to zero or to a // value which would require MAX_SERVERS to be increased. // *Action: set APPLY_SERVERS parameter to a non zero value or // increase MAX_SERVERS parameter accordingly. / 16274, 00000, "failure to perform operation on all Oracle RAC instances" // *Cause: One or more instances encountered an error while performing // an operation. // *Action: Ensure every instance in the Oracle RAC meets the requirements // for the operation, and retry the operation. / 16275, 00000, "prior failed CTAS detected and pre-existing table dropped" // *Cause: During the processing of a CTAS operation, an existing empty // table with the same name and attributes as the CTAS source table // was found, and the table was dropped. // *Action: No action is necessary. This informational statement is provided // to record the event for diagnostic purposes. 16276, 00000, "specified database link does not correspond to primary database" // *Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did // not link to the primary database for this logical standby database. // *Action: Specify a database link that corresponds to the primary database // for this logical standby database. The link should have // privileges to read and lock the table being instantiated, as well // as the SELECT_CATALOG_ROLE. 16277, 00000, "specified table is not supported by logical standby database" // *Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate // an unsupported table on the logical standby database. Tables with // unsupported data types cannot be replicated to a logical standby // database. // *Action: Specify a table which is not listed in the // DBA_LOGSTDBY_UNSUPPORTED_TABLE view. 16278, 00000, "specified table has a multi-object skip rule defined" // *Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE // must not have any skip rules defined with wildcard characters. // *Action: Remove or rewrite any skip rules defined for the specified table // so that they no longer contain wildcard characters, or no longer // affect the specified table. 16279, 00000, "supplied dblink does not have sufficient privileges" // *Cause: A dblink was specified that lacked one or more of the // CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles or that connects // to a user with insufficient privileges to lock the table. // *Action: Grant the necessary privileges to the dblink and the user to // which the dblink connects and retry the operation. / 16280, 00000, "cannot change master key on a logical standby database" // *Cause: An attempt was made to change the master key for transparent // data encryption on a logical standby database. // *Action: Set GUARD to NONE and reissue the command. This prevents you // from replicating tables with encrypted columns from the // primary database. / 16281, 00000, "missing identification key for table \"%s\".\"%s\"." // *Cause: No identification key was created for specified table. // *Action: Create a primakey key or unique index for specified table. / 16282, 00000, "operation not permitted during rolling upgrade" // *Cause: An operation was attempted that is not supported during a // rolling upgrade. // *Action: Retry the operation upon completion of the upgrade. / 16283, 00000, "operation not permitted on non-apply instance" // *Cause: An operation was attempted that is not supported since it // requires a running logical apply on the local instance. // *Action: Retry the operation on the instance on which the apply // engine is running. / 16284, 00000, "timed out waiting for an in-progress operation to complete" // *Cause: An operation timed out waiting for another operation to complete. // *Action: Retry the operation when the in-progress operation has // completed. / 16285, 00000, "operation not permitted due to inconsistent role state" // *Cause: A prior attempt to change the role of this database has failed // before the new role state could be fully committed. // *Action: Retry the previously attempted role-related operation before // attempting the current operation. / 16286, 00000, "operation not permitted due to lack of synchronized destination" // *Cause: A synchronized log archive destination was not found to which the // end-of-redo log file could be archived. // *Action: Before re-attempting the operation, wait at least one minute for // the Remote File Server to automatically recover any missing log // files or manually recover and register any missing log files with // logical standby. / 16287, 00000, "operation not permitted due to active apply state" // *Cause: An operation was attempted that was not supported while the logical // standby database had an active apply state. // *Action: Confirm the procedures used to configure the logical standby // database. Procedures which attempt to reconfigure a logical standby // database for a new primary database may encounter this error if an // error in a preliminary step was encountered. / 16288, 00000, "DDL skipped due to missing edition \"%s\"" // *Cause: The edition in which the DDL was performed on the primary // does not exist on the standby database. // *Action: No action is necessary. This infomational statement is provided // to record the event for diagnostic purposes. / 16300, 00000, "LSBY architected tracing event" // *Cause: // *Action: / 16301, 00000, "LSBY debug event" // *Cause: // *Action: // *Document: NO / 16302, 00000, "extended data type support is not supported for specified table" // *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that // was not supported for such an operation. The table either // does not have a primary key or it has a data type not supported // by this procedure. // *Action: Specify a table for which support exists in EDS_ADD_TABLE. / 16303, 00000, "specified table already has extended data type support" // *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that // already had EDS added on the local database. // *Action: None / 16304, 00000, "procedure must first be called on primary database" // *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical // standby database without having first called it on the primary // database. // *Action: Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and // then retry on the standby. / 16305, 00000, "procedure not supported on a logical standby" // *Cause: A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical // standby database which can only be called on a primary database // *Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database / 16306, 00000, "specified table does not have a primary key" // *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that // did not have a primary key. // *Action: Add a primary key and retry the operation. / 16307, 00000, "TSE key %s successfully applied" // *Cause: An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully // committed on the logical standby database. // *Action: No action necessary. This informational statement is provided // to record the event for diagnostic purposes. / 16308, 00000, "specified table has extended data type support" // *Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table // that is being maintained by extended data type support. // *Action: Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either // DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation. / 16311, 00000, "materialized view log already exists" // *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table // with a LOB that requires the creation of a specifically-defined // materialized view log but one already exists. // *Action: Drop the existing materialized view log and retry the operation. / / 16400 - 16499 Reserved for Physical Standby / 16400, 00000, "quota attributes are not allowed with DB_RECOVERY_FILE_DEST" // *Cause: Quota attributes for the destination parameters are not allowed // when the parameter DB_RECOVERY_FILE_DEST is defined. // *Action: No action is required. / 16401, 00000, "archive log rejected by Remote File Server (RFS)" // *Cause: An attempt was made to re-archive an existing archive log. // *Action: See alert log and trace file for more details. // No action is necessary. This is an informational statement provided // to record the event for diagnostic purposes. / 16402, 00000, "TRANSPORT=ONDEMAND is unsupported." // *Cause: The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was // specified on the primary database. // *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this // attribute from the LOG_ARCHIVE_DEST_n initialization parameter. 16403, 00000, "shut down in progress - remote connection is not permitted" // *Cause: A redo transport session could not be started because the database // was shutting down. // *Action: Wait for the remote instance to be restarted, or contact your DBA. / 16404, 0000, "Internal event for simulating software version mismatches" // *Document: NO // *Cause: This is an Oracle internal event code. It is used to test software // version mismatches between the primary and a standby database. // Setting this event causes the software version number to be // incremented by the value of the event level. // *Action: N/A, this is an Oracle internal event code. / 16405, 0000, "Internal event for simulating software version mismatches" // *Document: NO // *Cause: This is an Oracle internal event code. It is used to test software // version mismatches between the primary and a standby database. // Setting this event causes the software version number to be // decremented by the value of the event level. // *Action: N/A, this is an Oracle internal event code. 16406, 0000, "primary and standby database software version mismatch" // *Cause: The primary and standby databases were not running compatible // versions of Oracle server software. // *Action: Install the correct Oracle server software and try again. 16407, 00000, "An archive log from an earlier redo branch has been rejected" // *Cause: An archive log from a redo branch that is earlier than the one that // the standby database is currently applying was rejected. // *Action: No action is required. 16408, 00000, "An archive log from an incompatible redo branch has been rejected." // *Cause: An archive log from a redo branch that is incompatible with the one // that the standby database is currently applying was rejected. // *Action: No action is required. 16409, 00000, "archive log switchover reference number mismatch" // *Cause: The archive log switchover reference numbers of the primary // and standby database did not match. Remote archival of redo log // files is not allowed to incompatible standby database instances. // *Action: No action is required. 16410, 00000, "enable simulated LGWR netslave infinite wait" // *Document: NO // *Cause: Causes the LGWR to wait indefinitely to simulate network // connection indefinite stall. // *Action: N/A, this is an Oracle internal event code. 16411, 00000, "TRANSPORT=ONDEMAND is unsupported" // *Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was // specified on the primary database. // *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this // attribute from the LOG_ARCHIVE_DEST_n initialization parameter. 16412, 00000, "TRANSPORT=ONDEMAND is unsupported" // *Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was // specified on the primary database. // *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this // attribute from the LOG_ARCHIVE_DEST_n initialization parameter. 16413, 00000, "TRANSPORT=ONDEMAND is unsupported" // *Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was // specified on the primary database. // *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this // attribute from the LOG_ARCHIVE_DEST_n initialization parameter. 16414, 0000, "Event to prevent MRP from clearing online redo log files" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used to // prevent the MRP process from automatically creating or clearing // the online redo log files (ORLs) on a standby database. // *Action: N/A, this is an Oracle internal event code. / 16415, 0000, "Event to enable lock dumping" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to enable dumping of lock structures when desired. // *Action: N/A, this is an Oracle internal event code. / 16416, 00000, "No viable %sswitchover targets available" // *Cause: Switchover failed because no standby databases of the appropriate // type were available. // *Action: Check the alert log for errors, correct the problem and retry the // switchover. / 16417, 00000, "Activation occurred after recovery from standby redo log files; a full database backup is required" // *Cause: Activation occurred after recovery from standby redo log files. // *Action: Take a full database backup. / 16418, 0000, "Event to simulate idle RFS process in Physical Standby" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to simulate idle RFS process in Physical Standby // *Action: N/A, this is an Oracle internal event code. / 16419, 00000, "Snapshot standby must be converted to a physical standby database." // *Cause: The database was not a physical standby database. // *Action: Convert to physical standby database and retry the operation. / 16420, 00000, "fast-start failover target cannot be converted to snapshot standby" // *Cause: The database chosen for conversion to a snapshot standby was // the fast-start failover target standby database. // *Action: Choose another physical standby database and retry the operation. / 16421, 00000, "Event to disable streaming network I/O for Data Guard" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to disable streaming I/O for vaious Data Guard processes. // *Action: N/A, this is an Oracle internal event code. / 16422, 0000, "Event to disable archive process functions" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to disable archive process functions // *Action: N/A, this is an Oracle internal event code. / 16423, 0000, "Event to test ASM mirrors in Physical Standby" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to test ASM mirrors in Physical Standby. // *Action: N/A, this is an Oracle internal event code. / 16424, 0000, "RECOVER FINISH cannot complete due to a redo gap." // *Cause: RECOVER FINISH failed because there was a redo gap on the standby // database. // *Action: Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE // to perform an immediate failover with some data loss. / 16425, 0000, "RECOVER FINISH cannot be issued when recovery branch %s is not the target branch %s." // *Cause: RECOVER FINISH failed because a new branch existed on the physical // standby database. // *Action: Issue real-time apply recovery and see if recovery can proceed // on the new branch by checking if logs on the new branch are // applied by recovery. If so, issue another RECOVER FINISH. // Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE. / 16426, 0000, "Recovery requested an incorrect log from which to apply redo data." // *Cause: Media recovery selected an incorrect log. // *Action: Verify that the appropriate log has been properly registered // and restart media recovery. / 16427, 0000, "Redo gap is too large to resolve." // *Cause: The redo transport lag at this database was too large for // automatic redo gap detection to take place. // *Action: Re-create this standby database from a current backup copy of the // primary database. / 16428, 0000, "Event to set timeout value for ORA-19528 error" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to set the timeout value for the ORA-19528 error. // *Action: N/A, this is an Oracle internal event code. / 16429, 0000, "Event to disable Redo Transport Compression (RTC) back-off logic" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used to // disable Redo Transport Compression (RTC) back-off logic. // *Action: N/A, this is an Oracle internal event code. / 16430, 00000, "Event to kick off krs*.c error path tests" // *Document: NO // *Cause: Oracle internal testing only // *Action: N/A, this is an Oracle internal event for test purposes (valid // values are 1-26, 1 for krsa.c up through 26 for krsz.c) / 16431, 00000, "cannot expand control file" // *Cause: Additional redo log threads were added on the primary database // after the standby control file was created. // *Action: Shut down the standby database and replace the control file with a // new standby control file from the primary database or change the // COMPATIBLE parameter to 10.2.0 or above and restart the standby // database. / 16432, 00000, "inconsistent set of logs applied at a standby database" // *Cause: Redo apply stopped because it detected an inconsistency in the // progression of the SCNs. If this database is a bystander standby // database, this is most likely due to a failover operation in which // incompatible logs were applied from the old and new primary // databases. // *Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from // V$DATABASE on the new primary database. Then, flashback the target // database to this SCN and use RMAN to delete all archive logs at or // beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs // corresponding to the failover operation from the new primary and // register all these logs at the target database. Restart redo apply. / 16433, 00000, "The database must be opened in read/write mode." // *Cause: An attempt was made to open the database in read-only mode after an // operation that requires that the database be opened in read/write // mode. // *Action: Open the database in read/write mode. The database can then be // opened in read-only mode. 16434, 00000, "Archive log for branch %s thread %s sequence %s cannot be queued." // *Cause: An archive log needed by the standby database to resolve a redo gap // was not found on the primary database. This is a fatal situation // during a switchover because the primary database waits for the // target standby to be clear of all archive log gaps before allowing // the switchover to proceed. If a redo gap cannot be resolved, the // switchover cannot succeed. // *Action: If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID // of the local destination on the primary database but no longer // exists in that location on disk, the archived log can be copied // back to that location to allow gap processing to automatically // resolve the gap. If the specified log has been purged from // V$ARCHIVED_LOG, the archived log can be copied to disk on either // the primary or standby database and registered using the // ALTER DATABASE REGISTER OR REPLACE LOGFILE command. / 16435, 0000, "Event to bypass RFS on high destinations" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to bypass RFS on high destinations. // *Action: N/A, this is an Oracle internal event code. / 16436, 00000, "ALTER DATABASE ... RECOVER FINISH could not start" // *Cause: ALTER DATABASE ... RECOVER FINISH failed to start because the // standby database was missing redo changes below the checkpoint of // data files. // *Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead. / 16437, 00000, "No active coordinator RFS for current operation" // *Cause: The coordinator Remote File Server (RFS) for this parallel archival // either abnormally terminated or ran down before this subordinate // RFS could begin its leg of the operation. // *Action: No explicit user action is required. / 16438, 00000, "Switchover to primary cannot be executed at this time" // *Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be // executed because an incompatible operation such as // RMAN restore or flashback was in progress. See the database alert // log for details. // *Action: Wait for the incompatible operation to complete. The files that // have been flashed back or restored need recovery before you // can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY // statement. Start redo apply and verify that the // SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY // or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO // SWITCHOVER TO PRIMARY. / 16439, 00000, "Standby not ready to receive redo at this time" // *Cause: A logical standby or down stream capture database was not in a // state where it could accept a request to receive redo from // another database. This was likely due to the database not being // open. // *Action: See the database alert log at the receiving side of the transfer // for details of why the database was not ready. // If the database was mounted but not open, open it to clear // the problem. The initialization parameter // LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be // set to ENABLE. // / NOTE: 16440 - 16447 are reserved for Flush Redo To Standby project. / 16440, 00000, "Control file is corrupt." // *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file // was corrupt. // *Action: Restore the current control file at the primary database and then // reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted // primary instance. / 16441, 00000, "Current log %s for thread %s sequence %s is invalid." // *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo // log file was corrupt. // *Action: Restore the current log at the primary database, and then reissue // ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted // primary instance. / 16442, 00000, "ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied." // *Cause: The target standby database did not apply all received redo. // *Action: Allow the target standby database to apply all redo and then // reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement. / 16443, 00000, "could not switch out of log %s thread %s" // *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the // current log. // *Action: This can happen if there are one or more errors during archival of // the current log at the primary database. Reissue ALTER SYSTEM FLUSH // REDO TO STANDBY after resolving the archiving errors. / 16444, 00000, "ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file." // *Cause: A flush redo operation discovered SCNs greater than a previously // failed flush redo operation. // *Action: This can happen if there are one or more errors that have // corrupted the control file or online redo logs. In these cases, // flush redo operation is not possible. / 16445, 00000, "Database has to be mounted and cannot be open" // *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be // mounted, but not opened. // *Action: Mount the database and then reissue the operation. / 16446, 00000, "Target database was not a standby database" // *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target // database is not a standby database. // *Action: Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and // specify a standby database as the target database. / 16447, 00000, "Redo apply was not active at the target standby database" // *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply // is not active at the target database. // *Action: Start redo apply at the standby database and reissue the // ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the // ALTER SYSTEM FLUSH REDO TO STANDBY statement with the // NO CONFIRM APPLY clause. / 16448, 00000, "Primary database corruption has been detected by standby database." // *Cause: The primary database became corrupted. // *Action: Identify the extent of the corruption on both the primary and // standby database and take remedial action. / 16449, 00000, "incomplete redo thread enable operation" // *Cause: The switchover operation could not continue because it failed to // disable a thread that was left in an incomplete thread enable // state. // *Action: Check alert log for more details. / 16450, 00000, "Internal event for disabling ignoring of destination during open" // *Document: NO // *Cause: This is an internal event used for testing purposes. It is use // for disabling the ability to ignore max perf destinations during // open of database. It is used for testing various situations // with foreground death performing the open as it pertains to // ignoring max perf destinations. // *Action: No action is necessary. / 16451, 00000, "A remote archival request has timed out." // *Cause: When opening or closing a database instance, the database may wait // for up to 1 minute for pending remote archival requests to be // performed before proceeding with the operation. This error was // reported because that time limit was exceeded. // *Action: This is an informational message so no action is required. / 16452, 00000, "internal event for SRL-related testing" // *Document: NO // *Cause: This is an internal event code. This event is used // for SRL-related testing. // *Action: NA. This is an Oracle internal event code. / 16453, 0000, "Event for the first Timing Measurement Interface (TMI)" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to measure the difference in performance of Physical Standby // across different labels. // *Action: N/A, this is an Oracle internal event code. / 16454, 0000, "Standby redo log could not be selected" // *Document: NO // *Cause: Selection of standby redo log failed. Check the trace // file for the exact cause. // *Action: This is used internally. No action is required. / 16455, 00000, "switchover to standby failed" // *Cause: An attempt to switchover to a physical standby database failed. // *Action: Check alert log for more details. Issue the SHUTDOWN ABORT command // on the database before issuing another ALTER DATABASE COMMIT TO // SWITCHOVER TO STANDBY command. / 16456, 00000, "switchover to standby in progress or completed" // *Cause: The requested operation was not allowed because a switchover to // standby operation was either in progress or had completed. // *Action: Issue the SHUTDOWN ABORT command on the database after switchover // operation completes. / 16457, 00000, "Event to inject CFTXN errors during testing" // *Document: NO // *Cause: Oracle internal testing only. // *Action: None. This is an Oracle internal event for test purposes. / 16458, 00000, "Event to invoke I/O hangs during testing" // *Document: NO // *Cause: Oracle internal testing only. // *Action: None. This is an Oracle internal event for test purposes. 16462, 00000, "Event to generate a testing log file header" // *Document: NO // *Cause: Oracle internal testing only. // *Action: None. This is an Oracle internal event for test purposes. / / 16500 - 16699 Reserved for Data Guard Broker / 16501, 00000, "the Data Guard broker operation failed" // *Cause: The Data Guard broker operation failed. // *Action: See accompanying messages for details. / 16502, 00000, "the Data Guard broker operation succeeded with warnings" // *Cause: The Data Guard broker operation succeeded with warnings. // *Action: See accompanying messages for details. / 16503, 00000, "cannot exceed the maximum number of databases in this configuration" // *Cause: The Data Guard broker configuration already contained the maximum // number of databases that could be configured and managed by the // broker. // *Action: Select and remove an existing database from the broker // configuration, then reissue the command to add another database // to the configuration. Note that when COMPATIBLE is set lower // than 11.2.0.0.0, the broker can configure and manage up to 10 // databases. When COMPATIBLE is set to 11.2.0.0.0 or higher, this // limit is increased to 31. / 16504, 00000, "the Data Guard configuration already exists" // *Cause: A request to create a Data Guard configuration was made while // connected to a database that is part of an existing configuration. // *Action: To create a new configuration, the existing configuration must be // deleted. / 16505, 00000, "site identifier is invalid" // *Document: NO // *Cause: The request contained an invalid site identifier. The was an // internal error. // *Action: Contact Oracle Support Services. / 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" // *Document: NO // *Cause: The specified request identifier was not recognized by // the Data Guard broker. This was an internal error. // *Action: Contact Oracle Support Services. / 16508, 00000, "channel handle not initialized" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16509, 00000, "request timed out" // *Cause: The Data Guard broker timed out out the request. // *Action: Check the Data Guard broker log file for more information. Ensure // that the network connections between the databases are functioning // properly and retry the request. / 16510, 00000, "messaging error using ksrwait" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16511, 00000, "messaging error using ksrget" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16512, 00000, "parameter exceeded maximum size limit" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16513, 00000, "maximum requests exceeded" // *Cause: The maximum number of requests that the broker can service / on the database instance was exceeded. // *Action: Wait for the broker to complete processing the requests before // issuing more requests. / 16514, 00000, "request was not found" // *Document: NO // *Cause: An attempt was made to read a response but a matching request // was not found. This was an internal error. // *Action: Contact Oracle Support Services. / 16515, 00000, "no receive channel" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16516, 00000, "current state is invalid for the attempted operation" // *Cause: The broker may have returned this error for either switchover // operations or for database state change operations. // If this error was returned for a switchover operation, the broker // determined that either: // // - The databases changing roles are shut down. // - The primary database is not shipping redo data. // - The standby database that will become the primary database // is not applying redo data. // // If this error was returned for database state change operations, // the database state specified was invalid. // *Action: If this error is returned when attempting a switchover operation, // make sure that: // // - The databases changing roles are started. // - The primary database is shipping redo data. // - The standby database is applying redo data. // // If this error is returned when attempting a database state // change operation, make sure a valid database state is // specified. / 16517, 00000, "object handle is invalid" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16518, 00000, "unable to allocate virtual instance ID" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16519, 00000, "resource handle is invalid" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16520, 00000, "unable to allocate resource ID" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16523, 00000, "operation requires the client to connect to instance \"%s\"" // *Cause: The switchover or failover operation required the client to // connect to the apply instance of the target database. // *Action: Connect to the indicated instance and reissue the SWITCHOVER or // FAILOVER command. / 16524, 00000, "unsupported command, option, or argument" // *Cause: A command, option, or fast-start failover condition argument // was specified that is not supported in this release. // *Action: If trying to enable or disable a fast-start failover condition, // try a different Oracle error number. Otherwise, contact Oracle // Support Services. / 16525, 00000, "the Data Guard broker is not yet available" // *Cause: The Data Guard broker process was either not yet started, was // initializing, or failed to start. // *Action: If the broker has not been started, set the DG_BROKER_START // initialization parameter 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 memory to process request" // *Cause: The Data Guard broker was unable to allocate memory for a request. // *Action: Increase the size of the System Global Area (SGA). / 16527, 00000, "unable to allocate broker System Global Area (SGA) memory" // *Cause: The Data Guard broker was unable to allocate memory within the // System Global Area (SGA). // *Action: Increase the size of the System Global Area (SGA) memory. / 16528, 00000, "unable to allocate Program Global Area (PGA) memory" // *Cause: There was insufficient space in Program Global Area (PGA) to // allocate memory. // *Action: Increase process virtual memory. / 16529, 00000, "bad sender ID" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16530, 00000, "invalid buffer or length" // *Cause: A NULL buffer or a length of zero was specified. // *Action: Correct the command parameters and retry the command. / 16531, 00000, "unable to post message" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16532, 00000, "Data Guard broker configuration does not exist" // *Cause: A broker operation was requested that required a broker // configuration to already be created. // *Action: Create a Data Guard broker configuration prior to performing // other broker operations. If only one instance of a RAC // database is reporting this error, ensure that the // DG_BROKER_CONFIG_FILE[1|2] initialization parameters are // set to file locations that are shared by all instances of // the RAC database. / 16533, 00000, "inconsistent Data Guard broker state" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16534, 00000, "switchover, failover or convert operation in progress" // *Cause: The Data Guard broker returned this status because a switchover, // failover or convert operation was in progress. The broker could // not accept new requests until the operation finished. // *Action: Wait until the operation is complete and reissue the request. / 16535, 00000, "Oracle Restart or Oracle Clusterware prevented completion of broker operation" // *Cause: The broker could not complete the operation because Oracle Restart // (for single instance databases) or Oracle Clusterware (for RAC // databases) could not stop services or instances on this database. // *Action: Check the Data Guard broker log file for more information and // stop the appropriate services or instances using SRVCTL. Then // retry the broker operation. / 16536, 00000, "unknown object type" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16537, 00000, "child count exceeded" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16538, 00000, "no match on requested item" // *Cause: The Data Guard broker did not recognize the specified // property or state name, or a fast-start failover condition // was specified that is not enabled. // *Action: Verify command parameters and reissue the request. / 16539, 00000, "task element not found" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16540, 00000, "invalid argument" // *Cause: One of the arguments for the specified request was invalid for // the request type. // *Action: Verify arguments and then reissue the request. / 16541, 00000, "database is not enabled" // *Cause: The database specified in the request was not enabled. // *Action: Select an enabled database and reissue the request. / 16542, 00000, "unrecognized operation" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16543, 00000, "invalid request made to broker" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16544, 00000, "modifying DG_BROKER_START requires SID='*' qualifier" // *Cause: The setting for the DG_BROKER_START parameter must be exactly // the same on all RAC database instances. The SID='*' qualifier // was required in the command. // *Action: Reenter the command using the SID='*' qualifier. / 16545, 00000, "unable to get response" // *Document: NO // *Cause: The Data Guard broker was unable to return the result of // a previous request. This was an internal error. // *Action: Contact Oracle Support Services. / 16546, 00000, "missing or invalid value" // *Document: NO // *Cause: The value of the request to return was not specified or was // invalid. This was an internal error. // *Action: Contact Oracle Support Services. / 16547, 00000, "cannot disable or delete the primary database" // *Cause: An attempt was made to disable broker management of the primary // database or delete the primary database from the broker // configuration while the configuration was enabled. // *Action: If you wish to disable broker management of the primary // database when the configuration is enabled, you must instead // disable broker management of the entire broker configuration. // If you wish to delete the primary database from the broker // configuration while the configuration is enabled, you must // instead delete the entire broker configuration. / 16548, 00000, "database not enabled" // *Cause: An attempt was made to modify or query a disabled database. // This error is also returned on an attempt to enable, modify, // or query a database that the broker has disabled because of a // switchover or failover operation. The broker disables its // management of a database when it detects that the database needs // to be re-created because of a failover or switchover operation. // *Action: If broker management of the database is disabled, enable it // and reissue the request. / 16549, 00000, "invalid string" // *Cause: An invalid or NULL string value was specified. // *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 receive buffer. / 16551, 00000, "short string copied" // *Cause: A string property value that did not fill the receive buffer // was placed in the receive buffer. // *Action: This is an informational message only. / 16552, 00000, "error occurred while generating directives for client" // *Cause: The operation could not be completed because the broker // required assistance from the client that it was unable to // provide because of the accompanying error. // *Action: See the accompanying error message for more information and // follow the directions provided in the Action section of that // message. Then retry the operation. / 16553, 00000, "the Data Guard broker process (DMON) failed to shutdown" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16554, 00000, "translation not valid" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16555, 00000, "database is not active" // *Cause: An operation was attempted on a database that was not active. // not active. // *Action: Verify that the database is active and retry the operation. / 16556, 00000, "observer version mismatch" // *Cause: This version of the observer was incompatible with the version // of the specified Oracle database server to which the observer // had been connected. This observer client cannot be used to // observe the specified Oracle server. // *Action: Use a version of the observer that is compatible with the // Oracle database server to be observed. / 16557, 00000, "database is already in use" // *Cause: An attempt was made to create a duplicate database in the // broker configuration, or to add a duplicate instance (sid) // for an existing database in the broker configuration. // *Action: Check the database to be added to ensure there are no duplicates. / 16558, 00000, "database specified for switchover is not a standby database" // *Cause: An attempt was made to switchover to a database that was not a // standby database. // *Action: Locate an enabled standby database and select that database as // the target of the switchover. / 16559, 00000, "out of memory at %s" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16560, 00000, "unable to convert document, syntax error at \"%s\" " // *Document: NO // *Cause: There was an error in the specified sting. // *Action: Correct the errors and submit the request again. / 16561, 00000, "cannot remove an active instance" // *Cause: The instance to be removed was running. // *Action: Shut down the instance and reissue the REMOVE command. / 16562, 00000, "INTENDED_STATE not used here, syntax error at \"%s\"" // *Document: NO // *Cause: There was an error in the specified string. // *Action: Correct the errors and submit the request again. / 16563, 00000, "unable to add value, syntax error at \"%s\"" // *Document: NO // *Cause: There was an error in the specified string. // *Action: Correct the errors and submit the request again. / 16564, 00000, "lookup failed, syntax error at %s" // *Document: NO // *Cause: There was an error in the specified string. // *Action: Correct the errors and submit the request again. / 16565, 00000, "duplicate property, syntax error at \"%s\"" // *Document: NO // *Cause: There was an error in the specified string. // *Action: Correct the errors and submit the request again. / 16566, 00000, "unsupported document type" // *Document: NO // *Cause: The XML document type was not supported. // *Action: Correct the errors and submit the request again. / 16567, 00000, "Data Guard broker internal parser error at \"%s\"" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16568, 00000, "cannot set property %s" // *Cause: The specified property could not be modified because it was // either a monitorable property or a property that did not exist. // *Action: Retry the command with a valid configurable property. / 16569, 00000, "Data Guard configuration is not enabled" // *Cause: The requested operation required that broker management of the // Data Guard configuration must be enabled. // *Action: Enable the Data Guard configuration and reissue the request. / 16570, 00000, "database needs restart" // *Cause: The Data Guard broker operation required this database instance // to be shut down and restarted. // *Action: If DGMGRL or Enterprise Manager has not already done so, // shut down the Oracle instance and then restart it. / 16571, 00000, "Data Guard configuration file creation failure" // *Cause: The Data Guard broker was unable to create the configuration // file on permanent storage. // *Action: Verify space, permissions and file name as indicated by the // DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry // the operation. / 16572, 00000, "Data Guard configuration file not found" // *Cause: The Data Guard broker configuration file was either unavailable or // did not exist. // *Action: Verify that the configuration file was successfully created. // If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were // changed, ensure the file name on disk and the parameter value // match, there is space on the device, and the proper permissions // are granted. For a RAC database, ensure that these initialization // parameters are set to file locations that are shared by all // instances of the RAC database. / 16573, 00000, "attempt to change or access configuration file for an enabled broker configuration" // *Cause: The operation was rejected because the Data Guard broker // configuration file was in use. The attempted operation // was unsafe while broker management of the configuration was // enabled. For example: // - An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] // initialization parameters while the broker was running. // - Non-broker access (such as DBMS_FILE_TRANSFER) to the // configuration files was attempted. See the alert log for // additional information. // *Action: Disable the broker configuration and shut down the Data Guard // broker, then retry the operation. If the operation includes // altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, // be sure that the new parameter values correctly specify the files // at their expected location before reenabling broker management of // the configuration. / 16574, 00000, "switchover disallowed when required databases are shut down" // *Cause: Switchover failed because either the primary database or the // designated standby database were shut down. // *Action: Ensure that the primary and standby databases are running and // that primary database is shipping redo data to the designated // standby database. Also ensure that that the designated standby // database is applying the redo data received from the primary // database. / 16575, 00000, "request terminated because failover is in progress" // *Cause: This error was returned when the broker terminated a request // because it was processing a failover command. // *Action: Wait for failover to complete and then retry the request. / 16576, 00000, "failed to update Data Guard configuration file" // *Cause: A failure was encountered while the broker was updating // the Data Guard broker configuration file on permanent storage. // *Action: Verify space, permissions and file name as indicated by the // DG_BROKER_CONFIG_FILE[1|2] initialization parameters. / 16577, 00000, "corruption detected in Data Guard configuration file" // *Cause: The Data Guard broker detected errors while loading the // configuration file. // *Action: Verify space, permissions and file name as indicated by the // DG_BROKER_CONFIG_FILE[1|2] initialization parameters. // Contact Oracle Support Services. / 16578, 00000, "failed to read Data Guard configuration file" // *Cause: A failure was encountered while the broker was reading // the configuration file on permanent storage. // *Action: Verify space, permissions and file name as indicated by the // DG_BROKER_CONFIG_FILE[1|2] initialization parameters. / 16579, 00000, "bad network state detected" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16580, 00000, "bad network link" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16581, 00000, "Data Guard broker could not reach remote database" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16582, 00000, "cannot change instance-specific property" // *Cause: An attempt was made to change an instance-specific property // for a database that had more than one instance. // *Action: Retry the command and identify a specific instance whose // property value is to be changed. / 16583, 00000, "bad Data Guard broker connection process state" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16584, 00000, "operation cannot be performed on a standby database" // *Cause: The database specified for the operation was a standby database, // or the operation was attempted on a standby database. // *Action: Check the database type and retry the operation. If the command // must be executed on a primary database, connect to the primary // database and retry the operation. / 16585, 00000, "operation cannot be performed on a primary database" // *Cause: The database specified for the operation was a primary database, // or the operation was attempted on a primary database. // *Action: Check the database type and retry the operation. If the command // must be executed on a standby database, connect to a standby // database and retry the operation. / 16586, 00000, "cannot change database property with EDIT INSTANCE command" // *Cause: An attempt was made to change a database property using an // EDIT INSTANCE command instead of an EDIT DATABASE command. // *Action: Use the EDIT DATABASE command to change database properties. / 16587, 00000, "ambiguous object specified to Data Guard broker" // *Cause: An object was specified that the broker could not uniquely // distinguish from other objects in the configuration. // *Action: Try to further distinguish the object specified for the operation // and reissue the command. / 16588, 00000, "no more internal buffers" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16589, 00000, "Data Guard broker detected network transfer error" // *Cause: The Data Guard broker detected an error while transferring data // from one database to another. This may happen when: // - the broker detects an inconsistency in the block count of // configuration file when the file is transmitted between // databases. // - the broker encountered an error when writing the configuration // file. // *Action: Contact Oracle Support Services. / 16590, 00000, "Data Guard configuration does not contain a primary database" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16591, 00000, "unknown field \"%s\" in document" // *Document: NO // *Cause: There was an error in the specified string. // *Action: Correct the errors and submit the request again. / 16592, 00000, "missing field \"%s\" in document" // *Document: NO // *Cause: There was an error in the specified string. // *Action: Correct the errors and submit the request again. / 16593, 00000, "XML conversion failed" // *Document: NO // *Cause: There was an error in the XML document. // *Action: Correct the errors and submit the request again. / 16594, 00000, "DMON background process is not running" // *Cause: The Data Guard broker background process, DMON, was not running. // *Action: Check the Data Guard broker log and DMON process trace file // to determine why the DMON process is not running. / 16595, 00000, "process %s failed to terminate" // *Cause: The specified process did not terminate at the request of the Data // Guard broker. // *Action: Contact Oracle Support Services. / 16596, 00000, "database not part of the Data Guard broker configuration" // *Cause: The specified database is not in the Data Guard broker // configuration. // *Action: Retry the command with a database that is in the broker // configuration. / 16597, 00000, "Data Guard broker detects two or more primary databases" // *Cause: The Data Guard broker detected two or more primary databases in // the broker configuration and could not continue. // *Action: Contact Oracle Support Services. / 16598, 00000, "Data Guard broker detected a mismatch in configuration" // *Cause: The Data Guard broker detected a significant mismatch while // performing configuration membership validation between two // or more databases in the broker configuration. This can occur // when the primary database has stale broker configuration files. // *Action: Contact Oracle Support Services. / 16599, 00000, "Data Guard broker detected a stale configuration" // *Cause: The Data Guard broker detected a stale configuration during // initialization for this database. // *Action: The broker will automatically resolve this situation once the // primary database completes its initialization. / 16600, 00000, "not connected to target standby database for failover" // *Cause: The failover command failed because the client was not connected // to the target standby database. // *Action: Explicitly connect to the standby database to be failed over to and // retry the failover command. / 16601, 00000, "site contains required resources that are disabled" // *Document: NO // *Cause: Resources required to complete this command were disabled. // *Action: Enable all required resources and reissue the request. / 16602, 00000, "database must be disabled to perform this operation" // *Cause: An attempt was made to edit a database property while the // database was enabled. // *Action: Disable the database and retry the command. / 16603, 00000, "Data Guard broker detected a mismatch in configuration ID" // *Cause: There was a mismatch in configuration unique ID. This could occur // if the original configuration was re-created while this database // was disconnected from the network or the same database was added // to two different Data Guard broker configurations. // *Action: Make sure the database belongs to only one broker configuration. // Shut down the broker by setting the DG_BROKER_START initialization // parameter to false. Then remove the Data Guard broker configuration // files. Finally restart the broker by setting the DG_BROKER_START // initialization parameter to true. / 16605, 0000, "event to control fast-start failover diagnostic tracing" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to control fast-start failover diagnostic tracing. // DO NOT USE. // *Action: N/A, this is an Oracle internal event code. / 16606, 00000, "unable to find property \"%s\"" // *Cause: The specified property did not exist. // *Action: Specify a valid property name and reissue the request. / 16607, 00000, "one or more databases have failed" // *Cause: A failure was detected for one or more databases in the Data // Guard broker configuration. // *Action: Locate the database(s) with a failure status and correct it. / 16608, 00000, "one or more databases have warnings" // *Cause: A warning was detected for one or more databases in the Data // Guard broker configuration. // *Action: Locate the database(s) with a warning status and correct it. / 16609, 00000, "database is being disabled" // *Cause: A command was attempted on a database that was being disabled. // For example, attempting to reinstate the old primary database, // the database that was the primary database prior to the most // recent failover, before it was ready to be reinstated. // *Action: Wait for the Data Guard broker to disable the database and then // retry the command. / 16610, 00000, "command \"%s\" in progress" // *Cause: The specified broker command was already running and the // command issued could not be completed. // *Action: Wait for the specified command to finish and then retry the // command. / 16611, 00000, "command aborted at user request" // *Cause: The command was aborted 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 was too long. // *Action: Specify a shorter string value. / 16613, 00000, "initialization in progress for database" // *Cause: A request was made that required access to the Data Guard // broker configuration before the Data Guard broker had // completed initialization. // *Action: Wait until the Data Guard broker has completed initialization, // then reissue the request. / 16614, 00000, "Data Guard broker configuration is disabled" // *Cause: An attempt to enable a database failed because the Data Guard // broker configuration was disabled. // *Action: Enable the Data Guard broker configuration and issue the DGMGRL CLI // SHOW CONFIGURATION command to see if there are any databases that // are still disabled. If the database you tried to enable is still // disabled, issue the DGMGRL CLI SHOW DATABASE command to check // the status of the database. If the database status indicates // that the database needs to be reinstated then issue the DGMGRL // CLI REINSTATE DATABASE command to reinstate and enable the // database. If the database does not require reinstatement then // issue the DGMGRL CLI ENABLE DATABASE command to enable the // database. / 16615, 0000, "event for Data Guard NetSlave testing" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used for // verifying NetSlave functionality in Data Guard. DO NOT USE. // *Action: N/A, this is an Oracle internal event code. / 16616, 0000, "event for Data Guard monitor testing" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used for // verifying Monitor functionality in Data Guard. DO NOT USE. // *Action: N/A, this is an Oracle internal event code. / 16617, 0000, "unknown object identifier specified in request" // *Cause: Object identifier specified in the request was invalid or // unknown. // *Action: Verify that a valid object identifier is specified and reissue // reissue the request. / 16618, 0000, "response document of size \"%s\" bytes is too large" // *Document: NO // *Cause: The document response could not be returned because the size // of the document was too large. // *Action: View the broker log for the given database directly. / 16619, 0000, "condition for fast-start failover is already enabled" // *Cause: The condition specified for fast-start failover was already // enabled. // *Action: No action is required. Use the DGMGRL CLI SHOW FAST_START FAILOVER // command to see the conditions that are enabled. / 16620, 0000, "one or more databases could not be reached for a delete operation" // *Cause: One or more standby databases could not be reached for either // a DGMGRL CLI REMOVE DATABASE or a REMOVE CONFIGURATION command. // *Action: This typically indicates a network problem where the standby // database is unable to respond to the primary database. In the // event of this situation, examine the primary database Data // Guard broker log to determine which standby databases could // not be reached. For each standby database not reached, // connect to that database and shut down the broker by setting the // initialization parameter, DG_BROKER_START, to false. After the // broker has been shut down for the standby database, locate the // Data Guard broker configuration files from the standby database // DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and // delete them. Then restart the broker by setting DG_BROKER_START to // true. / 16621, 0000, "database name for ADD DATABASE must be unique" // *Cause: An attempt was made to add a database to the broker configuration // that already included a database with the specified name. The // database names must be unique. // *Action: Verify that a unique name is specified for the new database // to be added. Also, the database name must match the DB_UNIQUE_NAME // initialization parameter of the database. / 16622, 0000, "two or more broker database objects resolve to the same database" // *Cause: Multiple database objects referred to the same database. // *Action: Examine the details of all databases in the broker configuration // and verify that there are not two or more databases referring to // the same database. If two or more database profiles in the // broker configuration have the same value for the // DGConnectIdentifier database property, either: // - Remove and re-add the erroneously defined database(s) to resolve // the ambiguity. // - Ensure that the DGConnectIdentifier database property for each // database allows the broker to properly connect to that database. / 16623, 0000, "database detected role change" // *Cause: A successful switchover or failover operation had been completed // and was detected during database startup or broker health check. // If this database was unavailable during a switchover or failover // operation, it may not be a viable standby database for the new // primary database and was disabled by the Data Guard broker. // *Action: Connect to the new primary database and examine the broker // configuration for databases that were disabled and that may require // reinstatement or re-creation. / 16624, 0000, "broker protocol version mismatch detected" // *Cause: A network protocol version number mismatch was detected. // This could happen if the databases in the broker configuration // were not running the same version of Oracle. The broker would // disable standby databases that were not running the same version // of Oracle as the primary database if this situation was detected. // *Action: Examine the version of Oracle installed on all databases in // the broker configuration to ensure they are identical. Once all // of the databases in the broker configuration are running the same // version of Oracle, reenable the standby databases that were // disabled. / 16625, 0000, "cannot reach database \"%s\"" // *Cause: The command could not be executed because the database noted // in the error text was not reachable from the database where // the command was issued. // *Action: See accompanying messages for more information. Check the network // connections to the specified database. Alternatively, connect to // a different database in the Data Guard broker configuration and // retry the command. / 16626, 0000, "failed to enable specified database" // *Cause: This status was returned when attempting to enable a standby // database that: // - Could not locate itself in the broker configuration file. // - Failed to distinguish itself from two or more databases in // the configuration file. // - Determined it missed a role change within the configuration. // *Action: To correct the problem, try one of these actions: // - Confirm that the host and SID names for the database exactly // match the values in the HOST_NAME and INSTANCE_NAME columns // of V$INSTANCE. // - Confirm that there are not two or more databases with the // same connect identifier. That is, multiple databases in the // broker configuration should not reach the same database. // - If a failover had been performed and the old primary database // has been re-created (or a standby database has been re-created), // make sure the Data Guard broker configuration files have been // removed for that database. Do NOT remove the configuration // files that are in use by the new primary database. / 16627, 0000, "operation disallowed since no standby databases would remain to support protection mode" // *Cause: This status was returned because of one of the following: // - The broker rejected an attempt to change the overall // configuration protection mode since it could not find any // enabled standby databases that supported the proposed protection // mode. // - The broker rejected an attempt to enable the configuration // if it determined that there were no enabled standby databases // that supported the overall protection mode. // - The broker rejected an attempt to disable or remove a database // that, if disabled or deleted, would result in no remaining // standby databases that could support the overall configuration // protection mode. // - The broker rejected an attempt to switchover if doing so would // violate the overall configuration protection mode. // - Performing automatic health check if the broker determined that // no standby datbases supported the overall protection mode. // *Action: - If changing the overall protection mode, confirm that at least // one standby database satisfies the new protection mode. // - For enable failures, confirm that at least one standby database // has a LogXptMode configurable property setting that supports // the current overall protection mode. // - For delete and disable failures, confirm that at least one // other standby database has a LogXptMode configurable property // setting that supports the overall protection mode. // - For switchover failures that occur when the configuration // is operating in maximum protection or maximum availability // mode, confirm that at least one other standby database has its // LogXptMode configurable property set to the value "SYNC". // If the configuration contains a primary database and a single // standby database and is operating in either maximum protection // or maximum availability mode, ensure that the LogXptMode // configurable property of the primary database is set to the // value "SYNC". Since the old primary database will become the // standby database after switchover completes, its LogXptMode // configurable property setting must support the configuration // protection mode. // - For health check error, confirm that at least one standby // database has a LogXptMode configurable property setting // that supports the current overall protection mode. / 16628, 00000, "broker protection mode inconsistent with the database setting" // *Cause: The Data Guard broker protection mode saved in the broker // configuration file was inconsistent with the actual database // setting. // *Action: Reset the protection mode through the Data Guard broker. / 16629, 00000, "database reports a different protection level from the protection mode" // *Cause: The current database protection level was different from the // configured protection mode. This typically was caused by redo // transport problems, or the primary database was not open. // *Action: Check the database alert logs and Data Guard broker logs // for more details. Also, check the redo transport status. Ensure // that one standby database supports the configured protection // mode and that the network to that standby database is working // properly. Ensure the primary database is open. / 16630, 00000, "database property has been deprecated" // *Cause: The property that was specified in the command was deprecated. // *Action: Check the broker documentation to identify a replacement property // or SQL command for the deprecated property. / 16631, 00000, "operation requires shutdown of database or instance \"%s\"" // *Cause: The Data Guard broker operation required a shutdown of the // database or instance. // *Action: If database or instance has not been shutdown by the DGMGRL CLI // or Enterprise Manager, shutdown the database or instance // manually. / 16632, 00000, "instance being added to database profile" // *Cause: The Data Guard broker determined that an instance // successfully found its database profile within the broker // configuration file, but lacked an instance-specific profile. // The broker automatically created an instance-specific // profile and associated the instance with its database profile. // *Action: No user action is required. The broker will automatically // associate the instance with its database profile and incorporate // the instance into broker activity. / 16633, 00000, "the only instance of the database cannot be removed" // *Cause: The instance to be removed was the only instance of the // corresponding database that was known to the broker. // *Action: Remove the corresponding database object from the broker // configuration instead of the individual instance object of // the database. / 16634, 0000, "Event for Data Guard NetSlave tracing" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used to // control trace output of the Data Guard NetSlave process. DO // NOT USE. // *Action: N/A, this is an Oracle internal event code. / 16635, 0000, "network connection failed during transmission" // *Cause: The Data Guard broker detected a connection failure to a remote // database in the broker configuration. This failure happened // in the middle of a transmission session. A transmission session // usually requires more than one send operation for sending a large // amount of data (for example, the broker configuration file) to // the remote database. // *Action: In most cases, no user action is required. The Data Guard broker // always tries to resend the data. This error will be reported if the // problem persists. This error indicates there are some problems // with the network connection between broker managed databases. // Further network troubleshooting should be done to identify and // correct the actual problem. / 16636, 0000, "fast-start failover target standby in error state, cannot stop observer" // *Cause: A STOP OBSERVER operation could not be completed when fast-start // failover was enabled because the target standby database could // not participate in the STOP OBSERVER operation. // *Action: Additional information about this failure is recorded in the // Data Guard broker log file for the primary database. This // information helps to identify the reason why the target standby // database was unable to participate in the STOP OBSERVER operation. // If the problem can be corrected by the information in the broker // log file, retry the operation. Alternatively, fast-start failover // may be forcibly disabled by connecting to the primary database // and issuing the DISABLE FAST_START FAILOVER FORCE command from // the DGMGRL CLI. Once fast-start failover has been forcibly // disabled, the observer can be stopped regardless of the current // state of the target standby database. / 16637, 00000, "maximum number of Oracle error numbers for fast-start failover already reached" // *Cause: The broker could not enable any more Oracle error numbers for // initiating a fast-start failover. // *Action: Use the DGMGRL CLI SHOW FAST_START FAILOVER command to help // identify an Oracle error number that can be disabled before // attempting to enable an additional error number for initiating // a fast-start failover. / 16638, 00000, "could not obtain instance status" // *Cause: The broker could not determine whether the specified instance was // running. // *Action: See the next error message in the error stack for more detailed // information. If the situation described in the next error in the // stack can be corrected, do so; otherwise, contact Oracle Support // Services. / 16639, 0000, "specified instance inactive or currently unavailable" // *Cause: An attempt was made to perform an operation on an instance that // was not running or was unavailable. // *Action: Ensure that the instance specified in the operation is running // and then retry the operation. / 16640, 00000, "Oracle Clusterware was unable to shutdown database instances" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16641, 0000, "failure to acquire broker configuration metadata lock" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16642, 0000, "DB_UNIQUE_NAME mismatch" // *Cause: The expected DB_UNIQUE_NAME value did not match the actual // DB_UNIQUE_NAME value for the database that the broker contacted // using the connect identifier that was associated with that // database. // *Action: Verify that the connect identifier correctly connects to the // intended database. Verify that the name of the database the // broker expects to find by that connect identifier matches the // actual DB_UNIQUE_NAME for that database. / 16643, 0000, "unable to determine location of broker configuration files" // *Cause: The Data Guard broker was unable to determine the location of // its configuration files from the DG_BROKER_CONFIG_FILE[1|2] // initialization parameters. // *Action: Retry the operation and, if the error persists, contact Oracle // Support Services. / 16644, 0000, "apply instance not available" // *Cause: The broker operation could not finish, because it requires // a running apply instance for the standby database, and either // there was no such instance designated for the standby database // or the designated apply instance was not currently available. // *Action: Start the designated apply instance or wait until the broker // specifies an instance to be the apply instance and reissue the // command. / 16645, 0000, "startup of an instance interrupted current operation" // *Cause: The startup of an instance that is not part of the broker // configuration prevented the operation from completing. // *Action: Reissue the operation after the new instance has joined the // Data Guard configuration. / 16646, 0000, "fast-start failover is disabled" // *Cause: The operation was not allowed because fast-start failover was // disabled. // *Action: Enable fast-start failover and retry the operation. / 16647, 0000, "could not start more than one observer" // *Cause: The observer could not start because there was another observer // already observing the Data Guard configuration for which // fast-start failover may have been enabled. // *Action: Stop the running observer. Retry the operation. / 16648, 0000, "a new observer registered with identifier %s" // *Cause: The observer was registered with the Data Guard broker and will // begin observing the Data Guard configuration for conditions that // warrant doing a fast-start failover. // *Action: None / 16649, 0000, "possible failover to another database prevents this database from being opened" // *Cause: An attempt to open the primary database was made either after // a failover occurred, or when it was likely to have occurred as // the result of the primary being isolated from the fast-start // failover target standby database and from the fast-start failover // observer. // *Action: Check if a failover did occur. If fast-start failover is enabled, // and a failover did not occur, ensure that connectivity exists // between the primary database and either the observer or the // target standby database. Then, try opening the database again. / 16651, 0000, "requirements not met for enabling fast-start failover" // *Cause: The attempt to enable fast-start failover could not be completed // because one or more requirements were not met: // - The Data Guard configuration must be in either MaxAvailability // or MaxPerformance protection mode. // - The LogXptMode property for both the primary database and // the fast-start failover target standby database must be // set to SYNC if the configuration protection mode is set to // MaxAvailability mode. // - The LogXptMode property for both the primary database and // the fast-start failover target standby database must be // set to ASYNC if the configuration protection mode is set to // MaxPerformance mode. // - The primary database and the fast-start failover target standby // database must both have flashback enabled. // - No valid target standby database was specified in the primary // database FastStartFailoverTarget property prior to the attempt // to enable fast-start failover, and more than one standby // database exists in the Data Guard configuration. // *Action: Retry the command after correcting the issue: // - Set the Data Guard configuration to either MaxAvailability // or MaxPerformance protection mode. // - Ensure that the LogXptMode property for both the primary // database and the fast-start failover target standby database // are set to SYNC if the configuration protection mode is set to // MaxAvailability. // - Ensure that the LogXptMode property for both the primary // database and the fast-start failover target standby database // are set to ASYNC if the configuration protection mode is set to // MaxPerformance. // - Ensure that both the primary database and the fast-start failover // target standby database have flashback enabled. // - Set the primary database FastStartFailoverTarget property to // the DB_UNIQUE_NAME value of the desired target standby database // and the desired target standby database FastStartFailoverTarget // property to the DB_UNIQUE_NAME value of the primary database. / 16652, 0000, "fast-start failover target standby database is disabled" // *Cause: The command to enable or disable fast-start failover could not be // completed because Data Guard broker management of the fast-start // failover target standby database is currently disabled. // *Action: Enable broker management of the target standby database and // reissue the command. If an attempt was made to disable fast-start // failover when this error was reported, disable fast-start failover // forcibly using the DGMGRL DISABLE FAST_START FAILOVER FORCE // command. Consult the documentation for more information. / 16653, 0000, "failed to reinstate database" // *Cause: The Data Guard broker failed to reinstate the specified database // because the reinstatement could not be completed or the database // was already enabled. // *Action: Additional information about this failure is recorded in the // primary database or the specified database Data Guard // broker log files. This information is helpful in determining // how to proceed. / 16654, 0000, "fast-start failover is enabled" // *Cause: The attempted command was not allowed while fast-start failover // was enabled: // - The FastStartFailoverTarget property may not be modified. // - The LogXptMode property for either the primary database or the // fast-start failover target standby database may not be modified. // - The configuration's protection mode may not be modified. // - Neither the broker configuration nor the fast-start failover // target standby database may be disabled using the DGMGRL CLI // DISABLE command. // - Neither the broker configuration nor the fast-start failover // target standby database may be removed using the DGMGRL CLI // REMOVE command. // - The FAILOVER IMMEDIATE command is not allowed. // - The DG_BROKER_START initialization parameter may not be // set to FALSE. // *Action: Disable fast-start failover, using the FORCE option if required. // Then retry the attempted command. / 16655, 0000, "specified target standby database invalid" // *Cause: The attempted command was not allowed because fast-start failover // was enabled for this Data Guard configuration and the target // standby database specified in the command differs from the standby // database that was indicated by the FastStartFailoverTarget property // associated with the current primary database. // *Action: Retry the attempted command by specifying the standby database // that is indicated by the FastStartFailoverTarget property that is // associated with the current primary database. Alternatively, // fast-start failover may be disabled. Then retry the command // using the originally specified target standby database. / 16656, 0000, "Data Guard broker detected role change" // *Cause: The Data Guard broker detected a role during database startup or // health check. // *Action: Additional information about this failure is recorded in the // Data Guard broker log files, one for the primary database and // one for each standby database in the Data Guard configuration. This // information is helpful in determining how best to proceed from // this failure. / 16657, 0000, "reinstatement of database in progress" // *Cause: Reinstatement of this database was in progress. // *Action: None / 16658, 0000, "unobserved fast-start failover configuration" // *Cause: The fast-start failover configuration was currently unobserved // so failover was disallowed. // *Action: Make sure the observer is running and has connectivity to both // the primary and the target standby databases. Otherwise, disable // fast-start failover to perform a failover in the absence of the // observer process. / 16659, 0000, "failover operation in progress" // *Cause: A primary database that restarted contacted a standby database // that is being failed over to. // *Action: Shut down the primary database and wait for failover to complete // on the standby database. Once failover is complete, restart the // old primary database. If the failover occurred due to fast-start // failover, restarting the primary database after failover is // complete allows it to be automatically reinstated as a standby // database to the new primary database. / 16660, 0000, "fast-start failover operation attempted in absence of a broker configuration" // *Cause: An attempt was made to enable or disable fast-start failover when // connected to a standby database for which broker configuration // details are currently unavailable. For instance, the standby // database may currently require re-creation (or flashback // reinstantiation) before it may respond to broker client commands. // *Action: 1) An attempt to enable or disable (non-FORCE) fast-start failover // at this standby database will be rejected until such time that the // broker configuration details have been made available to that // standby database from the primary database. This normally occurs // when the standby database is successfully re-created or flashed // back, and then reenabled at the primary database. // 2) Use the FORCE option to override fast-start failover that // has been enabled at the standby database even when the broker // configuration details are currently unavailable to the standby // database. In this case, this status message is only a warning. // Note that fast-start failover is not formally disabled in the // broker configuration. The effect of this command issued under these // circumstances may or may not be permanent, depending upon when // the primary and standby databases regain full communication // between each other and if the state of fast-start failover has // been altered at the primary database in the meantime. / 16661, 00000, "the standby database needs to be reinstated" // *Cause: A role change has caused this database to require reinstatement. // *Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to // reinstate the database. Reinstate the database as soon as // possible, because the database will have to be re-created if // another role change occurs while it is in this state. / 16662, 0000, "network timeout when contacting a database" // *Cause: In response to the issued command, the Data Guard broker attempted // to contact a database in the Data Guard configuration. That // attempt failed because there was no response from that database // after the period of time specified by the CommunicationTimeout // configuration property. // *Action: Check the Data Guard broker log for the details of the failure. // Fix the problem and try the command again. / 16663, 0000, "event to control broker actions in the development environment" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used // to control the broker actions in the development environment. // DO NOT USE. // *Action: N/A, this is an Oracle internal event code. / 16664, 0000, "unable to receive the result from a database" // *Cause: During execution of a command, a database in the Data Guard // broker configuration failed to return a result. // *Action: Check Data Guard broker logs for the details of the failure. // Ensure network communication is working properly amongst the // members of the configuration. Fix any possible network problems // and reissue the command. / 16665, 0000, "timeout waiting for the result from a database" // *Cause: The Data Guard broker was forced to time out a network connection // to a remote database because: // - The network call to the remote database did not complete in // a timely manner. // - The remote database was unable to execute the command due to // an instance failure. // *Action: Check Data Guard broker logs for the details of the failure. // If the network call did not complete in a timely manner, increase // the CommunicationTimeout configuration property value and reissue // the command. / 16666, 00000, "unable to initiate fast-start failover on a standby database" // *Cause: The request to initiate a fast-start failover using // DBMS_DG.INITIATE_FS_FAILOVER was made to a standby database. // An application may only request that fast-start failover be // initiated by calling DBMS_DG.INITIATE_FS_FAILOVER on a primary // database. // *Action: Call DBMS_DG.INITIATE_FS_FAILOVER on the primary database. / 16667, 00000, "request Data Guard broker client to reissue command" // *Cause: The Data Guard broker operation required the same command be issued // again from the client. // *Action: If DGMGRL or Enterprise Manager has not already done so, // reissue the same command to the Data Guard broker manually. / 16668, 00000, "operation cannot be performed on the fast-start failover target standby database" // *Cause: The database specified for the operation was the fast-start // failover target standby database. // *Action: Retry the operation on a different database. Alternatively, disable // fast-start failover and retry the operation. / 16669, 00000, "instance cannot be opened because the Active Data Guard option is disabled" // *Cause: The attempt to open the instance failed because the Active Data // Guard option was not enabled and Redo Apply was either running // or was about to be started by the Data Guard broker. // *Action: Stop Redo Apply or set the database state to APPLY-OFF and then // open the database. / /16670, 00000, "file was opened with incorrect block size" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16671, 00000, "instance-specific property must be set uniquely for instances of an Oracle RAC database" // *Cause: An attempt was made to set an instance-specific property to the // same value for all instances of an Oracle RAC database for a // property whose value must be unique for each instance. // *Action: Use the EDIT INSTANCE command and specify the SID of each // instance whose instance-specific property value is to be changed. / / 16700 - 16899 reserved for Data Guard Broker RSM errors / 16700, 00000, "the standby database has diverged from the primary database" // *Cause: The primary database may have been flashed back or restored // from a backup set and then reopened with the RESETLOGS // option. // *Action: Re-create the standby database from the primary database or // flash back the standby database to the same point the primary // database had been flashed back to. / 16701, 00000, "Data Guard broker command failed" // *Cause: Command to modify or query the database failed. // *Action: Check the Data Guard broker log for the reason for the failure, // and reissue the command. / 16702, 00000, "Data Guard broker command warning" // *Cause: A command to modify or query the database resulted in a warning. // *Action: Check the Data Guard broker log for the warning and, if // necessary, reissue the command. / 16703, 00000, "cannot set property while the database is enabled" // *Cause: An attempt was made to change a database property while the // database was enabled. // *Action: Disable the database first, update the property and then, reenable // the database. / 16705, 00000, "internal error in Data guard broker" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16706, 00000, "Data Guard broker worker process not available" // *Cause: The Data Guard broker worker process was not available to // service the request. // *Action: Contact Oracle Support Services. / 16707, 00000, "the value of the property %s is invalid, valid values are %s" // *Cause: An invalid property value was specified while broker management of // the database was disabled. // *Action: Reset the property to a valid value. / 16708, 00000, "the state supplied to broker is invalid" // *Cause: The state name specified was invalid for the database. // *Action: Check the state name and reissue the request. / 16709, 00000, "standby archived log location settings conflict with database recovery area" // *Cause: The StandbyArchiveLocation or AlternateLocation property was set // to USE_DB_RECOVERY_FILE_DEST, but the initialization // parameter DB_RECOVERY_FILE_DEST did not specify a valid // destination. // *Action: Use a value other than USE_DB_RECOVERY_FILE_DEST for // StandbyArchiveLocation or AlternateLocation, or set up a valid // database recovery area by setting DB_RECOVERY_FILE_DEST to // a valid destination. / 16710, 00000, "snapshot standby database should be converted back to a physical standby database as soon as possible" // *Cause: A failover causes this snapshot standby database to enter a state // that requires it to be re-created if another failover occurs before // it is converted back to a physical standby database. // *Action: Reenable the snapshot standby database if it is disabled and // convert it back to a physical standby database as soon as possible // because the snapshot standby database will have to be re-created // if another failover occurs while it is in this state. / 16711, 00000, "resource manager service function not defined" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16712, 00000, "the resource handle is invalid" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16713, 00000, "the Data Guard broker command timed out" // *Cause: The Data Guard broker timed out the command. // *Action: Verify that the command is valid for the database and then // retry the command. / 16714, 0000, "the value of property %s is inconsistent with the database setting" // *Cause: The value of the specified configuration property was inconsistent // with database in-memory settings or server parameter file // settings. This may be caused by changing an initialization // parameter that corresponds to a configuration property. // *Action: Query the InconsistentProperties property on the database to // determine the which properties are set inconsistently. Reset the // properties to make them with the database settings. / 16715, 0000, "redo transport-related property %s of standby database \"%s\" is inconsistent" // *Cause: The value of the specified redo transport-related configuration // property of the given standby database was inconsistent // with the primary database redo transport service setting. This // may be caused by changing an initialization parameter that // corresponds to a configuration property. // *Action: Query the InconsistentLogXptProps property on the primary database // to determine which redo transport properties are set inconsistently // Reset the properties on the standby database to make them // consistent with the primary database redo transport settings. / 16716, 00000, "clearing parameter LOG_ARCHIVE_DEST failed" // *Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed. // *Action: Contact Oracle Support Services. / 16717, 00000, "clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed" // *Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed. // *Action: Contact Oracle Support Services. / 16718, 00000, "failed to locate database" // *Cause: The Data Guard broker was unable to locate the database in the // broker configuration. // *Action: Add the database to the broker configuration and then reissue // the command. / 16719, 00000, "unable to query V$ARCHIVE_DEST fixed view" // *Cause: The broker failed to query the V$ARCHIVE_DEST fixed view." // *Action: Test and clear the problem using SQL*Plus. / 16720, 00000, "no LOG_ARCHIVE_DEST_n initialization parameters available" // *Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use. // *Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters // so that broker can use them to set up the primary database // redo transport. / 16721, 00000, "unable to set LOG_ARCHIVE_DEST_n initialization parameters" // *Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n // initialization parameters. // *Action: Check the Data Guard broker log and Oracle alert logs // for more details. / 16722, 00000, "unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters" // *Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n // initialization parameters. // *Action: Check the Data Guard broker log and Oracle alert logs // for more details. / 16723, 00000, "setting AlternateLocation property conflicts with the redo transport setting" // *Cause: The standby database was not using standby redo logs, and // the redo transport service to the standby database is set to a // nonzero value for the ReopenSecs property and a value of zero for // the MaxFailure property. In this case, the redo transport service // will attempt to send redo data to the standby database // indefinitely and never switch to the alternate destination. // *Action: Any one of the following actions will solve the problem: // - add standby redo logs to the standby database. // - set ReopenSecs property to zero. // - set MaxFailure property to a nonzero value. // After performing one of the above actions, reset the standby // database AlternateLocation property. / 16724, 00000, "cannot resolve gap for one or more standby databases" // *Cause: The primary database could not resolve a gap request from one or // more standby databases. // *Action: To see which standby database has an unresolvable gap, check the // status of the primary database using either Enterprise Manager or // the DGMGRL CLI SHOW DATABASE command. Copy the missing archived // log files from either backups or from another database in the // configuration that has the files to the standby database that is // missing the files. / 16725, 00000, "the phase supplied to Data Guard broker worker process is invalid" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16726, 00000, "the external condition supplied to Data Guard broker worker process is invalid" // *Document: NO // *Cause: This was an internal error. // *Action: Contact Oracle Support Services. / 16727, 00000, "cannot close database" // *Cause: The Data Guard broker could not close the database. // *Action: Terminate any active sessions connected to the database and // then reissue the request. / 16728, 00000, "consistency check for property %s found %s error" // *Cause: The consistency check for the specified property failed // due to the error shown. // *Action: Check the error message and clear the error. / 16729, 00000, "validation of value for property %s found %s error" // *Cause: The property value validation failed due to the error shown. // *Action: Check the error message and clear the error. / 16730, 00000, "error executing DBMS_LOGSTDBY.SKIP_TXN procedure" // *Cause: Logical standby database package may not be installed. // *Action: Install logical standby database packages and reissue the request. / 16731, 00000, "error executing DBMS_LOGSTDBY.UNSKIP_TXN procedure" // *Cause: Logical standby database package may not be installed. // *Action: Install logical standby database packages and reissue the request. / 16732, 00000, "error executing DBMS_LOGSTDBY.SKIP procedure" // *Cause: Logical standby database package may not be installed. // *Action: Install logical standby database packages and reissue the request. / 16733, 00000, "error executing DBMS_LOGSTDBY.UNSKIP procedure" // *Cause: Logical standby database package may not be installed. // *Action: Install logical standby database packages and reissue the request. / 16734, 00000, "error executing DBMS_LOGSTDBY.SKIP_ERROR procedure" // *Cause: Logical standby database package may not be installed. // *Action: Install logical standby database packages and reissue the request. / 16735, 00000, "error executing DBMS_LOGSTDBY.UNSKIP_ERROR procedure" // *Cause: Logical standby database package may not be installed. // *Action: Install logical standby database packages and reissue the request. / 16736, 00000, "unable to find the destination entry of standby database \"%s\" in V$ARCHIVE_DEST" // *Cause: Either the standby destination was manually changed or deleted // outside of Data Guard broker, or no entry was available for // the Data Guard broker to use. // *Action: Clean up the destination setting, remove the unused settings, // and reset the redo transport service. / 16737, 00000, "the redo transport service for standby database \"%s\" has an error" // *Cause: A communication problem with the standby database caused the redo // transport to fail. // *Action: Query the LogXptStatus property to see the error message. // Check the Data Guard broker log and Oracle alert log for // more details. / 16738, 00000, "redo transport service for database \"%s\" is not running" // *Cause: The redo transport service for the specified standby database was // not running. // *Action: Check the Data Guard broker log and/or the alert log for more // details. If necessary, start the redo transport service for the // standby database. / 16739, 00000, "redo transport service for standby database \"%s\" is running" // *Cause: The redo transport service for the standby database was running. // *Action: Check the Data Guard broker log for more details. If // necessary, stop the redo transport service for the standby // database. / 16740, 00000, "redo transport service for standby database \"%s\" incorrectly set to ALTERNATE" // *Cause: The redo transport service to the standby database was set to // ALTERNATE when no other destination was set to alternate to this // destination. // *Action: Reenable the standby database or the entire configuration to allow // the configuration property settings to be propagated to the // initialization parameters. / 16741, 00000, "the destination parameter of standby database \"%s\" has incorrect syntax" // *Cause: The destination defined in the server parameter file of the // primary database had incorrect syntax and Data Guard broker // failed to update the destination when redo transport services // were enabled. // *Action: Fix the syntax error in the primary database server parameter // file or remove the entry from the server parameter file. Also, // check the values of the redo transport-related properties for // the specified standby database. / 16742, 00000, "the standby database \"%s\" has exhausted its quota" // *Cause: The standby database exhausted its quota for storing archived // redo logs. // *Action: Remove some archived redo logs from the standby database or // increase its quota. / 16743, 00000, "cannot determine status of redo transport service for standby database \"%s\"" // *Cause: The status of redo transport to the specified standby database // could not be determined. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16744, 00000, "the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full" // *Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full // and the Data Guard broker was not able to add a new DB_UNIQUE_NAME // to the list. // *Action: Remove some unused entries in the DG_CONFIG list, then reenable // the database. / 16745, 00000, "unable to add DB_UNIQUE_NAME \"%s\" into the DG_CONFIG list because it is full" // *Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full // and the Data Guard broker was not able to add the specified // DB_UNIQUE_NAME to the list. // *Action: Remove some unused entries in the DG_CONFIG list, then reenable // the database. / 16746, 00000, "Data Guard broker cannot mount the database" // *Cause: The Data Guard broker failed to mount the database." // *Action: Check the Data Guard broker log and Oracle alert log for // more details. / 16747, 00000, "logical standby database guard could not be turned on" // *Cause: The Data Guard broker could not turn on the logical standby // database guard. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16748, 00000, "Data Guard broker cannot open the primary database" // *Cause: The Data Guard broker failed to open the primary database" // the database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16749, 00000, "switchover to logical standby database failed" // *Cause: The Data Guard broker failed to switch a logical standby database // over to a primary database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16750, 00000, "failed to activate logical standby database" // *Cause: The Data Guard broker failed to activate a logical standby // database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16751, 00000, "failed to switchover to physical standby database" // *Cause: The Data Guard broker failed to switch a physical standby database // over to a primary database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16752, 00000, "Dump System State" // *Document: NO // *Cause: The Data Guard broker detected an internal problem and // request a system state dump. // *Action: N/A, this is an Oracle internal event code. / 16753, 00000, "Data Guard broker cannot open standby database" // *Cause: The Data Guard broker failed to open the standby database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16754, 00000, "failed to activate physical standby database" // *Cause: The Data Guard broker failed to activate the physical standby // database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16755, 00000, "failed to set initialization parameter" // *Cause: The Data Guard broker failed to set an initialization parameter // using either the ALTER SYSTEM SET or ALTER SYSTEM RESET command. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16756, 00000, "Dump Hang Analysis" // *Document: NO // *Cause: The Data Guard broker detected an internal problem and // request a hang analysis dump. // *Action: N/A, this is an Oracle internal event code. / 16757, 00000, "unable to get this property's value" // *Cause: The Data Guard broker failed to get the value for the specified // property, possibly because the specified property's value is // not available for the current database role. // *Action: If the specified property's value is not available for the // database's current role, please specify this property for a // database for which it is available. Otherwise, check the // Data Guard broker log for more details. / 16758, 00000, "the specified apply instance is not running" // *Cause: The Data Guard broker could not start apply services on the // specified instance because that instance was not running. // *Action: Start the instance and then retry the command. / 16759, 00000, "cannot start SQL Apply with initial SCN" // *Cause: The Data Guard broker failed to start SQL Apply with an initial // SCN. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16760, 00000, "cannot start SQL Apply" // *Cause: The Data Guard broker failed to start SQL Apply. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16761, 00000, "cannot stop SQL Apply" // *Cause: The Data Guard broker failed to stop SQL Apply. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16762, 00000, "invalid database state" // *Cause: Database was not in the intended state. // *Action: Determine the reason why the database is not running in the // intended state and reissue the command. / 16763, 00000, "redo transport service for a standby database is running" // *Cause: The redo transport service for a standby database was running. // *Action: For more details, check the status of the primary database using // either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. // If necessary, stop the redo transport service to the standby // database. / 16764, 00000, "redo transport service to a standby database is not running" // *Cause: The redo transport service to a standby database was not running. // *Action: For more details, check the status of the primary database using // either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. // If necessary, start the redo transport service to the standby // database. / 16765, 00000, "Redo Apply is running" // *Cause: Redo Apply was running when it should have been stopped. // *Action: If necessary, stop Redo Apply. / 16766, 00000, "Redo Apply is stopped" // *Cause: Redo Apply was stopped when it should have been running. // *Action: Check the alert log to see why Redo Apply terminated, correct any // problems that may exist, and restart Redo Apply by setting the // physical standby database state to APPLY-ON. / 16767, 00000, "SQL Apply is running" // *Cause: SQL Apply was running when it should have been stopped." // *Action: If necessary, stop SQL Apply. / 16768, 00000, "SQL Apply is stopped" // *Cause: SQL Apply was stopped when it should have been running." // *Action: Check the alert log to see why SQL Apply terminated, correct any // problems that may exist, and restart SQL Apply by setting the // logical standby database state to APPLY-ON. / 16769, 00000, "the physical standby database is open read-only" // *Cause: All instances in the physical standby database were put into // a read-only state instead of APPLY-OFF. // *Action: Issue the EDIT DATABASE SET STATE command to set the database // to the APPLY-OFF state. / 16770, 00000, "Redo Apply not started since physical standby database is opening" // *Cause: Redo Apply services could not be started on the physical standby // database because it was being opened. The Data Guard broker will // start Redo Apply services once the physical standby database has // been opened. // *Action: No action required. / 16771, 00000, "failover to a physical standby database failed" // *Cause: The Data Guard broker encountered errors when converting a physical // standby database to a primary database. // *Action: Check the Data Guard broker log and the Oracle alert log for more // details about the error. / 16772, 00000, "switchover to a standby database failed" // *Cause: The Data Guard broker encountered errors when switching over to // the specified standby database. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16773, 00000, "cannot start Redo Apply" // *Cause: The Data Guard broker failed to start Redo Apply. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. If the database is already open, the broker will not // start Redo Apply if the Active Data Guard option is not enabled. / 16774, 00000, "cannot stop Redo Apply" // *Cause: The Data Guard broker failed to stop Redo Apply. // *Action: Check the Data Guard broker log and Oracle alert log for more // details. / 16775, 00000, "target standby database in broker operation has potential data loss" // *Cause: The target standby database specified for the broker operation // did not have all the redo data from the primary database. // *Action: Confirm that the redo transport service on the primary database // is functioning correctly by checking its status using either // Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. // Reissue the broker command once all redo data is available on // the target standby database. / 16776, 00000, "health check of the redo transport service failed" // *Cause: The Data Guard broker could not complete the health check for the // redo transport service. // *Action: Check the Data Guard broker log and Oracle alert log for // more details. / 16777, 00000, "unable to find the destination entry of a standby database in V$ARCHIVE_DEST" // *Cause: Either a destination was manually deleted or no entry was available // for Data Guard. // *Action: Check the Data Guard broker log and the Oracle alert log for // more details. The redo transport service may need to be reset. / 16778, 00000, "redo transport error for one or more databases" // *Cause: The redo transport service was unable to send redo data to one // or more standby databases. // *Action: Check the Data Guard broker log and Oracle alert log for // more details. Query the LogXptStatus property to see the // errors. / 16779, 00000, "the destination parameter of a database is set incorrectly" // *Cause: The destination was defined in the LOG_ARCHIVE_DEST_n // server parameter file with incorrect syntax. // The Data Guard broker failed to update the destination when the // redo transport was turned on. // *Action: Check the Data Guard broker log to see which database has the // problem. Fix the syntax error in the server parameter file // or remove the entry from the server parameter file. // Check if the syntax of the redo transport-related properties // are correct. / 16780, 00000, "a database has exhausted its archived redo log storage quota" // *Cause: A database has exhausted its quota for storing archived redo logs. // *Action: Check the Data Guard broker log to see which database has the // problem. Remove some archived logs at the standby database // or increase its quota. / 16781, 00000, "cannot determine status of redo transport service for standby database" // *Cause: The status of redo transport to the specified standby database // could not be determined. // *Action: Check the Data Guard broker log and Oracle alert log for // more details. / 16782, 00000, "instance not open for read and write access" // *Cause: The database was mounted on an instance but not opened for read // and write access. // *Action: For more details, check the status of the database using either // Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. // If possible, open the instance manually. / 16783, 00000, "cannot resolve gap for database %s" // *Cause: The primary database could not resolve a gap request from the // specified standby database(s). // *Action: Copy the missing archived redo log files from either backups or // from another database in the configuration that has the files to // the standby database(s) missing the files. / 16784, 00000, "database name specified by Dependency property is incorrect" // *Cause: The database name, that should be the value of the // DB_UNIQUE_NAME initialization parameter, specified in the // Dependency property was incorrect. // *Action: Reset the Dependency property to the correct name of the database. / 16785, 00000, "the database is in NOARCHIVELOG mode" // *Cause: The database was in NOARCHIVELOG mode when it was either a // primary database or when it was a standby database that was // being switched over to be a primary database. // *Action: Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE // ARCHIVELOG command. / 16786, 00000, "unable to access Data Guard broker configuration files" // *Cause: The Data Guard broker configuration files did not exist or // or could not be accessed. // *Action: Check the Data Guard broker log for more details. / 16787, 0000, "event for Data Guard broker worker process testing" // *Document: NO // *Cause: This is an Oracle internal event code. This event is used for // verifying Data Guard broker worker process functionality. // DO NOT USE. // *Action: N/A, this is an Oracle internal event code. / 16788, 0000, "unable to set one or more database configuration property values" // *Cause: This situation occurred when the broker attempted to set database // configurable property values into the database by issuing // ALTER SYSTEM or ALTER DATABASE commands. // Typical causes of this error are: // - The values of redo transport-related properties contain syntax // syntax errors. // - The value of the LogArchiveTrace property was out of range. // *Action: Check the Data Guard broker log to see which property has the // problem and set the property to the correct value. / 16789, 0000, "standby redo logs not configured" // *Cause: Standby redo logs were not configured for the database. // *Action: Standby redo logs are required when the redo transport mode is // set to SYNC or ASYNC. Check the Data Guard documentation to see // how to create standby redo logs. / 16790, 0000, "the value of the configurable property is invalid" // *Cause: An invalid property value was entered, or a RESET was attempted // on a property for which no Broker default value exists. // *Action: Set the property to a correct value. / 16791, 0000, "unable to check the existence of the standby redo logs" // *Cause: The database may not be mounted, or the query of the V$STANDBY_LOG // fixed view failed. // *Action: Ensure the database is mounted and query the V$STANDBY_LOG fixed // view to see if the problem has been corrected, and retry the // operation. / 16792, 0000, "configurable property value is inconsistent with database setting" // *Cause: The values of one or more configurable properties were // inconsistent with database in-memory settings or server parameter // file settings. This may happen by directly altering initialization // parameters instead of editing configurable property values using // Data Guard broker. // *Action: Query the InconsistentProperties property on the database or check // the Data Guard broker log to find which properties are set // inconsistently. Reset these properties to make them consistent // with the database settings. Alternatively, enable the database // or the entire configuration to allow the configurable property // settings to be propagated to the initialization parameters. / 16793, 0000, "logical standby database guard is off" // *Cause: The logical standby database guard was turned off. // *Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on // and verify that Data Guard health check error or warning is // cleared. / 16794, 0000, "database guard is on for primary database" // *Cause: The database guard was turned on for the primary database. // *Action: Issue the ALTER DATABASE GUARD NONE command to turn off the guard // and verify that Data Guard health check error or warning is // cleared. / 16795, 0000, "the standby database needs to be re-created" // *Cause: A switchover or failover operation caused this database to // require re-creation. The database was marked for re-creation // because it was not a viable standby database for the new primary // database. // // Until this error status is resolved for this database, information // about this database and the broker configuration to which it // belongs is unavailable to a broker client that is connected to // this database. Therefore, all commands directed by that client to // this database cannot be completed. // // *Action: Re-create (or flash back) the standby database. Connect to the // primary database in the broker configuration and reenable broker // management of that database. Once enabled, it is possible // to connect to that standby database and manage it with the broker. // // Alternatively, many client commands that cannot be completed at // the standby database when in this error state can be completed // successfully when issued to the primary database. In this case, // simply reconnect to the primary database and retry the command. / 16796, 0000, "one or more properties could not be imported from the database" // *Cause: The broker was unable to import property values for the database // being added to the broker configuration. This error indicates: // - The Oracle Net service name specified in DGMGRL CREATE // CONFIGURATION or ADD DATABASE command was not one that provides // access to the database being added. // - There were no instances running for the database being added. // *Action: Remove the database from the configuration using the REMOVE // CONFIGURATION or REMOVE DATABASE command. Make sure that the // database to be added has at least one instance running and that the // Oracle Net service name provides access to the running instance. // Also check the broker log file for additional information. // Then, reissue the CREATE CONFIGURATION or ADD DATABASE command. / 16797, 0000, "database is not using a server parameter file" // *Cause: The database was not using a server parameter file or the broker // was unable to access the server parameter file. // *Action: Issue the CREATE SPFILE='..' FROM PFILE='...'" command to create // a server parameter file and then restart the database to use it. / 16798, 0000, "unable to complete recovery during failover" // *Cause: The physical standby database could not complete recovery // during failover. // *Action: Check the Data Guard broker log and the Oracle alert logs to see // more details on the reason for the failure. / 16799, 0000, "Redo Apply is not running" // *Cause: Either the Data Guard broker configuration indicates that Redo // Apply was turned off, or the recovery process, MRP0, was not // running. As a result, Redo Apply-related properties could not be // set. // *Action: Turn on Redo Apply through Data Guard broker and reissue the // command to set a Redo Apply-related property. / 16800, 00000, "redo transport service for a standby database incorrectly set to ALTERNATE" // *Cause: The redo transport service for a standby database was set to // ALTERNATE when no other destination is set to alternate to this // destination. // *Action: Reenable the standby database or the entire configuration to allow // the configuration property settings to be propagated to the // initialization parameters. / 16801, 0000, "redo transport-related property is inconsistent with database setting" // *Cause: The values of one or more redo transport-related configuration // properties were inconsistent with database in-memory settings or // server parameter file settings. This may happen by directly // altering initialization parameters instead of editing configurable // property values using Data Guard broker. // *Action: Query the InconsistentLogXptProps property on the primary database // or check the Data Guard broker log to find which properties are // set inconsistently. Reset these properties to make them consistent // with the database settings. Alternatively, enable the database // or the entire configuration to allow the configurable property // settings to be propagated to the initialization parameters. / 16802, 0000, "downgrading redo transport mode from SYNC disallowed" // *Cause: An attempt was made to downgrade the redo transport mode // of a standby database from SYNC to ASYNC when the configuration // was in Maximum Protection or Maximum Availability mode and the // primary database was a RAC database. This was not disallowed // even though there may have been other standby databases with redo // transport modes set to SYNC to support the protection mode. // *Action: Do one of the following if the redo transport mode of the standby // must be downgraded: // - Shut down all instances of the primary database and // restart one instance with the initialization parameter // CLUSTER_DATABASE set to FALSE. Downgrade the redo transport // mode of the standby database of interest. Then, shutdown the // instance, set the the CLUSTER_DATABASE initialization // parameter to TRUE, and restart all primary database instances. // - Downgrade the protection mode to Maximum Performance mode and // then, downgrade the redo transport mode of the standby database // of interest. Finally, upgrade the protection mode. This will // require a restart of all primary database instances if upgrading // to Maximum Protection mode. // Note that the above only works when there is at least one standby // database in the configuration that has its redo transport mode // set to SYNC. / 16803, 0000, "unable to query a database table or fixed view" // *Cause: Failed to query a database table or fixed view. The database // may not be opened or mounted. // *Action: Check the Data Guard broker log for more details. / 16804, 0000, "one or more configuration properties have invalid values" // *Cause: Data Guard broker health check detected that one or more // configuration properties in the broker configuration had // invalid values. The property values were changed while // broker management of the database was disabled. // *Action: Check Data Guard broker log for more details on which properties // have invalid values and reset them through the Data Guard broker. / 16805, 0000, "change of LogXptMode property violates overall protection mode" // *Cause: The broker disallowed the attempt to change the LogXptMode // configurable property for the standby database because, if allowed, // the overall protection mode for the configuration would have been // violated. // *Action: If the LogXptMode configuration property must be changed for the // specified standby database, first downgrade the overall // protection mode for the broker configuration. After that operation // has completed, the LogXptMode configuration property for the // standby database can be changed. / 16806, 0000, "supplemental logging is not turned on" // *Cause: Supplemental logging was not turned on while there was a logical // standby database in the configuration. This could happen either // on the primary database or on the logical standby database that // was being switched over to be the primary database. // *Action: Check the Data Guard broker log for more details. Issue the ALTER // DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) // COLUMNS to add supplemental logging. / 16807, 0000, "unable to change database protection mode" // *Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE // {PROTECTION | AVAILABILITY | PERFORMANCE} failed. // *Action: Check the Data Guard broker log and the Oracle log for more // information. / 16808, 0000, "primary database is not open" // *Cause: A prior attempt to open the primary database was disallowed // because the primary had shut itself down earlier after being // isolated from both the fast-start failover observer and the // target standby database for more than FastStartFailoverThreshold // seconds. It was assumed that a fast-start failover was underway. // Since that time, re-contact with either the observer or the target // standby database indicates that no such failover had actually // occurred. The primary database can now be opened. // *Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN // command. / 16809, 0000, "multiple warnings detected for the database" // *Cause: The broker detected multiple warnings for the database. // *Action: To get a detailed status report, check the status of the database // specified using either Enterprise Manager or the DGMGRL CLI SHOW // DATABASE command. / 16810, 0000, "multiple errors or warnings detected for the database" // *Cause: The broker detected multiple errors or warnings for the // database. // *Action: To get a detailed status report, check the status of the database // specified using either Enterprise Manager or the DGMGRL CLI SHOW // DATABASE command. / 16811, 0000, "apply instance not recorded by the Data Guard broker" // *Cause: The broker did not register an apply instance for a standby // database. // *Action: Reenable the standby database to clear the error. / 16812, 0000, "log apply service not running on apply instance recorded by the broker" // *Cause: Log apply services were not running on the instance the // Data Guard broker expected them to be running upon. // *Action: Reenable the standby database to clear the error. / 16813, 0000, "log apply service not running on apply instance %s recorded by the broker" // *Cause: Log apply services were not running on the instance the // Data Guard broker expected them to be running upon. // *Action: Reenable the standby database to clear the error. / 16814, 0000, "incorrect redo transport setting for AlternateLocation for standby database" // *Cause: The Data Guard broker detected an incorrect redo transport // setting for a standby database AlternateLocation property. // The incorrect setting could be one of the following: // - The AlternateLocation property was empty, but the redo // transport to the standby database had an ALTERNATE setting. // - The AlternateLocation property was not empty and the redo // transport to the standby database had no ALTERNATE setting. // - The AlternateLocation property did not match the ALTERNATE // setting in the redo transport. The mismatch may include // service string, directory specification of the alternate // location, or the DB_UNIQUE_NAME attribute. // - The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the // alternate location was not set to ALTERNATE. // - The flash recovery area was being used by the standby database // for archived logs, but the redo transport to the standby // database still had an ALTERNATE setting for the // AlternateLocation property. // Data Guard broker logs provide more details on which of // the above cases caused the error. // *Action: Reenable the primary database to clear the error. / 16815, 0000, "incorrect redo transport setting for AlternateLocation for standby database \"%s\"" // *Cause: The Data Guard broker detected an incorrect redo transport // setting for a standby database AlternateLocation property. // The incorrect setting could be one of the following: // - The AlternateLocation property was empty, but the redo // transport to the standby database had an ALTERNATE setting. // - The AlternateLocation property was not empty and the redo // transport to the standby database had no ALTERNATE setting. // - The AlternateLocation property did not match the ALTERNATE // setting in the redo transport. The mismatch may include // service string, directory specification of the alternate // location, or the DB_UNIQUE_NAME attribute. // - The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the // alternate location was not set to ALTERNATE. // - The flash recovery area was being used by the standby database // for archived logs, but the redo transport to the standby // database still had an ALTERNATE setting for the // AlternateLocation property. // Data Guard broker logs provide more details on which of // the above cases caused the error. // *Action: Reenable the primary database to clear the error. / 16816, 0000, "incorrect database role" // *Cause: The Data Guard broker detected that the specified database // had a different database role than that recorded in the Data // Guard broker configuration. This could be the result of a // failed switchover or failover operation, or a switchover or // failover operation performed with SQL*Plus. // *Action: Check the Data Guard broker documentation to see how to recover // from failed role change operations, or from role changes that // were performed using SQL*Plus for databases managed by Data Guard // broker. / 16817, 0000, "unsynchronized fast-start failover configuration" // *Cause: The fast-start failover target standby database was not // synchronized with the primary database. As a result, a fast-start // failover could not happen automatically in case of a primary // database failure. // *Action: Ensure that the fast-start failover target standby database is // running and that the primary database can ship redo data to it. // When the standby database has received all of the redo data from // the primary database, the primary and standby databases will then // be synchronized. The Data Guard configuration may then fail over // automatically to the standby database in the event of loss of the // primary database. / 16818, 0000, "fast-start failover suspended" // *Cause: The primary database was intentionally shutdown. As a result, // a fast-start failover could not happen automatically. // *Action: Start the primary database. This effectively restores the // ability to automatically perform a fast-start failover in the // event of a failure of the primary database. / 16819, 0000, "fast-start failover observer not started" // *Cause: The observer for fast-start failover was not started. As a // result, fast-start failover could not happen in the case of // a primary database failure. // *Action: Start the fast-start failover observer by using, for example, the // DGMGRL START OBSERVER command. / 16820, 0000, "fast-start failover observer is no longer observing this database" // *Cause: A previously started observer was no longer actively observing this // database. A significant amount of time elapsed since this // database last heard from the observer. // Possible reasons were: // - The host where the observer was running was not available. // - The network connection between the observer and this database // was not available. // - The observer process was terminated unexpectedly. // *Action: Check the reason why the observer cannot contact this database. // If the problem cannot be corrected, stop the current observer by // connecting to the Data Guard configuration and issue the DGMGRL // STOP OBSERVER command. Then, restart the observer on another // host. Finally, use the DGMGRL START OBSERVER command to start the // observer on the other host. / 16821, 0000, "logical standby database dictionary not yet loaded" // *Cause: The logical standby database had not loaded the dictionary. // This status was detected by the broker health check mechanism. // Alternatively, this status may be returned when attempting to // switch or fail over to a logical standby database that had not // yet loaded its dictionary. // *Action: Start SQL Apply on the logical standby database, if it is not // already running, and wait for it to reach the APPLYING state. / 16822, 0000, "new primary database not yet ready for standby database reinstatement" // *Cause: The new primary database, as a result of a logical standby // database failover operation, had not fully completed the failover // operation. An attempt to reinstate a disabled standby database // could not be completed until failover completed on the new // primary database. // *Action: Wait until the failover operation has completed on the new primary // database. Then retry the reinstate operation. / 16823, 0000, "redo transport mode is incompatible for current operation" // *Cause: The redo transport mode of this database was incompatible for this // broker operation. // *Action: Reset the LogXptMode database property for this database and // retry the broker operation. / 16824, 0000, "multiple warnings, including fast-start failover-related warnings, detected for the database" // *Cause: The broker detected multiple warnings for the database. // At least one of these warnings may have prevented fast-start // failover from occurring. // *Action: To get a detailed status report, check the status of the database // specified using either Enterprise Manager or the DGMGRL CLI SHOW // DATABASE command. / 16825, 0000, "multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database" // *Cause: The broker detected multiple errors or warnings for the // database. At least one of these errors or warnings // may have prevented a fast-start failover from occurring. // *Action: To get a detailed status report, check the status of the database // specified using either Enterprise Manager or the DGMGRL CLI SHOW // DATABASE command. / 16826, 0000, "apply service state is inconsistent with the DelayMins property" // *Cause: This warning was caused by one of the following reasons: // - The apply service was started without specifying the real-time // apply option or without the NODELAY option when the DelayMins // property was set to zero. // - The apply service was started with the real-time apply option or // with the NODELAY option when the DelayMins property was set to // a value greater than zero. // *Action: Reenable the standby database to allow the broker to restart // the apply service with the apply options that are consistent // with the specified value of the DelayMins property. / 16827, 0000, "Flashback Database is disabled" // *Cause: The broker detected that the Flashback Database feature was // disabled. With Flashback Database disabled, the broker would not // be able to: // - reinstate a database that required reinstatement. // - convert a physical standby database to a snapshot standby // database. // - convert a snapshot standby database to a physical standby // database. // Flashback Database may been disabled manually with the ALTER // DATABASE FLASHBACK DATABASE OFF command or automatically by the // database in the event of an error. // *Action: Check the database alert log to determine whether Flashback // Database was disabled due to errors and then correct the // problem. If Flashback Database had been manually disabled, // reenable Flashback Database with the ALTER DATABASE FLASHBACK // DATABASE ON command. If, after enabling Flashback Database, // the database still cannot be reinstated or converted, you must // re-create the database from a copy of the primary database. / 16828, 00000, "invalid value specified for REDO_TRANSPORT_USER initialization parameter" // *Cause: An invalid value was specified for the REDO_TRANSPORT_USER // initialization parameter. The length of the user name exceeded // 30 characters. // *Action: Check the documentation and specify a new value for the // REDO_TRANSPORT_USER initialization parameter. / 16829, 0000, "fast-start failover configuration is lagging" // *Cause: The fast-start failover target standby database was not // within the lag limit specified by the FastStartFailoverLagLimit // configuration property. As a result, a fast-start failover // could not happen in the event of a primary database failure. // *Action: Ensure that the fast-start failover target standby database is // running and applying redo data and that the primary database // is successfully trasmitting redo data. If this condition persists // consider raising the value of the FastStartFailoverLagLimit // configuration property. / 16830, 0000, "primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down" // *Cause: The primary database was isolated from both the observer and // target standby database for longer than the seconds specified // by the FastStartFailoverThreshold property. A fast-start failover // probably occurred. If the FastStartFailoverPmyShutdown // configuration property was set to TRUE, the broker will shut down // the primary database in this situation. // *Action: Ensure one instance of this database is running and the database // is mounted on that instance so that the broker may reinstate // the old primary database. / 16831, 00000, "operation disallowed on this standby database type" // *Cause: The Data Guard broker operation was disallowed on the standby // database type. // *Action: Check the documentation for the correct standby database type // and reissue the Data Guard broker command to another standby // database that is of the correct standby database type. / 16832, 0000, "user-configurable fast-start failover initiated: shutting down" // *Cause: The broker initiated a fast-start failover to the target standby // database because a user-configurable condition was detected on the // primary database. In addition, the broker shut down the primary // database. // *Action: Correct the problem on the old primary database that caused the // broker to initiate a fast-start failover, then reinstate the old // primary database. / / 16900 - 16949 Reserved for Data Guard Broker / / /============================================================================ / 16950 - 16999 Reserved for SQL Analyze / / Begin messages for SQL Analyze errors /============================================================================ / 16950, 00000, "Remote mapped cursors are not supported by this feature." // *Cause: This cursor is a remote mapped cursor which could not be processed locally. // *Action: Try to process this statement directly on the remote site. 16951, 00000, "Too many bind variables supplied for this SQL statement." // *Cause: Binding this SQL statement failed because too many bind variables were supplied. // *Action: Pass the correct number of bind variables. 16952, 00000, "Failed to bind this SQL statement." // *Cause: Binding this SQL statement failed. // *Action: Check if bind variables for that statement are properly specified. 16953, 00000, "Type of SQL statement not supported." // *Cause: This type of SQL statement could not be processed. // *Action: 16954, 00000, "SQL parse error." // *Cause: The specified SQL statement failed to be parsed. // *Action: Check if syntax is correct and ensure that this // statement can be parsed by the specified user name. 16955, 00000, "Unknown error during SQL analyze." // *Cause: The specified SQL statement failed to be analyzed. // *Action: This is an internal error, please contact Oracle support. 16956, 00000, "Only SELECT or DML statements are supported for test execute." // *Cause: The specified SQL statement cannot be tested for execute. // *Action: 16957, 00000, "SQL Analyze time limit interrupt" // *Cause: This is an internal error code used indicate that SQL analyze has // reached its time limit. // *Action: 16958, 00000, "DML statements running parallel are not supported for test execute." // *Cause: The specified DML statement cannot be tested for execute because part of it is running parallel. // *Action: 16959, 00000, "Statement type has been disabled for SQL Analyze" // *Cause: The system attempted to analyze a type of statement that // was disabled by the current feature. // *Action: Try a different feature capable of analyzing this statement type. 16960, 00000, "SQL Analyze could not reproduce the desired plan." // *Cause: SQL Analyze failed to reproduce a particular plan using an // outline. // *Action: Check the outline data. 16961, 00000, "SQL statement with SQL patch is ignored" // *Cause: SQL statements with SQL patches are not supported by SQL tuning advisor. // *Action: Check the SQL patch information. Rerun SQL repair advisor on // that SQL statement for a potential better SQL patch. / 16962, 00000, "SQL statement attempted to begin an autonomous transaction" // *Cause: The SQL statement being analyzed attempted to begin an // autonomous transaction, which is not supported. // *Action: Analyze another statement or remove the autonomous transaction // from the current statement. 16963, 00000, "The given user or schema is not supported by this feature." // *Cause: The SQL statement being analyzed had a parsing user or schema // which is not currently supported for SQL Analyze. // *Action: Analyze another statement. / / / 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 Services 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 file 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 that was 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 Services / 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 Services / 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 Services / 17511, 00000, "Event used internally for farm testing using RMAN seed database" // *Document: NO // *Cause: This event fixes db_name and file names in control file so that // files restored from RMAN seed database works in another view. // *Action: / 17512, 00000, "Block Verification Failed" // *Cause: Block Verification after a read operation on a database file // failed since the block is media corrupt. // *Action: check additional error messages in the trace file and call // Oracle Support Services / 17513, 00000, "dNFS package call failed" // *Cause: An attempt was made to call a dNFS package in a non-dNFS // environment // *Action: Make sure dNFS is enabled and the file can be accessed using dNFS. / 17514, 00000, "Access to clonedb bitmap file failed" // *Cause: Accessing the bitmap block file in clonedb environment has // encountered an error // *Action: check additional error messages in the trace file and call // Oracle Support Services / 17515, 00000, "Creation of clonedb failed using snapshot file %s" // *Cause: Creating a datafile in a clonedb environment failed. // *Action: Make sure the snapshot file passed to clonedb is not from another // clonedb instance and call Oracle Support Services for further assistance / 17516, 00000, "dNFS asynchronous I/O failure" // *Cause: The asynchronous I/O request failed due to storage server reboot. // *Action: Make sure the storage server does not reboot repeatedly during // database operations. / 17610, 00000, "file '%s' does not exist and no size specified" // *Cause: An attempt to create 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 / 17612, 00000, "Failed to discover Oracle Disk Manager library, return value %s" // *Cause: Discovery of the odm library by calling odm_discover() failed // *Action: Contact your storage vendor who has provided the ODM // library or call Oracle Support / 17613, 00000, "Failed to initialize Oracle Disk Manager library: %s" // *Cause: ODM initialization for the thread failed due to insufficient // previlige or memory. // *Action: Make sure there is enough system resources available for the // oracle process and it has access to the ODM library 17614, 00000, "Event to cause disk subsystem to require pre-allocation" // *Document: NO // *Cause: // *Action: 17615, 00000, "Event to disable pre-allocation algorithm during backup" // *Document: NO // *Cause: // *Action: 17616, 00000, "Event to disable pupulating V$RMAN_STATUS" // *Document: NO // *Cause: This event disables the dbsm_backup_restore functions // createRmanStatusRow, updateRmanStatusRow, and commitRmanStatusRow // (the functions will be no op). // In order to limit size of rows in V$RMAN_STATUS and to delete the // entire V$RMAN_STATUS use the named event KRBMRSR_LIMIT. If the // level of that event is 1, then size of the V$RMAN_STATUS view // will be zero so the above functions will signal ORA-19901. If the // level is bigger than 1, then it sets the maximum number of rows in // the V$RMAN_STATUS fixed view. // *Action: 17617, 00000, "Event to disable populating V$RMAN_OUTPUT" // *Document: NO // *Cause: This event disables the dbsm_backup_restore function // createRmanOutputRow (the function will be no op). // In order to limit size of rows in V$RMAN_OUTPUT and to delete the // entire V$RMAN_OUTPUT, use the named event KRBMROR_LIMIT. If the // level of that event is 1, then size of the V$RMAN_OUTPUT view will // be zero, so the function createRmanOutputRow will signal ORA-19901. // If the level is bigger than 1, then level*256 is maximum number of // the rows in the V$RMAN_OUTPUT fixed view. // *Action: / 17618, 00000, "Unable to update block 0 to version 10 format" // *Cause: An attempt was made to update block 0 to version 10 format. // *Action: Check additional error messages and call Oracle Support Services 17619, 00000, "max number of processes using I/O slaves in a instance reached" // *Cause: An attempt was made to start large number of processes // requiring I/O slaves. // *Action: There can be a maximum of 35 processes that can have I/O // slaves at any given time in a instance. / 17620, 00000, "failed to register the network adapter with Oracle Disk Manager library: %s" // *Cause: The ODM library returned an error while trying to register the // network adapter. // *Action: Make sure the network adapter name given in the // fileio_network_adapters is a valid name, and that the Oracle // user has the correct access privileges. 17621, 00000, "failed to register the memory with Oracle Disk Manager library" // *Cause: The ODM library returned an error while trying to register the // memory. // *Action: Contact the Oracle Disk Manager Library provider. / 17622, 00000, "failed to deregister the memory with Oracle Disk Manager library" // *Cause: The ODM library returned an error while trying to deregister the // memory. // *Action: Contact the Oracle Disk Manager Library provider 17623, 00000, "Event to enable compression debugs in backup and restore" // *Document: NO // *Cause: // *Action: 17624, 00000, "Failed to delete directory %s" // *Cause: The directory that was being deleted is still in use or the process // had insufficient permission to delete the directory. // *Action: check additional error messages. 17625, 00000, "Event to test delete directory" // *Document: NO // *Cause: For internal use only. // *Action: 17626, 00000, "ksfdcre: %s 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 17627, 00000, "%s" // *Cause: An error returned by OCI while sending/receiving message from // remote instance // *Action: Look at error message and take appropriate action or contact // Oracle Support Services for further assistance 17628, 00000, "Oracle error %s returned by remote Oracle server" // *Cause: Oracle server on the remote instance has returned an error. // *Action: Look at remote instance alert log/trace file for more information // and take appropriate action or contact Oracle Support Services // for further assistance 17629, 00000, "Cannot connect to the remote database server" // *Cause: Connecting to the remote server specified by database connect // string for netowrk file transfer failed. // *Action: Check additional error messages 17630, 00000, "Mismatch in the remote file protocol version client %s server %s" // *Cause: Cannot communicate with the remote database server as // there is a mismatch in the Oracle file protocol version. // *Action: Check additional error messages 17631, 00000, "dbname '%s' specified by remote server does not match the instance name '%s'" // *Cause: The dbname specified by the remote server is not intended // for this instance. // *Action: Check the dbname specified in the command of the remote instance // and look for further error messages. 17632, 0000, "file '%s' is a formatted ASM disk" // *Cause: An attempt to create a datafile on a device that was formatted // for ASM disk failed. // *Action: Check that the device specified is not an ASM disk. If you would // like to use the disk for datafiles, please clear the disk before // you retry the operation. 17633, 0000, "Operation not supported as one of the servers involved is not capable of performing the requested operation" // *Cause: An attempt was made to perform an operation involving // two Oracle servers where both servers did not have // the capability required for carrying out the operation. // It is likely that one of the servers needs a patch or an // upgrade to successfully participate in the operation. // *Action: Apply the required fix or update on the lower version // server. Contact Oracle Support Services for further // assistance. / / 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 / /============================================================================ / 18100 - 18199 Reserved for XMLQuery Update errors / / Begin messages for XQuery Update errors /============================================================================ / 18100, 00000, "XUST0001 - Updating expression in a wrong position" // *Cause: An updating expression was used in a position other than one of // the following: // - The topmost expression in the body of a query. // - The MODIFY clause of a TRANSFORM expression. // - The RETURN clause of a FLWOR expression. // - The RETURN clauses of a TYPESWITCH expression in which every // RETURN clause contains an updating expression, an empty // expression ( ), or a call to the fn:error function. // - The THEN and ELSE clauses of a conditional statement in which // both the then and else clauses contain either an updating // expression, an empty expression ( ), or a call to // the fn:error function. // - An operand of a comma expression in which each operand is // either an updating expression, an empty expression ( ), or // a call to the fn:error function. // - The content of a parenthesized expression. // - The body of a function declaration in which the keyword // UPDATING is specified. // *Action: None. / 18101, 00000, "XUST0002 - Non-updating expression in a wrong position" // *Cause: A non-updating expression other than an empty expression ( ) or a // call to the fn:error function was used in one of the following // positions: // - The MODIFY clause of a TRANSFORM expression. // - The top-level expression in the body of a function // declaration in which the keyword UPDATING is specified. // *Action: None. / 18102, 00000, "XUST0003 - Repeated revalidation declaration" // *Cause: Prolog contained more than one revalidation declaration. // *Action: None. / 18103, 00000, "XUTY0004 - Invalid attribute node in the insertion sequence" // *Cause: The insertion sequence of an INSERT expression contained an // attribute following a node that was not an attribute node. // *Action: None. / 18104, 00000, "XUTY0005 - Invalid target expression for INSERT" // *Cause: In an INSERT expression where INTO, AS FIRST INTO, or AS LAST INTO // was specified, the target expression returned a nonempty result // that did not consist of a single element or document node. // *Action: None. / 18105, 00000, "XUTY0006 - Invalid target expression for INSERT" // *Cause: In an INSERT expression where BEFORE or AFTER was specified, the // target expression returned a nonempty result that did not consist // element, text, comment, or processing instruction node. // *Action: None. / 18106, 00000, "XUTY0007 - Invalid target expression for DELETE" // *Cause: The target expression of a DELETE expression did not return a // sequence of zero or more nodes. // *Action: None. / 18107, 00000, "XUTY0008 - Invalid target expression for REPLACE" // *Cause: In a REPLACE expression, the target expression returned a nonempty // result that did not consist of a single element, attribute, text, // comment, or processing instruction node. // *Action: None. / 18108, 00000, "XUDY0009 - Invalid target expression for REPLACE" // *Cause: In a REPLACE expression where VALUE OF was not specified, the node // returned by the target expression did not have a parent. // *Action: None. / 18109, 00000, "XUTY0010 - Invalid replacement sequence for REPLACE" // *Cause: In a REPLACE expression where VALUE OF was not specified and // the target was an element, text, comment, or processing instruction // node, the replacement sequence did not consist of zero or more // element, text, comment, or processing instruction nodes. // *Action: None. / 18110, 00000, "XUTY0011 - Invalid replacement sequence for REPLACE" // *Cause: In a REPLACE expression where VALUE OF was not specified and // the target is an attribute node, the replacement sequence did not // consist of zero or more attribute nodes. // *Action: None. / 18111, 00000, "XUTY0012 - Invalid target expression for RENAME" // *Cause: In a RENAME expression, the target expression returned a nonempty // result that did not consist of a single element, attribute, or // processing instruction node. // *Action: None. / 18112, 00000, "XUTY0013 - Invalid COPY expression for TRANSFORM" // *Cause: In a TRANSFORM expression, a source expression in the copy clause // did not return a single node. // *Action: None. / 18113, 00000, "XUDY0014 - Modified node was not created by the COPY clause" // *Cause: In a TRANSFORM expression, the MODIFY clause modified a node that // was not created by the COPY clause. // *Action: None. / 18114, 00000, "XUDY0015 - Duplicate RENAME for the same target node" // *Cause: A node was the target of more than one RENAME expression within // the same query. // *Action: None. / 18115, 00000, "XUDY0016 - Duplicate REPLACE for the same target node" // *Cause: A node was the target of more than one REPLACE expression (without // VALUE OF being specified) within the same query. // *Action: None. / 18116, 00000, "XUDY0017 - Duplicate REPLACE for the same target node" // *Cause: A node was the target of more than one REPLACE VALUE OF expression // within the same query. // *Action: None. / 18117, 00000, "XUDY0018 - External not updating function returns an updated value" // *Cause: A function that was declared to be external but not updating // returned a nonempty pending update list. // *Action: None. / 18118, 00000, "XUDY0019 - External updating function returns an invalid value" // *Cause: A function that was declared to be both external and updating // returned a nonempty data model instance. // *Action: None. / 18119, 00000, "XUDY0020 - Deleted node has no parent" // *Cause: Node was deleted that had no parent before execution of the query // began. // *Action: None. / 18120, 00000, "XUDY0021 - The result XDM instance violates XDM constraints" // *Cause: XDM instance resulting from applying all the updates in a query // violated constraint specified in [XQuery/XPath Data Model (XDM)]. // In this case, none of the updates in the query were made effective. // *Action: None. / 18121, 00000, "XUTY0022 - Invalid attribute insertion into a document node" // *Cause: INSERT expression specified the insertion of an attribute node into // a document node. // *Action: None. / 18122, 00000, "XUDY0023 - Updating expression introduces a namespace conflict" // *Cause: An INSERT, REPLACE, or RENAME expression affected an element node // by introducing a new namespace binding that conflicted with one of // its existing namespace bindings. // *Action: None. / 18123, 00000, "XUDY0024 - Updating expression introduces a namespace conflict" // *Cause: Effect of a set of updating expressions introduced conflicting // namespace bindings into an element node. // *Action: None. / 18124, 00000, "XUDY0025 - Invalid QName for processing instruction RENAME" // *Cause: Target of a RENAME expression was a processing instruction node, // and the new name expression returned a QName with a nonempty // namespace prefix. // *Action: None. / 18125, 00000, "XUST0026 Revalidation mode %s is not supported" // *Cause: Revalidation declaration in a Prolog specified a revalidation mode // that is not supported by the current implementation. // *Action: None. / 18126, 00000, "XUDY0027 - Invalid target expression" // *Cause: Target expression of an INSERT, REPLACE, or RENAME expression // evaluated to an empty sequence. // *Action: None. / 18127, 00000, "XUST0028 - Updating function should not have a return type" // *Cause: Function declaration specified both UPDATING and a return type. // *Action: None. / 18128, 00000, "XUDY0029 - INSERT expression target node doesn't have a parent" // *Cause: In an INSERT expression where BEFORE or AFTER was specified, // a node returned by the target expression did not have a parent. // *Action: None. / 18129, 00000, "XUDY0030 - Invalid insertion of an attribute node" // *Cause: INSERT expression specified the insertion of an attribute node // before or after a child of a document node. // *Action: None. / 18130, 00000, "FOUP0001 - Invalid 'fn:put' first operand" // *Cause: The first operand of fn:put was not a node of a supported kind. // *Action: None. / 18131, 00000, "FOUP0002 - Invalid 'fn:put' second operand" // *Cause: The second operand of fn:put was not a valid lexical representation // of the xs:anyURI type. // *Action: None. / /============================================================================ / 18150 - 18199 RDBMS specific XQuery Update errors /============================================================================ / 18150, 00000, "SQL input value cannot be modified in updating expression" // *Cause: Updating expression was specified as top-level XMLQuery expression. // *Action: Use XQuery TRANSFORM expression to copy input value and modify it. / /============================================================================ / 18160 - 18199 RDBMS specific XQuery FullText errors /============================================================================ / 18160, 0000, "FTST0001 - FTMildNot operator not supported" // *Cause: An attempt was made to use the mild not option when the FTMildNot operator was not supported. An implementation that does not support the FTMildNot operator must raise a static error if a full-text query contains a mild not. // *Action: Do not use the FTMildNot full-text query operator. / 18161, 0000, "FTST0002 - FTUnaryNot operator not supported" // *Cause: An implementation that enforces one of the restrictions on FTUnaryNot must raise a static error if a full-text query does not obey the restriction. // *Action: Do not use the FTUnaryNot full-text query operator. / 18162, 0000, "FTST0003 - FTUnit and FTBigUnit not supported" // *Cause: An implementation that does not support one or more of the choices on FTUnit and FTBigUnit must raise a static error if a full-text query contains one of those choices. // *Action: Do not use the FTUnit or FTBigUnit option. / 18163, 0000, "FTST0004 - FTScope not supported" // *Cause: An implementation that does not support the FTScope operator must raise a static error if a full-text query contains a scope. // *Action: Do not use the FTScope full-text query operator. / 18164, 0000, "FTST0005 FTTimes not supported" // *Cause: An implementation that does not support the FTTimes operator must raise a static error if a full-text query contains a times. // *Action: Do not use the FTTimes full-text query operator. / 18165, 0000, "FTST0006 FTStopwordOption not supported" // *Cause: An implementation that restricts the use of FTStopwordOption must raise a static error if a full-text query contains a stop word option that does not meet the restriction. // *Action: Do not use the FTStopwordOption full-text query operator. / 18166, 0000, "FTST0007 FTIgnoreOption not supported" // *Cause: An implementation that restricts the use of FTIgnoreOption must raise a static error if a full-text query contains an ignore option that does not meet the restriction. // *Action: Do not use the FTIgnoreOption full-text query operator. / 18167, 0000, "FTST0008 stop word list not found" // *Cause: It is a static error if, during the static analysis phase, the query is found to contain a stop word option that refers to a stop word list that is not found in the statically known stop word lists. // *Action: Please make sure the stop word list exist. / 18168, 0000, "FTST0009 language option not supported" // *Cause: It may be a static error if, during the static analysis phase, the query is found to contain a language identifier in a language option that the implementation does not support. The implementation may choose not to raise this error and instead provide some other implementation-defined behavior. // *Action: Do not use the language full-text query option. / 18169, 0000, "FTST0010 FTOrder not succeeding FTWindow or FTDistance operator" // *Cause: It is a static error if, during the static analysis phase, an expression is found to use an FTOrder operator that does not appear directly succeeding an FTWindow or an FTDistance operator and the implementation enforces this restriction. // *Action: Do not use the FTOrder succeeding FTWindow or FTDistance full-text query operator. / 18170, 0000, "FTST0011 FTWindow and FTDistance restriction" // *Cause: An implementation may restrict the use of FTWindow and FTDistance to an FTOr that is either a single FTWords or a combination of FTWords involving only the operators && and ||. If it a static error if, during the static analysis phase, an expression is found that violates this restriction and the implementation enforces this restriction. // *Action: Follow FTWindow and FTDistance restriction. / 18171, 0000, "FTST0012 FTContent not supported" // *Cause: An implementation that does not support the FTContent operator must raise a static error if a full-text query contains one. // *Action: Do not use FTContent full-text query operator. / 18172, 0000, "FTST0013 more than one language encountered" // *Cause: It is a static error if, during the static analysis phase, an implementation that restricts the use of FTLanguageOption to a single language, encounters more than one distinct language option. // *Action: Do not use more than one language in FTLanguag full-text option. / 18173, 0000, "FTST0014 score computation restriction" // *Cause: An implementation may constrain the form of the expression used to compute scores. It is a static error if, during the static analysis phase, such an implementation encounters a scoring expression that does not meet the restriction. // *Action: / 18174, 0000, "FTST0015 FTCaseOption restriction" // *Cause: It is a static error if, during the static analysis phase, an implementation that restricts the choices of FTCaseOption encounters the "lowercase" or "uppercase" option. // *Action: / 18175, 0000, "FTDY0016 weights invalid" // *Cause: It is a dynamic error if an implementation that does not support negative weights encounters a weight expression that does not meet the restriction. // *Action: Do not use invalid weights value. / 18176, 0000, "FTDY0017 mild not selection containings StringExclude" // *Cause: It is a dynamic error if an implementation encounters a mild not selection, one of whose operands evaluates to an AllMatches that contains a StringExclude // *Action: / /============================================================================ / 19000 - 19099 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 %s does not match expected %s." // *Cause: The given XML document conformed to a different schema than expected. // *Action: Insert/Update only the XML documents that conform to that particular schema. 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. 19020, 00000, "invalid dereference of XMLType columns " // *Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table // *Action: You can only dereference the attributes of a base table XMLType column 19021, 00000, "General event for XML operations" // *Document: NO // *Cause: Disables functional evaluation of XML XPath operators on level 1 // *Action: N/A, this is an Oracle internal event code. 19022, 00000, "Unoptimized XML construct detected." // *Document: YES // *Cause: XMLOptimizationCheck is enabled and unrewritten XML construct was detected. This prevents execution of XML construct. // *Action: Make sure that XML construct is being optimized. See trace file for further information. Disable XMLOptimizationCheck if you want the unoptimized XML operation to be executed. 19023, 00000, "The first argument to UPDATEXML operator has to be an XMLTYPE" // *Cause: The first argument passed to the update value operator was not an XMLTYPE. // *Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE. 19024, 00000, "Cursor expression must be named" // *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. 19025, 00000, "EXTRACTVALUE returns value of only one node" // *Cause: Given XPath points to more than one node. // *Action: Rewrite the query so that exactly one node is returned. 19026, 00000, "EXTRACTVALUE can only retrieve value of leaf node" // *Cause: Given XPath does not point to a leaf node. // *Action: Rewrite the query so that a leaf node is returned. 19027, 00000, "Event for supressing query rewrite with XML operators" // *Document: NO // *Cause: This event turns off query rewrite for XML operators // *Action: N/A, this is an Oracle internal event code. 19028, 00000, "Invalid ADT parameter passed to toObject() function" // *Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type. // *Action: Pass an object of the correct type to toObject(). 19029, 00000, "Cannot convert the given XMLType to the required type " // *Cause: The passed in XMLType could not be convert to the required type // *Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types. 19030, 00000, "Method invalid for non-schema based XML Documents." // *Cause: The method can be invoked on only schema based xmltype objects. // *Action: Don't invoke the method for non schema based xmltype objects. 19031, 00000, "XML element or attribute %s does not match any in type %s.%s" // *Cause: The passed in XML tag does not match any in the object type // *Action: Pass a valid canonical XML that can map to the given object type 19032, 00000, "Expected XML tag %s got %s" // *Cause: When converting XML to object, a wrong tag name was present // *Action: Pass a valid canonical XML that can map to the given object type 19033, 00000, "schema specified in the XML document does not match the schema parameter" // *Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the 'schema' parameter. // *Action: Change the schema parameter to match the schema specified in the XML document. 19034, 00000, "Type not supported during schema generation" // *Cause: The object type contained a type that is not supported for schema generation. // *Action: Use a different type or do not generate a schema. 19035, 00000, "Invalid select item of the query in newContextFromHierarchy()" // *Cause: The query does not have a number select item followed by an XMLType select item only. // *Action: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType. 19036, 00000, "Invalid query result set in newContextFromHierarchy()" // *Cause: The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query. // *Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query. 19037, 00000, "XMLType result can not be a fragment" // *Cause: The select item of the query in newContextFromHierarchy() is an XML fragment. // *Action: Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment 19038, 00000, "Invalid opertions on query context" // *Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy(). // *Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy(). 19039, 00000, "Keyword %s reserved for future use" // *Cause: The keyword is reserved for future use as a builtin function. // *Action: Change the name mentioned above to a different one. 19040, 00000, "Element %s does not match expected %s." // *Cause: The given XML document had a different root element than expected. // *Action: Insert/Update only the XML documents that conform to that particular schema and element. 19041, 00000, "Comment data cannot contain two consecutive '-'s" // *Cause: The given comment string expression has two consecutive '-'s. // *Action: Modify comment string to eliminate one or both of the consevutive '-'s. 19042, 00000, "Enclosing tag %s cannot be xml in any case combination" // *Cause: The given enclosing tag matched 'xml' in some case combination // *Action: Modify the enclosing tag so that it is not xml in any case combination. 19043, 00000, "Multiply nested XMLROOT function disallowed" // *Cause: An XMLROOT function has an operand that is also an XMLROOT function. // *Action: Modify the query so that there are no multiply nested XMLROOT functions. 19044, 00000, "character length specified for XMLSerialize is too small." // *Cause : An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small. // *Action : Modify the query so that the character length specified is larger. 19045, 00000, "character set id specified for XMLSerialize not valid " // *Cause : An XMLSerialize function was called with an invalid value for the caracter set id. // *Action : Modify the query so that the character set id is valid. 19046, 00000, "Out-of-line table cannot be shared by two top-level tables (table '%s.%s' and the current table being created)." // *Cause : An attempt was made to share an out-of-line table between two top-level tables. // *Action : Use the existing top-level XML table. 19047, 00000, "Cannot specify storage for individual VARRAYS" // *Cause : An attempt was made to combine storage specification for a particular VARRAY with // STORE ALL VARRAYS clause. // *Action : Either specify storage for individual VARRAYs or use the STORE ALL VARRAYS clause. 19048, 00000, "Cannot specify VARRAY storage in tableProps" // *Cause : An attempt was made to store all varrays as tables or // LOBs in tableProps. // *Action: Do not specify varray store as tables or LOBs in tableProps. 19049, 00000, "Event for disabling fast path insert for SQL" // *Document: NO // *Cause: This event turns off fast path insert for XMLType tables. // *Action: Use if you want to turn off fast path insert for the XMLType table. 19050, 00000, "Event for adding order to SELECT from OCTs" // *Document: NO // *Cause: This event adds ordering by array_index when selecting from OCTs. // *Action: N/A, this is an Oracle internal event code. 19051, 00000, "Cannot use fast path insert for this XMLType table" // *Cause : Error while trying to insert into an XMLType table using fast path // insert. // *Action: Set event 19049 to disable fast path insert and try again. 19052, 00000, "Internal event" // *Document: NO // *Cause: // *Action: N/A, this is an Oracle internal event code. 19053, 00000, "Internal event" // *Document: NO // *Cause: // *Action: N/A, this is an Oracle internal event code. / / /============= gap for other XML error messages======== /============================================================================ / 19100 - 19159 Reserved for XMLQuery and XMLTable error messages / / Begin messages for XMLQuery and XMLTable errors /============================================================================ 19100, 00000, "PASSING or RETURNING keyword expected" // *Cause: The keyword PASSING or RETURNING was missing. // *Action: Specify the PASSING or RETURNING keyword. 19101, 00000, "CONTENT keyword expected" // *Cause: The keyword CONTENT was missing. // *Action: Specify the CONTENT keyword. 19102, 00000, "XQuery string literal expected" // *Cause: The string literal containing the XQuery expression was missing. // *Action: Specify the XQuery expression as a string literal. 19103, 00000, "VALUE keyword keyword" // *Cause: The keyword VALUE was missing. // *Action: Specify the VALUE keyword. 19104, 00000, "invalid XQueryX: missing attribute %s " // *Cause: The XQueryX expression was not assigned the expected attribute. // *Action: Specify a valid XQueryX. 19105, 00000, "invalid XQueryX: expected text node - got %s " // *Cause: The XQueryX expression did not contain a text node as expected. // *Action: Specify a valid XQueryX. 19106, 00000, "invalid XQueryX: expected %s - got %s " // *Cause: The XQueryX expression did not contain the node as expected. // *Action: Specify a valid XQueryX. 19107, 00000, "invalid XQueryX - unsupported construct - %s" // *Cause: The given XQuery expression contains an unsupported construct. // *Action: Specify a valid XQueryX. 19108, 00000, "WHITESPACE keyword expected" // *Cause: The keyword WHITESPACE was missing. // *Action: Specify the WHITESPACE keyword. 19109, 00000, "RETURNING keyword expected" // *Cause: The keyword RETURNING was missing. // *Action: Specify the RETURNING keyword. 19110, 00000, "unsupported XQuery expression" // *Cause: The program specified an XQuery expression that is not supported. // *Action: Rewrite the XQuery with a expression that is supported. 19111, 00000, "error during evaluation of the XQuery expression" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19112, 00000, "error raised during evaluation: %s" // *Cause: The error function was called during evaluation of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19113, 00000, "trace function called during evaluation: %s" // *Cause: The trace function was called during evaluation of the XQuery expression. // *Action: Check the log file for the trace message. 19114, 00000, "XPST0003 - error during parsing the XQuery expression: %s" // *Cause: An error occurred during the parsing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19115, 00000, "too many context items specified" // *Cause: More than one context item was specified as input to the XMLQuery function. // *Action: Specify a single context item for the XMLQuery function. 19116, 00000, "too many xmlspace declarations" // *Cause: The query prolog contained multiple xmlspace declarations. // *Action: Remove the duplicate xmlspace declarations. 19117, 00000, "XQST0070 - invalid redefinition of predefined namespace prefix '%s'" // *Cause: The given predefined namespace was being redefined in a namespace declaration. // *Action: Remove the namespace declaration that redefines the predefined namespace prefix. 19118, 00000, "XQST0066 - duplicate default namespace definition - %s" // *Cause: More than one default namespace declaration used the given namespace URI. // *Action: Remove the duplicate default namespace definition. 19119, 00000, "Event for turning on XMLQuery and XMLTable function" // *Document: NO // *Cause: This event turns on the XMLQuery and XMLTable functions // *Action: N/A, this is an Oracle internal event code. 19120, 00000, "Event for changing behavior of XMLQuery and XMLTable functions" // *Document: NO // *Cause: This event changes the behavior of the XMLQuery and XMLTable functions // *Action: N/A, this is an Oracle internal event code. 19121, 00000, "duplicate attribute definition - %s" // *Cause: More than one attribute with the same name. // *Action: Remove the duplicate attribute definition. 19122, 00000, "unsupported XQuery declaration" // *Cause: The program specified an XQuery declaration that is not supported. // *Action: Rewrite the XQuery with a declaration that is supported. 19123, 00000, "FORG0003: fn:zero-or-one() called with a sequence containing more than one item" // *Cause: sequence with more than one item was passed into fn:zero-or-one() function // *Action: correct input argument to fn:zero-or-one() function 19124, 00000, "FORG0004: fn:one-or-more() called with a sequence containing no items" // *Cause: sequence containing no items was passed into fn:one-or-more() function // *Action: correct input argument to fn:one-or-more() function 19125, 00000, "FORG0005: fn:exactly-one() called with a sequence containing zero or more than one item" // *Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function // *Action: correct input argument to fn:exactly-one() function 19126, 00000, "XQuery extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces" // *Cause: No expression was enclosed in curly braces for the extension expression or the pragma content was not recognized. // *Action: Correct inputs to extension expression. 19127, 00000, "XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19128, 00000, "XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19129, 00000, "XQST0069: A static error is raised if a Prolog contains more than one empty order declaration" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19130, 00000, "XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19131, 00000, "XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19132, 00000, "XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19133, 00000, "XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19134, 00000, "XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.)" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19135, 00000, "XQST0075: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19136, 00000, "XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19137, 00000, "XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19138, 00000, "The target type of a cast or castable expression must be an atomic type that is in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator \"?\"; otherwise a static error is raised" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19139, 00000, "XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19140, 00000, "XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19141, 00000, "XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19142, 00000, "FONC0001 = FONC0001: undefined context item" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19143, 00000, "XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19145, 00000, "XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19146, 00000, "XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19147, 00000, "XQST0089: It is a static error if a variable bound in a for clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames)" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19148, 00000, "XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19149, 00000, "XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19150, 00000, "XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19151, 00000, "XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 ... Mi ... M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19152, 00000, "FOCH0001 = FOCH0001: codepoint not valid" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19153, 00000, "FOCH0002: unsupported collation" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19154, 00000, "FOCH0003: unsupported normalization form" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19155, 00000, "FOCH0004: collation does not support collation units" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19156, 00000, "FODC0001: no context document" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19157, 00000, "FODC0002: error retrieving resource" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19158, 00000, "FODC0004: invalid argument to fn:collection()" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19159, 00000, "FODC0005: invalid argument to fn:doc" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. / /============= gap for other XQuery/XMLTable error messages======== /============================================================================ / 19160 - 19179 Reserved for XMLQuery syntax/static type errors / / Begin messages for XQuery syntax and static type errors /============================================================================ 19160, 00000, "XPST0003 - syntax error: invalid variable name %s" // *Cause: The given XQuery variable does not begin with the '$' sign // *Action: Fix the variable name to start with the "$" sign. 19161, 00000, "XPTY0004 - XQuery type mismatch: invalid argument type '%s' for function '%s'" // *Cause: The type of the argument that was passed to the given function was not valid. // *Action: Fix the argument to be of a type supported by the given function. 19162, 00000, "XPTY0004 - XQuery type mismatch: invalid argument types '%s', '%s' for function '%s'" // *Cause: The type of the arguments that were passed to the given function was not valid. // *Action: Fix the arguments to be of a type appropriate for the given function. 19163, 00000, "XPTY0004 - XQuery type mismatch: argument type mismatch: expected - '%s' got - '%s' for function '%s'" // *Cause: The type of the arguments that were passed to the given function was not valid. // *Action: Fix the arguments to be of a type appropriate for the given function. 19164, 00000, "XQST0085 - It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1]." // *Cause: There was a zero-length URI in namespace declaration. // *Action: Fix the namespace declaration. 19165, 00000, "FONS0003: no prefix defined for namespace" // *Cause: There was a zero-length URI in namespace declaration. // *Action: Fix the namespace declaration. 19166, 00000, "FONS0003: FONS0004: no namespace found for prefix" // *Cause: There was a zero-length URI in namespace declaration. // *Action: Fix the namespace declaration. 19167, 00000, "FONS0005: base uri not defined in the static context" // *Cause: There was a zero-length URI in namespace declaration. // *Action: Fix the namespace declaration. 19168, 00000, "FORG0002: invalid argument to fn:resolve-uri()" // *Cause: There was a zero-length URI in namespace declaration. // *Action: Fix the namespace declaration. 19169, 00000, "FORG0006: invalid argument type in '%s'" // *Cause: There was a zero-length URI in namespace declaration. // *Action: Fix the namespace declaration. 19170, 00000, "Event for turning on XML Query Cost-based Rewrite" // *Document: NO // *Cause: This event turns on the XML Query Cost-based Rewrite. // *Action: This is an Oracle internal event code. No action is required. 19171, 00000, "FORG0007: invalid argument to aggregate function" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19172, 00000, "FORG0008: both arguments to fn:dateTime have a specified timezone" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19173, 00000, "FORG0009: error in resolving a relative URI against a base URI in fn:resolve-uri" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19174, 00000, "FORX0001: invalid regular expression flags" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19175, 00000, "FORX0002: invalid regular expression" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19176, 00000, "FORX0003: regular expression matches zero-length string" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19177, 00000, "FORX0004: invalid replacement string" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19178, 00000, "FOTY0001: type error" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19179, 00000, "FOTY0011: Type error. Context item is not a node" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19180, 00000, "FOTY0012: argument node does not have a typed value" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19181, 00000, "FOTY0014: type exception" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19182, 00000, "FORT0001: invalid number of parameters" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19183, 00000, "FOTY0002: type definition not found" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19184, 00000, "FOTY0021: invalid node type" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19185, 00000, "FOAR0002: numeric operation overflow/unflow" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19186, 00000, "FOCA0001: input value too large for decimal" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19187, 00000, "FOCA0002: invalid lexical value" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19188, 00000, "FOCA0003: input value too large for integer" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19189, 00000, "FOCA0005: NaN supplied as float/double value" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19190, 00000, "FOER0000: Unidentified error" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19191, 00000, "FOAR0001: division by zero" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19192, 00000, "XQST0047: It is a static error if multiple module imports in the same Prolog specify the same target namespace" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19193, 00000, "XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19194, 00000, "XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string \"?>\"" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19195, 00000, "Invalid policy in ora:contains" // *Cause: An invalid policy was specified in ora:contains. // *Action: Rename the policy name, policy schema name, or do not specify any policy to pick up default policy. 19196, 00000, "XMLType table or view is not allowed with this form of fn:collection" // *Cause: The table or view specified in fn:collection was of XMLType. // *Action: XMLType table or view is not allowed in the form of fn:collection('oradb:/schema/table/ROW/column'). It has to be a relational table or view. 19197, 00000, "Column not found or invalid column type with this form of fn:collection" // *Cause: The column to be retrieved was not found or was not of XMLType. // *Action: The column to be retrieved in the form of fn:collection('oradb:/schema/table/ROW/column') or fn:collection('oradb:/schema/table/ROW[predicate]/column') has to be of XMLType. 19198, 00000, "Column not found or invalid column specified in the predicate with this form of fn:collection" // *Cause: The column specified in the predicate was not found or was not allowed. // *Action: The column specified in the predicate in the form of fn:collection('oradb:/schema/table/ROW[predicate]/column') cannot be of XMLType. / /============= gap for other syntax error messages ======== /============================================================================ / 19200 - 19219 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. 19206, 00000, "Invalid value for query or REF CURSOR parameter" // *Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR. // *Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR. 19207, 00000, "scalar parameter %s of XMLELEMENT cannot have an alias." // *Cause: The scalar parameter to XMLELEMENT has been qualified with an alias. // *Action: Remove the AS clause of the scalar element. 19208, 00000, "parameter %s of function %s must be aliased" // *Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression. // *Action: Specify an alias for the expression using the AS clause. 19209, 00000, "invalid or unsupported formatting argument" // *Cause: An invalid or unsupported formatting argument was supplied // *Action: Change the formatting argument to legal supported values 19210, 00000, "column '%s', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table '%s'" // *Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table. // *Action: Change the column specified to be a column in the table 19211, 00000, "column '%s', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type" // *Cause: The column specified using setKeyColumn() was a non-scalar type column. // *Action: Change the column specified to be a scalar column in the table 19212, 00000, "no key columns specified before call to DBMS_XMLSTORE.updateXML()" // *Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML. // *Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns / /============================================================================ / 19220 - 19299 Reserved for XQuery standard error messages / / Begin messages for XMLQuery specification defined errors /============================================================================ 19221, 00000, "XPST0001 - XQuery static context component %s not initialized" // *Cause: An unitialized static context component was encountered during the static analysis of the expression. // *Action: initialize the given static context. 19222, 00000, "XPDY0002 - XQuery dynamic context component %s not initialized" // *Cause: An unitialized dynamic context component was encountered during the evaluation of the expression. // *Action: Initialize the particular dynamic context component. /---------- /==== more syntax errors defined in error section 19160 and above /----------- 19223, 00000, "XPST0003 - syntax error in XQuery expression" // *Cause: The given XQuery expression contains syntax errors. // *Action: Fix the syntax error in the XQuery expression. 19224, 00000, "XPTY0004 - XQuery static type mismatch: expected - %s got - %s " // *Cause: The expression could not be used because it's static type is not appropriate for the context in which it was used. // *Action: Fix the expression to be of the required type or add appropriate cast functions around the expression. 19225, 00000, "XPST0005 - XQuery static type error: expected non empty type got empty sequence" // *Cause: The static type assigned to an expression other than the () expression must not be the empty type. // *Action: Fix the expression so it does not return empty sequences. 19226, 00000, "XPTY0006 - XQuery dynamic type mismatch: expected %s got %s" // *Cause: The expression could not be used because it's dynamic type did not match the required type as specified by XQuery sequencetype matching rules. // *Action: Fix the expression to return the expected type or use appropriate cast functions. 19227, 00000, "XPTY0007 - fn:data function is applied to a node (type (%s)) whose type annotation denotes a complex type with non-mixed complex content." // *Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content. // *Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content. 19228, 00000, "XPST0008 - undeclared identifier: prefix '%s' local-name '%s'" // *Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context. // *Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace. 19229, 00000, "XQST0009 - schema import not supported" // *Cause: A schema import was encountered in the query. // *Action: remove the schema import. 19230, 00000, "XPST0010 - unsupported axis %s " // *Cause: An unsupported axis was encountered in the given expression. // *Action: Remove the unsupported axis from the expression. 19231, 00000, "XPST0011 - " // *Cause: // *Action: 19232, 00000, "XQST0012 - imported schemas violate validity rules" // *Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification. // *Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique -- that is, the pool of definitions must not contain two or more schema components with the same name and target namespace. 19233, 00000, "XQST0013 - invalid pragma" // *Cause: A pragma was specified whose contents are invalid. // *Action: Specify the pragma with the correct contents. 19234, 00000, "XQST0014 - invalid or unsupported must-understand extension" // *Cause: The must-understand extension specified was either invalid or unsupported. // *Action: remove the unsupported must-understand extension or fix the error. 19235, 00000, "XQST0015 - unsupported must-understand extension" // *Cause: The XQuery flagger was enabled and the query contained a must-understand extension. // *Action: remove the unsupported must-understand extension. 19236, 00000, "XQST0016 - module declaration or import not supported" // *Cause: The given query had a module declaration or module import. // *Action: Remove the import module or module declaration. 19237, 00000, "XPST0017 - unable to resolve call to function - %s:%s" // *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. // *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. 19238, 00000, "XPTY0018 - It is a type error if the result of the last step in a path expression contains both nodes and atomic values" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19239, 00000, "XPTY0019 - It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value" // *Cause: The step expression returned a sequence containing an atomic value. // *Action: Fix the path expression to return only nodes. 19240, 00000, "XPTY0020 - context item must be node in an axis expression" // *Cause: The context item that was used in the axis epression is not a node. // *Action: Change the context item to be a node. 19241, 00000, "XPDY0021 - cast to type %s failed" // *Cause: The value inside a cast expression could not be cast to the required type. // *Action: Fix the input to the cast expression to be of a castable type. 19242, 00000, "XQST0022 - namespace declaration attribute must be a literal" // *Cause: The namespace declaration attribute was not a literal string. // *Action: Fix the namespace declaration to be a literal string. 19243, 00000, "XQTY0023 - invalid document node content in element constructor" // *Cause: The content sequence in an element constructor contained a document node. // *Action: Change the content of the element constructor so that it does not contain a document node. 19244, 00000, "XQTY0024 - invalid attribute node in element constructor" // *Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node. // *Action: Change the content sequence of the element constructor so that it does not contain the attribute node. 19245, 00000, "XQDY0025 - duplicate attribute name %s" // *Cause: The content sequence of the element constructor contained more than one attribute that had the same name. // *Action: Remove the duplicate attributes. 19246, 00000, "validation failed - element %s not found in in-scope element declarations" // *Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations. // *Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration. 19247, 00000, "XQDY0027 - validation error" // *Cause: An error was encountered during the validation of the expression. // *Action: Fix the validation error. 19248, 00000, "XQTY0028 - invalid node in document constructor" // *Cause: The content sequence in a document constructor contained either a document or an attribute node. // *Action: Fix the content so it does not contain any of the above node types. 19249, 00000, "XQDY0029 - value does not match facet of the target type" // *Cause: The input value to a cast expression did not satisfy the facets of the target type. // *Action: Fix the value to conform to the facets of the target type. 19250, 00000, "XQTY0030 - too many values to validate expression" // *Cause: The argument of a validate expression returned more than one element or document node. // *Action: Fix the argument of the validate expression to return a single element or document node. 19251, 00000, "XQST0031 - unsupported query version" // *Cause: The query version specified in the prolog was not supported. // *Action: Supply the version of the query that is supported. 19252, 00000, "XQST0032 - too many declarations for base URI" // *Cause: The query prolog contained multiple declarations for the base URI. // *Action: Remove the duplicate definitions for the base URI. 19253, 00000, "XQST0033 - too many declarations for namespace prefix %s" // *Cause: The query prolog contained multiple declarations for the same namespace prefix. // *Action: Remove the duplicate definitions for the namespace prefix. 19254, 00000, "XQST0034 - too many declarations for function %s" // *Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName. // *Action: Remove the duplicate function definitions. 19255, 00000, "XQST0035 - too many declarations of %s in imported schemas" // *Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope. // *Action: Fix the schema imports to remove the name conflict. 19256, 00000, "XQST0036 - missing type definitions in imported module" // *Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module. // *Action: Fix the module definintion to include the in-scope type definition. 19257, 00000, "XQST0037 - function or variable %s in module already defined" // *Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module. // *Action: Remove the conflicting declarations. 19258, 00000, "XQST0038 - unsupported or duplicate default collation specified" // *Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported. // *Action: Remove the duplicate definition or specify a supported collation. 19259, 00000, "XQST0039 - duplicate parameter name %s in function declaration" // *Cause: The function declaration contained more than one parameter with the same name. // *Action: Fix the function declaration to remove the duplicate parameters. 19260, 00000, "XQST0040 - invalid namespace node in element constructor" // *Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node. // *Action: Remove the namespace node in the element constructor. 19261, 00000, "XQDY0041 - non empty URI in QName" // *Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty. // *Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part. 19262, 00000, "XQST0042 - namespace constructor not inside an element constructor" // *Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor. // *Action: Fix the namespace constructor to be inside an element constructor. 19263, 00000, "XQST0043 - duplicate namespace prefix %s" // *Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix. // *Action: Remove the duplicate namespace definitions. 19264, 00000, "XQDY0044 - invalid namespace in attribute constructors" // *Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns). // *Action: Change the namespace for the computed attribute constructor. 19265, 00000, "XQST0045 - invalid or unknown prefix %s in function declaration" // *Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local. // *Action: Fix the function declaration to have the correct prefix. 19266, 00000, "XQST0046 - invalid URI" // *Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema. // *Action: Fix the URI. 19267, 00000, "module %s not found" // *Cause: The module with the given target URI could not be found. // *Action: Fix the prolog to import only available modules. 19268, 00000, "XQST0048 - namespace %s does not match target namespace %s" // *Cause: The module contained a function or variable whose namespace did not match the target namespace of the module. // *Action: Fix the namespace of the function or variable to match the target namespace of the module. 19269, 00000, "XQST0049 - variable %s defined multiple times" // *Cause: The module defined or imported the same variable multiple times. // *Action: Fix the import or the module definition to remove duplicate definitions. 19270, 00000, "XPDY0050 - treat failed - expected %s got %s" // *Cause: The type of the operand to the treat expression did not match the required type. // *Action: Fix the input operand to be of the correct type. 19271, 00000, "XPST0051 - invalid atomic type definition" // *Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type. // *Action: Use the correct atomic type name. 19272, 00000, "XQDY0052 - invalid atomic value in attribute or element constructor" // *Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string. // *Action: Fix the content to contain atomic values that can be cast to a string. 19273, 00000, "XQST0053 - empty string in namespace declaration" // *Cause: An empty string was used in a namespace declaration. // *Action: Fix the namespace declaration to have a non-empty string. 19274, 00000, "XQST0054 - variable initialization failed due to circularity" // *Cause: A circular definition was encountered when the variable was initialized. // *Action: Remove the circularity in the initialization. 19275, 00000, "XQST0055 - schema path %s not found in list of in-scope schema definitions" // *Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions. // *Action: Include the appropriate schema that can be used to resolve the ElementTest. 19276, 00000, "XPST0005 - XPath step specifies an invalid element/attribute name: (%s)" // *Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure. // *Action: Correct the element or attribute name as the name may be mis-spelled. 19277, 00000, "XPST0005 - XPath step specifies an item type matching no node: (%s)" // *Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure. // *Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure. 19278, 00000, "Invalid value: (%s) for type: (%s)" // *Cause: The value was invalid for the type. // *Action: Correct the value or change the type. 19279, 00000, "XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence" // *Cause: The XQuery sequence passed in had more than one item. // *Action: Correct the XQuery expression to return a single item sequence. 19280, 00000, "XQuery dynamic type mismatch: expected atomic value - got node" // *Cause: A node was passed in to the expression where an atomic value was expected. // *Action: Correct the XQuery expression to return an atomic value. 19281, 00000, "XQST0055 - It is a static error if a Prolog contains more than one copy-namespaces declaration" // *Cause: The query prolog contained multiple copy-namespaces declarations. // *Action: Remove the duplicate copy-namespaces declarations. 19282, 00000, "XQST0068 - It is a static error if a Prolog contains more than one xmlspace declaration" // *Cause: The query prolog contained multiple xmlspace declarations. // *Action: Remove the duplicate xmlspace declarations. 19283, 00000, "XQST0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation." // *Cause: The query contained a version declaration not supported by this implementation. // *Action: Change the version declaration to 1.0 which is the version supported by this implementation. 19284, 00000, "Encoding specification in version declaration not supported" // *Cause: The query contained an encoding specification. // *Action: Remove the encoding specification. 19285, 00000, "FODC0002 - error retrieving resource" // *Cause: The URI provided could not be resolved to a valid resource. // *Action: Provide a valid URI for a resource. 19286, 00000, "XPST0017 - unable to resolve call to function - %s" // *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. // *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. 19287, 00000, "XPST0017 - invalid number of arguments to function - %s:%s" // *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. // *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. 19288, 00000, "XPST0017 - invalid number of arguments to function - %s" // *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. // *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. 19289, 00000, "XQST0034 - function %s:%s declared or defined multiple times" // *Cause: Multiple functions declared or imported by a module had the same expanded QName and the same number of arguments. // *Action: Fix the function declaraction or definition to remove duplicates. 19290, 00000, "XQST0069 - more than one empty order declaration declared in the prolog" // *Cause: A prolog had more than one empty order declaration. // *Action: Fix the prolog to have just one empty order declaration. 19291, 00000, "XPST0081 - specified QName cannot be expanded into a namespace URI" // *Cause: The namespace prefix of the QName could not be expanded into a namespace URI by using the statically known namespaces. // *Action: Use a namespace prefix that can be resolved into a namespace URI from the statically known namespaces. 19292, 00000, "XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19293, 00000, "XQST0058: It is a static error if multiple schema imports specify the same target namespace" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19294, 00000, "XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19295, 00000, "XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI)" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19296, 00000, "XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19297, 00000, "XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to \"XML\" (in any combination of upper and lower case" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19298, 00000, "XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. 19299, 00000, "XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration" // *Cause: An error occurred during the processing of the XQuery expression. // *Action: Check the detailed error message for the possible causes. / /============================================================================ / 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 / / 19361 - 19370 = reserved for analyze parse and execution errors / 19361, 00000, "ONLINE option not allowed with this type of index" // *Cause: The ONLINE option was specified to validate the structure of a // system-generated metadata index // *Action: The ONLINE option can not be used with system-generated metadata // indexes such as an LOB index, an IOT Top index, an Index on // Clusters etc., Run query without using the ONLINE option. / /============================================== /= 13750 - 13799 reserved for SqlSet = /= 19371 - 19390 reserved for sqlset/sqltune = /============================================== / 19371, 00000, "invalid update option" // *Cause: The user attempted to call load_sqlset with an update option // that is different than REPLACE and ACCUMULATE. // *Action: Adjust the update option and retry the operation. / 19372, 00000, "invalid update condition" // *Cause: The user attempted to call load_sqlset with an invalid update // condition. // *Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) // and retry the operation. / 19373, 00000, "invalid staging table or tablespace" // *Cause: The user attempted to create a staging table and specified an // invalid staging table (or one that already exists) or tablespace // *Action: Check the arguments and try again. / 19374, 00000, "invalid staging table" // *Cause: The user specified an invalid staging table to one of the // pack, unpack, or remap stgtab routines, or the user does // not have the correct privileges on the staging table // *Action: Provide a correct staging table or grant the // appropriate privileges / 19375, 00000, "no CREATE TABLE privilege on schema \"%s\"" // *Cause: The user tried to create a staging table when he is missing the // CREATE TABLE privilege on the specified schema. // *Action: Grant the privilege to the user and retry // / 19376, 00000, "no privileges on tablespace provided or tablespace is offline" // *Cause: The user tried to create a staging table on a tablespace on which he // does not have any space allocated, or it is offline // *Action: Allocate space on the tablespace, bring it online, and retry / 19377, 00000, "no \"SQL Tuning Set\" with name like \"%s\" exists for owner like \"%s\"" // *Cause: The user specified a filter to a pack/unpack function for the SQL // Tuning Set that targets no STS in the SYS schema or the staging // table, respectively // *Action: Provide a different filter after checking the state of the system / 19378, 00000, "invalid mode" // *Cause: The user specified an invalid mode argument to the capture // function. // *Action: Provide a mode argument that was defined in the dbmssqlt file / 19379, 00000, "invalid time_limit or repeat_interval" // *Cause: The user specified a NULL value for either the time_limit or the // repeat_interval, or a repeat_interval that is greater than the // time_limit // *Action: Provide a non-null value and make sure time_limit >= repeat_interval / 19380, 00000, "invalid plan filter" // *Cause: The user specified an invalid filter for the plan when calling the // select_sqlset table function. // *Action: Adjust the the filter to be one of the following values // and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, // MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED // LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED. / 19381, 00000, "cannot create staging table in SYS schema" // *Cause: The user attempted to create a staging table in the sys schema // *Action: Create the table in another schema. / 19382, 00000, "timeout encountered during sqltune test-execute" // *Document: NO // *Cause: This is an internal error code used internally to signal a // timeout during a SQL Tune test-execute operation / 19383, 00000, "all plans encountered errors during sqltune test-execute" // *Document: NO // *Cause: This is an internal error code used to signify that // a sqltune test-execute operation in RESILIENT mode ended with // all plans encountering errors. // *Action: Examine the errors stored in the plans one by one. / 19384, 00000, "cannot pack into staging table from previous version" // *Cause: An attempt was made to perform a pack operation on a staging // table from a previous version. // *Action: Create a staging table in the current version and retry the // operation. / 19385, 00000, "staging table is empty" // *Cause: An attempt was made to perform an operation on an empty staging // table. // *Action: Check the staging table to make sure that it has rows. / 19386, 00000, "target object already exists for tuning task \"%s\"" // *Cause: An attempt was made to set a target object for a tuning task // when one had already been set. // *Action: Create a new task if another target object is needed. / 19387, 00000, "\"SQL Tuning Set\" \"%s\" belongs to another tuning task" // *Cause: The user attempted to tune a task-managed SQL Tuning Set belonging // to one task within the scope of another task. // *Action: Check the SQL Tuning Set and retry the operation. / 19388, 00000, "operation not supported for \"SQL Tuning Set\" type" // *Cause: The attempted operation was unsupported for the type // of the given SQL Tuning Set. // *Action: Check the SQL Tuning Set and retry the operation. / 19389, 00000, "LOB types are not supported for SQL binds" // *Cause: A LOB type was provided in a SQL bind list. // *Action: Replace the LOB binds with legal bind types or try another // SQL. / 19390, 00000, "The profile type is not valid" // *Cause: The profile type is not valid. // *Action: Check the available profile types. / /========================================================================== / 19391 - 19399 are reserved for autonfs. /========================================================================== / 19391, 00000, "autonfs - kgodm tracing " // *Document: NO // *Cause: This is an Oracle internal event code. This event is bitmask // used to control trace output of AutoNFS kgodm . DO // NOT USE. // *Action: N/A, this is an Oracle internal event code. / 19392, 00000, "autonfs - kgnfs tracing " // *Document: NO // *Cause: This is an Oracle internal event code. This event is bitmask // used to control trace output of AutoNFS kgnfs . DO // NOT USE. // *Action: N/A, this is an Oracle internal event code. / 19393, 00000, "autonfs - skgnfs tracing " // *Document: NO // *Cause: This is an Oracle internal event code. This event is bitmask // used to control trace output of AutoNFS skgnfs . DO // NOT USE. // *Action: N/A, this is an Oracle internal event code. / /========================================================================== / 19400 - 19499 are reserved for KOT. /========================================================================== / 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. / / Copyright (c) 1995, 2006, Oracle Corporation. All rights reserved. / / NAME / e19500.msg / DESCRIPTION / Error messages Reserved for Recovery Manager (RMAN). / NOTES / All errors in this file are reserved for Recovery Manager (RMAN). Please / do not take them for other purpose. / / Error numbers / / 19500 - 19998 Reserved for Server Managed Recovery / 19500-19524: KGF*, KSF* / 19525-19539: More db file errors / 19540-19549: KRB events / 19550-19699: KRB*, except KRBI / 19700-19719: KRBI / 19720-19739: Transportable Tablespace kernel errors (KCP) / 19740-19749: More KRBI errors / 19750-19799: Block change tracking / 19800-19829: Recovery Area Errors / 19830-19835: SQL Engine Errors / *** 19836-19850: General-use range - first free message=19839 / 19851-19859: Auxiliary instance / 19860-19870: Additional KRBR Messages / 19871-19879: Reserved for testing events / 19880-19889: Unused block Compression / 19899-19912: Recovery thru resetlogs project / 19913-19920: Encrypted backups / 19921-19925: KRB* errors / 19926-19929: Transport database errors / 19930-19940: More KRB* errors / 19941-19950: cross platform transpotable tablespace (xtts) / 19951-19960: DBNEWID / / MODIFIED / pkapil 03/03/11 - Backport pkapil_bug-10409625 from main / fsanchez 02/23/11 - Backport fsanchez_bug-11074876 from main / pkapil 02/09/11 - Backport pkapil_bug-9234538 from main / fsanchez 03/30/10 - do not allow a backup controfile from rman's / duplicate to open the database / fsanchez 03/04/10 - lrg 4521736, add 19837 / molagapp 01/07/10 - add 19824, 19825 event / fsanchez 01/25/10 - bug 9230148 / molagapp 12/26/09 - add 19823 event to adjust space pressure percentage / molagapp 12/26/09 - add 19822 event to adjust FRA monitoring interval / mgirkar 12/24/09 - Add more text to 19527 error message / fsanchez 08/20/09 - bug 8689421 / molagapp 06/03/09 - remove flash reference / molagapp 02/24/09 - bug 6489610 / swerthei 02/13/09 - bug 8246019 - allow compressed backup of encrypted ts / fsanchez 08/18/08 - bug 6623413 / fsanchez 08/10/10 - lzo support / molagapp 09/10/08 - fix 19932 / fsanchez 08/18/08 - bug 6623413 / yuli 08/25/08 - add 19972 and 19975 / yuli 06/18/08 - deprecate ALTER DATABASE RECOVER STANDBY / DATAFILE|TABLESPACE / fsanchez 05/23/08 - add 19961 / fsanchez 05/20/08 - bug 1690875 / molagapp 05/12/08 - add 19943 / jjlee 05/08/08 - add 19820 and 19821 / yuli 04/29/08 - multi-instance standby switchover / ssamaran 02/19/08 - add 19780 - active data guard not enabled / yuli 02/09/08 - add 19899 / shsong 12/17/07 - add 19963 / fsanchez 10/16/06 - reword 19870 / swerthei 08/11/06 - remove 19872 / fsanchez 08/25/06 - add 19882, modify cause/action for unused block opt. / molagapp 08/14/06 - add 19546 event / swerthei 01/05/06 - multi-section backup messages / fsanchez 03/08/06 - reserve 19541 for event / swerthei 10/07/05 - sbt-allocated buffers / fsanchez 01/03/06 - improve message readability / fsanchez 12/08/05 - add 19941, 19942 / molagapp 10/03/05 - add 19529 / molagapp 08/23/05 - add 19819 / molagapp 08/22/05 - molagapp_dbhygiene_rman_3 / molagapp 08/16/05 - Creation / /19500 - 19524: Reserved for KGF*, KSF* / / 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\", block number %s (block size=%s)" // *Cause: read error on input file // *Action: check the file 19502, 00000, "write error on file \"%s\", block number %s (block size=%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\" (block size=%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. 19512, 00000, "file search failed" // *Cause: Recovery manager or Oracle Server attempted to discover files // that matched the specified pattern but failed. // *Action: Check errors on the error stack for an explanation // why the search for files could not be successfully executed. 19513, 00000, "failed to identify sequential file" // *Cause: Unable to identify the sequential file. // *Action: Check additional messages, and check if the file exists on media. / /19514 reserved for skgfq-allocated buffer disabling event / /19525 - 19547: More db file errors / 19525, 00000, "tempfile for the clone database must be renamed" // *Cause: Opening a clone database failed because Oracle server forces the // tempfile to be renamed, in order to avoid overwriting // the primary tempfile. // *Action Rename the tempfiles manually or automatically by using // the DB_FILE_NAME_CONVERT initialization parameter. 19526, 00000, "only one location allowed for parameter %s" // *Cause: A list of default locations was provided in an Oracle-managed // files parameter. // *Action Edit the parameter to include a single location. 19527, 00000, "physical standby redo log must be renamed" // *Cause: An attempt was made to clear redo log at a physical standby // database. Clearing an OMF redo log will not work unless // DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or // DB_RECOVERY_FILE_DEST parameter is specified. Clearing a non-OMF // (or user-defined) redo log file will not work unless the // LOG_FILE_NAME_CONVERT initialization parameter is // set. // *Action Set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or // DB_RECOVERY_FILE_DEST parameter for OMF redo log files and // re-issue the operation that attempted to clear redo log. Set // LOG_FILE_NAME_CONVERT parameter for non-OMF redo log files and // re-issue the operation that attempted to clear redo log. 19528, 00000, "redo logs being cleared may need access to files" // *Cause: The redo logs are being cleared. This procedure may need the // files this operation is being applied to. // *Action: Wait for the redo logs to be cleared. 19529, 00000, "Pattern %s in initialization parameter %s has an Oracle Managed Files file name." // *Cause: An attempt was made to convert a database file name to an Oracle // Managed Files file name using DB_FILE_NAME_CONVERT or // LOG_FILE_NAME_CONVERT initialization parameter. This was not a // valid operation. // *Action: Retry the operation with a pattern template instead of a full // Oracle Managed Files file name. / // Reserved errors for KRB events - do not document here the events. // 19540 // 19541 // 19542 - crash event // Level Description // ----- ----------- // 1 crash process before updating file header for incr restore // 2 crash process before cataloging file for incr restore // 19544 // 19545 // 19546 // 19547 // 19548 // 19549 / / / 19550-19699: KRB*, except KRBI / 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 name" // *Cause: An invalid name of device limit was specified in a call to // DBMS_BACKUP_RESTORE.SETLIMIT. // *Action: Use one of the device limit names described in dbmsbkrs.sql 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 archived log, control file, 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, its header was not // recognized as a valid file header for a file of the indicated // type (datafile, 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 control file" // *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 control file. // *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 file name must be specified" // *Cause: This type of copy or restore requires an output file name. // *Action: Specify an output file name 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 file name should be taken from // the control file. However, the control file 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 control file cannot // be used for restoration. // *Action: Either specify an output file name or issue a SQL RENAME command // to enter a valid name for this file in the control file. 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, "archived log record for %s not found" // *Cause: No archived log record corresponding to input file could be // found in the control file. // *Action: Specify a valid archived log 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, "archived log file header validation for %s failed" // *Cause: Archived log file header is corrupt and could not be validated. // *Action: Provide a valid archived log 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 for MAXPIECESIZE for this channel // is not enough to hold the backup set control data. // *Action: Allocate a channel specifying a larget valule for MAXPIECESIZE // 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 control file" // *Cause: The control file that is the source for a backup or copy operation // is not a snapshot or backup control file. // *Action: Specify the name of a snapshot or backup control file. 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, "backup aborted because job time exceeded duration time" // *Cause: You tried to backup with duration option and the time provided // was not sufficient to complete the backup. // *Action: Adjust the duration time and re-run the command. Or run the backup // command without duration option. 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, "control file already included as %s" // *Cause: The control file is already specified for inclusion in this backup // or restore conversation. A backup or restore conversation may // process only a single instance of the control file. // *Action: No action required - the conversation is still active, and // more files can be specified. 19595, 00000, "archived log %s already included in backup conversation" // *Cause: The indicated archived log 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, "SPFILE already included" // *Cause: The SPFILE is already specified for inclusion in this backup // or restore conversation. A backup or restore conversation may // process only a single instance of the SPFILE. // *Action: No action required - the conversation is still active, and // more files can be specified. 19597, 00000, "file %s block size %s does not match set block size 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, "can not backup SPFILE because the instance was not started with SPFILE" // *Cause: A backup command requested a backup of the SPFILE, but no SPFILE // was used to startup the instance. // *Action: Create an SPFILE and re-start the instance using the SPFILE. 19599, 00000, "block number %s is corrupt in %s %s" // *Cause: A corrupt block was found in a control file, archived log, or // backup piece that // is being read for a backup or copy. Corruption shall not be // tolerated in control files, archived logs, 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 // control file 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 // control file 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 control file 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 .. UNRECOVERABLE 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 file name must be specified" // *Cause: The input file name was not specified for a control file copy // operation. // *Action: Specify an input file name and retry the operation. 19606, 00000, "Cannot copy or restore to snapshot control file" // *Cause: A control file copy or restore operation specified the name of the // snapshot control file as the output file. It is not permitted to // overwrite the snapshot control file in this manner. Other // methods are available to create the snapshot control file. // *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 control file" // *Cause: A control file copy, restore, or backup specified the name of a // control file 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 control file. // *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, "archived log thread %s sequence %s not found in backup set" // *Cause: The indicated archived log file was named explicitly 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 file that was not found. // *Action: See the instructions for message 19613. 19616, 00000, "output file name must be specified if database not mounted" // *Cause: A datafile restore specified no target file name, but the // database is not mounted. The database must be mounted when no // target file name is specified, so that the target file name // can be obtained from the control file. // *Action: The restore conversation remains active. If you wish to restore // datafiles without their target file names, then mount the database // before continuing. Otherwise, a target file name 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, "%s is not of %s type" // *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, its header was not // recognized as a valid file header for a file of the indicated // type (datafile, archived log, or control file) belonging // to the current database. // *Action: The indicated file cannot be processed. Ensure that the correct // files are being specified for the copy or backup operation. 19621, 00000, "archived log 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, "archived log 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 control file application" // *Cause: This is a control file restore conversation, which is using the // offline range information from one or more control files to update // datafile checkpoint data. Backup sets are not used during this // type of conversation. // *Action: The conversation is still active and more control files 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 archived log 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 file system 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, "archived log record contains no file name" // *Cause: This archived log 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 archived log 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 control file" // *Cause: The name passed to GETFNO was not found in the control file. // *Action: Supply a valid file name. 19633, 00000, "control file record %s is out of sync with recovery catalog" // *Cause: The control file 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, "file name 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 file names are identical: %s" // *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, "archived log thread %s sequence %s already included" // *Cause: The indicated archived log has already been specified for inclusion // in this restore conversation. A restore conversation may process // only one copy of any archived log. // *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 file name 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, "start SCN of incremental backup 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: Restore needs to adjust the size of the file as indicated, but // the file size adjustment failed. // *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. // // NOTE that this message will usually only be encountered by the // user while taking an incremental backup with Recovery Manager. // Recovery Manager should intercept all usual cases of this error // and simply ignore the incremental backup for this file. So, if // you do encounter this error, please report it to Oracle Support. 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 control file. This probably means that the // specified control file is no longer the same control file that // Recovery Manager thinks it is. // *Action: Specify the RECID/STAMP of a record that exists in the control file // 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 control file was backed up. // *Action: Restore and mount an earlier control file. It is acceptable to use // a control file that was backed up prior to the creation of the // specified datafile. 19654, 00000, "must use backup control file to switch file incarnations" // *Cause: This SWITCHTOCOPY operation is attempting to switch incarnations // of a datafile, but the currently mounted control file is not a // backup control file. // *Action: Restore and mount a backup control file. 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 control file 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 control file. // *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 control file" // *Cause: The control file was included in an incremental restore conversation // *Action: If you wish to restore the control file, you must do a full restore // of the control file 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: file number 0 specified in block media recovery // *Action: check file number 19682, 00000, "file %s not in block media recovery context" // *Cause: Internal error // *Action: 19683, 00000, "real and backup block size 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 19685, 00000, "SPFILE could not be verified" // *Cause: Some data blocks for the SPFILE were corrupt in the // backup set. // *Action: Unless the damage to the backup set can be repaired, the SPFILE // cannot be restored from this backup set. 19686, 00000, "SPFILE not restored due to %s" // *Cause: The indicated file could not be restored, because some of its data // blocks were not found in the backup piece. // *Action: Unless the damage to the backup set can be repaired, the SPFILE // cannot be restored from this backup set. 19687, 00000, "SPFILE not found in backup set" // *Cause: The SPFILE could not be restored, because it is not 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 in the piece. // You must supply the first backup piece of a backup set that // contains the requested file. 19688, 00000, "control file AUTOBACKUP format(%s) for %s does not have %F" // *Cause: control file AUTOBACKUP format must contain %F for the device. // *Action: Change control file format using RMAN command CONFIGURE CONTROLFILE // BACKUP FORMAT FOR DEVICE TYPE TO . 19689, 00000, "cannot have more than one %F in control file AUTOBACKUP format(%s) for %s" // *Cause: control file AUTOBACKUP format contains more than one %F for the // device. // *Action: Change control file format using RMAN command CONFIGURE CONTROLFILE // BACKUP FORMAT FOR DEVICE TYPE TO . 19690, 00000, "backup piece release %s incompatible with Oracle release %s" // *Cause: The backup piece was created by incompatible software. // *Action: Either restart with a compatible software release or create another // backup using the current release. 19691, 00000, "%s is from different database: id=%s, name=%s" // *Cause: The database name or database id in backup piece header does not // match the one in control file. // *Action: Supply the correct backup piece belonging to this database. 19692, 00000, "missing creation stamp on piece %s" // *Cause: The backup piece doesn't have information about creation stamp. // *Action: Supply another backup piece which is created by oracle 9i or // later version. 19693, 00000, "backup piece %s already included" // *Cause: This backup piece was already specified for inclusion in the // restore conversation. A restore conversation may process only // a single instance of a backup piece. // *Action: Remove the specified duplicate backup piece in restore steps // and restart the conversation. 19694, 00000, "some changed blocks were not found in the change tracking file" // *Cause: A backup or copy found that some changed blocks had not been // recorded in the change tracking file. The details of which files // and blocks are affected will be in an Oracle trace file. // *Action: This indicates that there is a problem with the change tracking // feature. Disable change tracking and re-start the backup. 19695, 00000, "fixed table X$KRBMSFT has not been populated" // *Cause: This is an internal error. The fixed table X$KRBMAFT was not // populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES. // *Action: Internal error - contact Oracle Customer Support. 19696, 00000, "control file not found in backup set" // *Cause: The control file could not be restored because it is not 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 in the piece. // You must supply the first backup piece of a backup set that // contains the requested file. 19697, 00000, "standby control file not found in backup set" // *Cause: The standby control file could not be restored because it is not // 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 in the piece. // You must supply the first backup piece of a backup set that // contains the requested file. 19698, 00000, "%s is from different database: id=%s, db_name=%s" // *Cause: Catalog failed because the database id in file header // does not match the one in control file. // *Action: Supply the correct file belonging to this database. 19699, 00000, "cannot make copies with compression enabled" // *Cause: Datafile copies with compression are not supported. // *Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called // outside RMAN, then the incompatible values are being passed for // the parameters DOCOMPRESS and IMAGCP. If this message occurs // during an RMAN job, then this is an internal error in RMAN, // and you should contact Oracle support. / / / 19700-19719: KRBI / / ************************************************************************** / * 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 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 file names in the // control file 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 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 %s for generated name" // *Cause: A restricted format or undefined format was used incorrectly. // *Action: Change the format specified in the additional information // by removing the restricted format. 19716, 00000, "error processing format %s to generate name for backup" // *Cause: There were errors while processing the format to generate // name for backup. // *Action: Change the format. 19717, 00000, "for non-OMF search the pattern must be specified" // *Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with // an empty pattern while the parameter OMF was set to FALSE. // *Action: Either specify the pattern or set the parameter OMF to TRUE. 19718, 00000, "length for command id longer than %s" // *Cause: The specified command id exceeds the maximum length for command id. // *Action: Supply a shorter command id and retry the operation. 19719, 00000, "length for operation name longer than %s" // *Cause: The specified operation name exceeds the maximum length for // operation name. // *Action: Supply a shorter operation name and retry the operation. / / 19720 - 19739 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 control file, 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 control file, 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. 19737, 00000, "simulate read-only database connection to execute sql query" // *Document: NO // *Cause: Set on RMAN foreground connections when archiver was hung. // *Action: Turn off plsql/sql statistics collection, obtaining the temp // segment for sorting and grabbing the sequence number from disk. / 19738, 00000, "cannot find language information for character set: '%s'" // *Cause: The compatibility check failed because a character set name // that was provided is not valid. // *Action: Correct the character set name and retry. / / 19740-19749: More KRBI errors / / 19740, 00000, "text is longer than %s" // *Cause: The specified text exceeds the maximum length for text. // *Action: Supply a shorter text and retry the operation. 19741, 00000, "%s exceeds maximum allowable length of %s for parameter '%s'" // *Cause: The specified string exceeds the maximum allowable length for // the parameter // *Action: Supply a shorter string for the parameter and retry the operation. 19742, 00000, "control file is not a backup control file" // *Cause: This parameter could not be set because the control file was not // a backup control file. // *Action: Do not use this call for this control file. / / / 19750 - 19799 reserved for Block Change Tracking / 19750, 00000, "change tracking file: '%s'" // *Cause: This message reports the name of a file involved in other messages. // *Action: See associated error messages for a description of the problem. 19751, 00000, "could not create the change tracking file" // *Cause: It was not possible to create the change tracking file. // *Action: Check that there is sufficient disk space and no conflicts in // file names and try to enable block change tracking again. 19752, 00000, "block change tracking is already enabled" // *Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, // but block change tracking is already turned on for this database. // *Action: None, this is an informative message only. 19753, 00000, "error writing to change tracking file" // *Cause: An I/O error occurred while writing to the change tracking file. // *Action: There will be other messages on the error stack that show // details of the problem. 19754, 00000, "error reading from change tracking file" // *Cause: An I/O error occurred while reading from the change tracking file. // *Action: There will be other messages on the error stack that show // details of the problem. 19755, 00000, "could not open change tracking file" // *Cause: The change tracking file could not be opened. // *Action: There will be other messages on the error stack that show // details of the problem. 19756, 00000, "corrupt block number %s found in change tracking file" // *Cause: The specified block number is corrupt in the change tracking file. // *Action: There will be other messages on the error stack that show // details of the problem. There will also be a trace file that // contains a complete dump of the corrupt block. 19757, 00000, "could not resize change tracking file to %s blocks" // *Cause: An error occurred while trying to change the size of the change // tracking file. // *Action: There will be other messages on the error stack that show // details of the problem. 19758, 00000, "failed to enable/disable block change tracking: out of SGA memory" // *Cause: out of SGA memory // *Action: Increase SGA and restart the instance. 19759, 00000, "block change tracking is not enabled" // *Cause: A command was entered that requires block change tracking to be // enabled, but block change tracking is not enabled. // *Action: None, this is an informative message only. 19760, 00000, "error starting change tracking" // *Cause: Change tracking is enabled, but a problem was encountered while // enabling the change tracking subsystem in this instance. // The alert log and the trace file from the CTWR process will // contain more information about the error. // *Action: Examine the trace and alert files. Correct the error if possible, // otherwise disable change tracking. 19761, 00000, "block size %s is not valid for change tracking file" // *Cause: While opening the specified change tracking file, it was found that // the file header did not contain a valid logical block size. This // probably means that the file is corrupt. // *Action: If the file can be repaired, do so, otherwise disable and re-enable // change tracking to re-initialize the file. 19762, 00000, "invalid file type %s" // *Cause: An invalid file type was found in the change tracking file. // Some other file was put in place of the change tracking file, or // the file is corrupt. // *Action: Disable then re-enable change tracking. 19763, 00000, "compatibility version %s is higher than maximum allowed: %s" // *Cause: The compatibility version in the change tracking file is greater // than what can be used by the current release of Oracle. // This can happen when you upgrade, use change tracking with a new // release, then downgrade. // *Action: Disable then re-enable change tracking. 19764, 00000, "database id %s does not match database id %s in control file" // *Cause: The change tracking file is not the correct one for this database. // This can happen when the database ID for this database has been // changed. // *Action: Disable then re-enable change tracking. 19765, 00000, "mount id %s does not match mount id %s in control file" // *Cause: The change tracking file does not match the one that was present // when this instance was opened. In RAC, this error is most likely // caused by having a change tracking file that cannot be // consistently updated by all instances. // *Action: In RAC, ensure that the name specified for the change tracking // file truly represents the same disk location for all nodes in // the cluster. Disable then re-enable change tracking. 19766, 00000, "missing CHANGE keyword" // *Cause: Syntax error. // *Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING 19767, 00000, "missing TRACKING keyword" // *Cause: Syntax error. // *Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING 19768, 00000, "USING clause only valid with ENABLE CHANGE TRACKING" // *Cause: The USING clause was specified with DISABLE CHANGE TRACKING // *Action: Correct the statement. 19769, 00000, "missing FILE keyword" // *Cause: Syntax error. // *Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING 19770, 00000, "invalid change tracking file name" // *Cause: The USING clause was specified with ALTER DATABASE ENABLE // BLOCK CHANGE TRACKING, but no file name was given. // *Action: Specify the change tracking file name, or omit the USING clause // to allow Oracle to create a default name for the change tracking // file. 19771, 00000, "cannot rename change tracking file while database is open" // *Cause: The ALTER DATABASE RENAME FILE command was used to rename the // change tracking file, and the database is open by one or more // instances. The database must be mounted, and not open, to // rename the change tracking file. // *Action: Close the database and reissue the command. 19772, 00000, "change tracking file name exceeds limit of %s characters" // *Cause: The name specified for the change tracking file is too long. // *Action: Specify a shorter change tracking file name. 19773, 00000, "must specify change tracking file name" // *Cause: No file name was specified with the ALTER DATABASE ENABLE // CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter // was not set. // *Action: Either specify a file name, or set the DB_CREATE_FILE_DEST // parameter. / // Do not use messages 19774 and 19775. They are KRC events. / 19776, 00000, "PROXY restore to ASM disk group \"%s\" is not supported." // *Cause: An attempt was made to proxy restore a file to ASM disk group // using RMAN command. This is not supported. // *Action: Use a different file name and reissue RMAN command. 19777, 00000, "ASM file %s cannot be proxy backed up." // *Cause: An attempt was made to proxy backup a ASM file. This is not // supported. // *Action: Use a different file name and reissue RMAN command. 19778, 00000, "event to be in hot backup mode for given seconds" // *Document: NO // *Cause: N/A // *Action: Set to test shutdown during proxy backup 19779, 00000, "could not obtain resilvering status for change tracking file" // *Cause: An error occurred while obtaining the mirror resilvering status // of the change tracking file. // *Action: Refer to other error messages shown for additional details of // the problem. 19780, 00000, "Active Data Guard option not enabled" // *Cause: Change tracking at a standby database required the Active Data // Guard option. // *Action: Enable the Active Data Guard option. / /19800 - 19829: Reserved for Recovery Area / / 19800, 00000, "Unable to initialize Oracle Managed Destination" // *Cause: The name given for an Oracle managed files destination // cannot be initialized. // *Action: Check previous error messages for the reason Oracle // was unable to initialize destination. Take corrective // action, if possible, and retry the command or use a // different name for destination. 19801, 00000, "initialization parameter DB_RECOVERY_FILE_DEST is not set" // *Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST // when DB_RECOVERY_FILE_DEST was not set. There are number of // possible causes of this error, including: // 1) A LOG_ARCHIVE_DEST_n parameter was specified using a // LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and // an archived log file creation was attempted. // 2) STANDBY_ARCHIVE_DEST parameter was specified using a // LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and // an archived log file creation was attempted. // *Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in // initialization parameter file or with the ALTER SYSTEM SET // command. 19802, 00000, "cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE" // *Cause: There are two possible cause for this error: // 1) The DB_RECOVERY_FILE_DEST parameter was in use when no // DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while // fetching initialization parameter. // 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the // ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE // was in use. // *Action: Correct the dependency parameter definitions and retry the command. 19803, 00000, "Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - %s)" // *Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid. // *Action: Specify a valid number within the range. 19804, 00000, "cannot reclaim %s bytes disk space from %s limit" // *Cause: Oracle cannot reclaim disk space of specified bytes from the // DB_RECOVERY_FILE_DEST_SIZE limit. // *Action: There are five possible solutions: // 1) Take frequent backup of recovery area using RMAN. // 2) Consider changing RMAN retention policy. // 3) Consider changing RMAN archived log deletion policy. // 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. // 5) Delete files from recovery area using RMAN. 19805, 00000, "RECID %s of %s was deleted to reclaim disk space" // *Cause: The file described by the record in control file was deleted // in order to reclaim disk space from recovery area for // other operations. // *Action: Wait and try again. 19806, 00000, "cannot make duplex backups in recovery area" // *Cause: Duplex backup to recovery area is not supported. // *Action: Remove duplex option and try again. 19808, 00000, "recovery destination parameter mismatch" // *Cause: The value of parameters DB_RECOVERY_FILE_DEST and // DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. // instance. All databases must have same recovery destination // parameters. // *Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE // values in all instances. 19809, 00000, "limit exceeded for recovery files" //*Cause: The limit for recovery files specified by the // DB_RECOVERY_FILE_DEST_SIZE was exceeded. // *Action: There are five possible solutions: // 1) Take frequent backup of recovery area using RMAN. // 2) Consider changing RMAN retention policy. // 3) Consider changing RMAN archived log deletion policy. // 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. // 5) Delete files from recovery area using RMAN. 19810, 00000, "Cannot create temporary control file %s in DB_RECOVERY_FILE_DEST" // *Cause: An attempt was made to create a control file for a temporary purpose // in DB_RECOVERY_FILE_DEST. // *Action: Retry the operation with a new file name. 19811, 00000, "cannot have files in DB_RECOVERY_FILE_DEST with keep attributes" // *Cause: An attempt was made to // 1) Create a backup piece or image copy in the recovery area with // KEEP option. // 2) Update the KEEP attributes of an existing backup piece or // image copy in the recovery area. // *Action: Reissue RMAN command without KEEP options. 19812, 00000, "cannot use %s without DB_RECOVERY_FILE_DEST" // *Cause: There are three possible cause for this error: // 1) The indicated parameter was in use when no // DB_RECOVERY_FILE_DEST parameter was encountered while // fetching the initialization parameter. // 2) An attempt was made to set indicated the parameter with // the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST // was in use. // 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with // the ALTER SYSTEM command when the indicated parameter // was in use. // *Action: Eliminate any incompatible parameter definitions. 19813, 00000, "cannot have unavailable file %s in DB_RECOVERY_FILE_DEST" // *Cause: An attempt was made to change a backup piece or image copy in // recovery area to UNAVAILABLE. // *Action: Correct and resubmit the RMAN command. // Do not use messages 19814; it is used for simulating crash. 19815, 00000, "WARNING: %s of %s bytes is %s%% used, and has %s remaining bytes available." // *Cause: DB_RECOVERY_FILE_DEST is running out of disk space. // *Action: One of the following: // 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. // 2. Backup files to tertiary device using RMAN. // 3. Consider changing RMAN retention policy. // 4. Consider changing RMAN archived log deletion policy. // 5. Delete files from recovery area using RMAN. 19816, 00000, "WARNING: Files may exist in %s that are not known to database." // *Cause: One of the following events caused this: // 1. A database crash happened during file creation. // 2. A backup control file was restored. // 3. The control file was re-created. // 4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled. // *Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such // files. If the file header is corrupted, then delete those files // using an OS utility. // Do not use messages 19817; it is used for simulating lock failure // Do not use messages 19818; it is used for space reclamation before backup // Do not use messages 19819; it is used to disable clearing file name 19820, 00000, "database must be in NOARCHIVELOG mode to disable logging" // *Cause: Logging was disabled when ARCHIVELOG mode was used. // *Action: Execute ALTER DATABASE NOARCHIVELOG in mount state. 19821, 00000, "an intentionally corrupt log file was found" // *Cause: A log file that was intentionally corrupt for testing or // benchmarking purposes was found and failed the operation. // *Action: Remove such log files and retry or use the NOARCHIVELOG option // if possible. 19822, 00000, "mmon recovery area usage monitoring interval" // *Document: NO // *Cause: Set on all instances to change recovery area usage monitoring // interval. // *Action: level 1 - once every 15 minutes. // level 2 - once every 30 minutes. // ... // level n - once every n * 15 minutes. 19823, 00000, "soft limit recovery area space pressure percentage" // *Document: NO // *Cause: Set on all instances to alter recovery area space pressure // trigger percentage. // *Action: level 1 to 100 indicates the percentage when the space // pressure has to be triggered. 19824, 00000, "amount of space in MB to be reclaimed on archiver IO error" // *Document: NO // *Cause: Set on all instances to alter recovery area reclaimation space // on archiver IO error. // *Action: level indicates the amount in MB. 19825, 00000, "recovery area test event level %s" // *Document: NO // *Cause: Event set to test various recovery area error conditions. // *Action: None. / / / / 19830 - 19835: reserved for SQL Engine Errors: / 19830, 00000, "error from target database: \n%s" // *Cause: This error should be followed by other errors indicating // the cause of the problem. // *Action: No action required. 19831, 00000, "incompatible %s.%s.%s.%s DBMS_BACKUP_RESTORE package: %s.%s.%s.%s required" // *Cause: This version of database was incompatible with the the indicated // DBMS_BACKUP_RESTORE package installed in the database. // *Action: If the database has been upgraded from an earlier version, ensure // that the catxxxx.sql script has been run successfully. // Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. / /19836 - 19850: General purpose. First free message=19839. 19836, 00000, "cannot use passphrase encryption for this backup" // *Cause: Passphrase encryption was attempted for a backup that // contains encrypted tablespaces and uses compression. // *Action: Do not use passphrase encryption for this backup. // Use transparent wallet-based encryption instead. 19837, 00000, "invalid blocksize %s in backup piece header" // *Cause: The blocksize of the backup piece obtained from the header was // invalid. // *Action: The backup piece is corrupted, a different backup piece should // be used for restore. 19838, 00000, "Cannot use this control file to open database" // *Cause: This control file was restored by a DUPLICATE operation used only // to restore and recover the datafiles of the new database. It is // not meant to be used for opening the database, as allowing so // might corrupt datafiles or online redo logs of the target // database or both. // *Action: Re-create control file manually specifying all names of datafiles // and online redo logs. Do not forget to use NID to change the // name or DBID or both of the new database. 19843, 00000, "Cannot obtain datafile name for datafile %s" // *Cause: While trying to obtain the file enqueue for the datafile the // datafile name could not be obtained. // *Action: Examine the trace and alert files for possible causes. // Fix underlying problem before attempting command again. / /19851 - 19859: Reserved for Recovery Area / 19851, 00000, "OS error while managing auxiliary database %s" // *Cause: An OS error was received while managing the automatic // auxiliary instance. // *Action: Check the accompanying errors. 19852, 00000, "error creating services for auxiliary instance %s (error %s)" // *Cause: An error was received while managing the services // of the auxiliary instance. // *Action: Check the accompanying errors. 19853, 00000, "error preparing auxiliary instance %s (error %s)" // *Cause: An error was received while managing the automatic // auxiliary instance. // *Action: Check the accompanying errors. 19854, 00000, "error obtaining connect string from target" // *Cause: Could not obtain the connect string from the target database // *Action: Check the accompanying errors. / / / 19860 - 19879 reserved for Additional KRB* errors / 19860, 00000, "piece validation cannot be performed more than once" // *Cause: The user attempted to validate a list of backup pieces // more than once. Validation may only be performed once for // a given validation conversation. // *Action: Do not attempt to validate the pieces more than once. 19861, 00000, "additional backup pieces cannot be validated in this conversation" // *Cause: The user tried to add new pieces to the list of files // being validated after the validation had already been // performed. In a validation conversation, the list can // only be validated once. // *Action: Add all the backup pieces to the list before validating, // or start a new validation conversation for the remaining pieces. 19862, 00000, "backup pieces must be validated before accessing results" // *Cause: The user tried to get validation results for backup pieces before // the pieces were actually validated. // *Action: Validate the pieces before trying to access the results. 19863, 00000, "device block size %s is larger than max allowed: %s" // *Cause: The user specified a device BLKSIZE that is larger than the device // BLKSIZE specified during compressed backup. // *Action: Change the device BLKSIZE to be smaller than the maximum allowed. 19864, 00000, "%s" // *Cause: // *Action: 19865, 00000, "Backup piece %s has no data" // *Cause: No data was returned for the specified backup piece. // *Action: This normally indicates a problem with the media management // software which is linked with Oracle to provide backup and // restore services. // Contact the media management software vendor. 19866, 00000, "error writing file header for datafile %s" // *Cause: During a block recovery, the header of the datafile could not // be updated. // *Action: Contact Oracle Support Services. 19870, 00000, "error while restoring backup piece %s" // *Cause: This error should be followed by other errors indicating // the cause of the problem. // *Action: See other errors actions. / // Do not use message 19871; it is used by RMAN client for testing previous // resync time when using backup/standby control file. // 19872, 00000, "Unexpected end of file at block %s while decompressing backup piece %s" // *Cause While reading a compressed backup piece, RMAN received an // end-of-file without finding the end-of-compression stream. // *Action: This is most likely caused by a corrupted backup piece. // Consider using a different backup piece for restore. 19873, 00000, "cannot apply this backup section to file %s" // *Cause RMAN cannot restore a multi-section backup to the indicated // file, because this section is not a backup of this file, or // the file was not prepared correctly for this restore. // *Action: If this error occurs while running RMAN, then it is an internal // error and you should contact Oracle support. 19874, 00000, "cannot finish multi-section restore to file %s" // *Cause: During a multi-section restore, the file being restored is not // a file in which a multi-section restore is in progress. // *Action: If this error occurs while running RMAN, then it is an internal // error and you should contact Oracle support. 19875, 00000, "multi-section restore not complete for file %s" // *Cause: While completing a multi-section restore, it was found that // all required sections for this file were not correctly applied. // *Action: If this error occurs while running RMAN, then it is an internal // error and you should contact Oracle support. / / 19876 - 19879 : Reserved for testing events. / / 19880 - 19889 reserved for optimized backups / 19880, 00000, "Corrupted space header for datafile %s, block %s" // *Cause: When reading the space header block to use Unused Block // Optimization for the backup of the datafile, the space header // block had corrupted information. // *Action: The corrupt space header must be fixed before Unused Block // Optimization can be used for this file. Note that you should // fix the corruption in any case because it will affect the // availability of the data in the file, beyond just taking // backups. 19881, 00000, "Corrupted space bitmap for datafile %s, block %s" // *Cause: When reading a space bitmap block to use Unused Block // Optimization for the backup of the datafile, the space bitmap // block had corrupted information. // *Action: The corrupt space bitmap must be fixed before Unused Block // Optimization can be used for this file. Note that you should // fix the corruption in any case because it will affect the // availability of the data in the file, beyond just taking // backups. 19882, 00000, "datafile %s checkpoint %s is ahead of space bitmap datafile %s checkpoint %s" // *Cause: When checkpointing the datafile containing the space bitmaps // for the datafile being backed up in order to use Unused Block // Optimization, the checkpoint of the datafile containing the // space bitmaps did not advance. // *Action: Examine the trace and alert files for possible causes. // Fix underlying problem to use Unused Block Optimization // for datafile's backup. 19883, 00000, "Unused Block Optimization stopped for datafile %s" // *Cause: Accompanying errors detail the problem that prevented // Unused Block Optimization from being used. // *Action: See accompanying errors for appropiate action. 19884, 00000, "datafile %s is unable to use Unused Block Optimization because tablespace has been dropped" // *Cause: When attempting to find information about datafile that holds // bitmaps of migrated tablespace, the tablespace was found to have // been dropped. // *Action: None. This is an informational message. / / 19899 - 19912 reserved for recovery through RESETLOGS project / 19899, 00000, "missing incarnation information" // *Cause: Media recovery stopped because information of one or more ancestor // incarnations of recovery target incarnation was not available. // *Action: Register logs from the missing incarnations and retry recovery. 19900, 00000, "RESETLOGS must be specified after recovery to new incarnation" // *Cause: Recovery was done to an incarnation after changing the destination // incarnation using RMAN's RESET DATABASE command. // *Action: Open the database with the RESETLOGS option. 19901, 00000, "database needs more recovery to create new incarnation" // *Cause: Recovery was done to an incarnation after changing the destination // incarnation using RMAN's RESET DATABASE command, but one or more // of the recovered datafiles still belongs to the parent incarnation. // This usually happens when recovery is ended before any logs from // the desired incarnation have been applied. // *Action: Continue recovery. 19902, 00000, "incarnation key %s not found" // *Cause: The specified incarnation was not found in the control file. // *Action: Resubmit request with known incarnation key. // To see which incarnations are available for this target database, // query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION // command. 19903, 00000, "test recovery not allowed when recovering to new incarnation" // *Cause: Either a new incarnation was set using RMAN's RESET // DATABASE command for a control file that was CURRENT, or the // control file is from a prior incarnation. As recovery to // a new incarnation requires changing the control file, test // recovery is not allowed. // *Action: Perform actual recovery or RESET DATABASE to incarnation // that was last opened using the control file to do test recovery. 19904, 00000, "test recovery not allowed for datafile %s" // *Cause: The specified datafile has been restored from a backup that was // taken before the last RESETLOGS. Recovering this datafile will // require a file header update that is incompatible with test // recovery. // *Action: Perform actual recovery. 19905, 00000, "log_archive_format must contain %%s, %%t and %%r" // *Cause: log_archive_format is missing a mandatory format element. // Starting with Oracle 10i, archived log file names must contain each // of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to // ensure that all archived log file names are unique. // *Action: Add the missing format elements to log_archive_format. 19906, 00000, "recovery target incarnation changed during recovery" // *Cause: While a media recovery was active, a new incarnation was detected // by the server due to inspection or cataloging of archived logs // or backup files. // *Action: If you want recovery to use the new incarnation, restart recovery. // This is the most common action on a standby database when RESETLOGS // is done in primary. If you do not want recovery to use the new // incarnation, // change the recovery destination using RMAN's RESET DATABASE // TO INCARNATION command. // To see which incarnations are available for this target database, // query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION // command. 19907, 00000, "recovery time or SCN does not belong to recovered incarnation" // *Cause: A point-in-time recovery to an SCN or time stamp prior to the last // RESETLOGS was requested. // *Action: Either change the specified recovery time/SCN, or // change the recovery destination using RMAN's RESET DATABASE // command. 19908, 00000, "datafile %s has invalid checkpoint" // *Cause: The specified datafile has an invalid checkpoint. // *Action: Restore the datafile from a backup. 19909, 00000, "datafile %s belongs to an orphan incarnation" // *Cause: Either the specified datafile was restored from a backup that was // taken during a period of time that has already been discarded by // a RESETLOGS operation, or Oracle cannot identify which database // incarnation the file belongs to. The alert log contains more // information. // *Action: Restore a backup of this file that belongs to either the current // or a prior incarnation of the database. If you are using RMAN // to restore, RMAN will automatically select a correct backup. 19910, 00000, "can not change recovery target incarnation in control file" // *Cause: The RESET DATABASE TO INCARNATION command was used while the // database is open. This is not allowed. // *Action: Close the database then re-issue the command. 19911, 00000, "datafile %s contains future changes at the incarnation boundary" // *Cause: The file did not hit end backup marker redo during recovery at // the incarnation boundary, hence may contain changes discarded // by new incarnation. // *Action: Use older backup of the file and then re-issue the command. 19912, 00000, "cannot recover to target incarnation %s" // *Cause: The control file is not in the recovery path of the target // incarnation, and does not contain enough information as to how // to recover to the target incarnation. // *Action: Restore the latest control file from the target incarnation and // retry. / / 19913 - 19920 reserved for encrypted backups / 19913, 00000, "unable to decrypt backup" // *Cause: A backup piece could not be decrypted. This message is accompanied // with another message that indicates the name of the encrypted // backup that could not be restored. The reason could be either // that an invalid password was entered, or that, when using // transparent decryption, the database external security device // is not open. // *Action: If password-based restore was enabled for this backup, // then supply the correct password using the RMAN SET DECRYPTION // command. If transparent restore was enabled for this backup, // then ensure that the database external security device is open. 19914, 00000, "unable to encrypt backup" // *Cause: RMAN could not create an encrypted backup. This message will // be accompanied by other messages that give more details about // why the encrypted backup could not be created. The most common // reason for this message is that you are trying to create a // backup that can be transparently decrypted, and the database // external security device is not open. // *Action: If the external security device is not open, then open it. // If the external security device is not configured, then the // only type of encrypted backup that you can create is a // password-based backup. 19915, 00000, "unable to encrypt pre-10.2 files" // *Cause: An RMAN encrypted backup was requested, but this backup includes // one or more archived logs that were generated by an older // release of Oracle. These archived logs cannot be encrypted. // *Action: Back up the older logs without encryption. Logs created with // Oracle release 10.2 and greater can be encrypted. 19916, 00000, "%s" // *Cause: An error occurred when processing user request. // *Action: // Do not use message 19917; it is used internally for testing purpose. // Do not use message 19918; it is an internal event used by encryption. 19919, 00000, "encrypted backups to tertiary storage require Oracle Secure Backup" // *Cause: RMAN was configured to create encrypted backups, but the channel // is neither a DISK channel nor an Oracle Secure Backup channel. // *Action: Allocate a DISK channel or an Oracle Secure Backup channel to // use backup encryption. 19920, 00000, "RMAN does not support PKI-based master key for encryption." // *Cause: An attempt was made to use Oracle public key infrastructure (PKI) // based master key algorithm. RMAN only supports Advanced Encryption // Standard (AES) based encryption. // *Action: Use AES based encryption. / /19921 - 19925: KRB* errors / / 19921, 00000, "maximum number of %s rows exceeded" // *Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT // table has been exceeded. // *Action: Close some of existing and unused RMAN connections and sessions. 19922, 00000, "there is no parent row with id %s and level %s" // *Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row // did not exist. // *Action: This is an internal error. Contact Oracle Support. 19923, 00000, "the session for row with id %s is not active" // *Cause: RMAN tried to update an V$RMAN_STATUS row but the process which // owns this row died. // *Action: This is an internal error. Contact Oracle Support. 19924, 00000, "there are no row with id %s" // *Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don't exist. // *Action: This is an internal error. Contact Oracle Support. 19925, 00000, "Internal error while cleaning memory used by V$RMAN_STATUS view" // *Cause: // *Action: This is an internal error. Contact Oracle Support. / / / 19926 - 19929: reserved for transport database errors / 19926, 1, "Database cannot be converted at this time" // *Cause: Another CONVERT DATABASE operation is already in progress. // *Action: Retry CONVERT DATABASE command later. 19927, 1, "CONVERT DATABASE operation cannot proceed" // *Cause: An error occurred earlier during CONVERT DATABASE operation. // *Action: Retry CONVERT DATABASE command. 19928, 1, "CONVERT of data files with undo segments between different endian is not supported." // *Cause: Conversion of data files with undo segments was not supported between endianess. // The only time that data files with undo segments can be converted is between the // same endianess as part of convert database. Convert database between different // endian is not supported. // *Action: Do not attempt to convert data files with undo segments between different endian. / /19930 - 19940: More KRB* errors / 19930, 00000, "file %s has invalid checkpoint SCN %s" // *Cause: When opening the file to be placed in a copy or backup set, // to be inspected, the file header was not recognized as a valid // header because it contained a invalid checkpoint SCN. The // indicated file cannot be processed. // *Action: Ensure that the correct files are being specified for the // catalog or backup operation. 19931, 00000, "file %s has invalid creation SCN %s" // *Cause: When opening the file to be placed in a copy or backup set, // to be inspected, the file header was not recognized as a valid // header because it contained a invalid creation SCN. The indicated // file cannot be processed. // *Action: Ensure that the correct files are being specified for the // catalog or backup operation. 19932, 00000, "control file is not clone, standby or backup" // *Cause: The operation failed because the control file was not mounted as // clone, standby or backup. // *Action: Mount the database as clone, standby or backup and retry. / / 19941- 19950 reserved for cross platform transpotable tablespace (xtts) / 19941, 00000, "invalid blocksize in cross platform datafile %s" // *Cause: Blocksize in header of datafile copy being converted at target // was invalid. Either datafile has not been made read/write // with compatibility 10.0 or greater at source database or // datafile copy is corrupted. // *Action: Make a new datafile copy taken after tablespace has been made // read/write with compatibility 10.0 at source database and retry // conversion. 19942, 00000, "datafile copy %s not created with compatibility 10.0 or greater" // *Cause: The specified datafile copy to be converted at the target was // not produced after making the tablespace in read/write mode // with compatibility 10.0 or greater at the source database. // *Action: Make a new datafile copy taken after tablespace has been made // read/write with compatibility 10.0 at source database and retry // conversion. 19943, 00000, "The current database incarnation changed during backup" // *Cause: The backup failed because the current database incarnation was // changed during the backup. // One of the following events caused this incarnation change: // - The database was opened using ALTER DATABASE OPEN RESETLOGS // statement. // - RMAN command RESET DATABASE TO INCARNATION was issued. // - If this happened on physical standby database, then redo apply // has applied redo data from a new database incarnation. // *Action: Re-try the backup. / / 19951- 19960 reserved for NID / 19951, 00000, "cannot modify control file until DBNEWID is completed" // *Cause: An operation requiring to modify the control file was // attempted, but a NID change is in progress. // *Action: Wait until NID completes before attempting the operation. 19952, 00000, "database should be mounted exclusively" // *Cause: The database was started in parallel mode. To change the DBID, // the database must be mounted exclusively. // *Action: Shut down the database and start it in exclusive mode. 19953, 00000, "database should not be open" // *Cause: The database was open. To change the DBID, the database must be // mounted exclusively. // *Action: Shut down the database and mount it in exclusive mode. 19954, 00000, "control file is not current" // *Cause: The operation failed because a non-current, non-standby control // file was mounted. // *Action: Make the control file current and retry. 19955, 00000, "only one open thread is allowed to change the DBID" // *Cause: The operation failed because there were active threads in the // database. The most likely cause is that the database crashed the // last time it was shut down. // *Action: Ensure that all threads are closed before retrying // the operation. Start and open the database // to perform crash recovery, then shut down with the NORMAL // or IMMEDIATE options to close it cleanly. Finally, try running // the utility again. 19956, 00000, "database should have no offline immediate datafiles" // *Cause: The operation failed because the database had one or more // datafiles that were in OFFLINE IMMEDIATE mode. // *Action: Drop the datafiles or recover them and bring them online. 19957, 00000, "database should have no datafiles in unknown state" // *Cause: The operation failed because the database had one or more // datafiles that were in an unknown state. // *Action: Drop the datafiles or recover them and bring them online. 19958, 00000, "potential deadlock involving DIAG process" // *Cause: DIAG requested a control file operation that may lead // to a deadlock // *Action: Try last operation later when the control file is released // NLS_DO_NOT_TRANSLATE [19960,19960] 19960, 00000, "Internal use only" // *Cause: NID usage // *Action: None / 19961, 00000, "compression algorithm %s requires advanced compression option to be enabled" // *Cause: Requested compression algorithm in initialization parameter // or by RMAN configuration requires that the advanced // compression option be enabled and it was not. // *Action: Change initialization parameter advanced_compression_option_usable // to true or change RMAN configurations and retry the operation. 19962, 00000, "compression algorithm %s is not valid with release %s" // *Cause: Algorithm in initialization parameter requires a lower // compatibility that is currently set. // *Action: Change algorithm in initialization parameter file or lower // compatibility. 19963, 00000, "error getting logical block size of file %s" // *Cause: Error occurred when querying the logical block size of a file. // *Action: None / / 19965 - 19999 multi-instance standby switchover / 19965, 00000, "ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated" // *Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER // statement (partial_database_recovery clause) has been deprecated. // *Action: If you want to recover the standby database to a consistent point, // but no further, use the statement ALTER DATABASE RECOVER MANAGED // STANDBY DATABASE UNTIL CONSISTENT. 19966, 00000, "ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated" // *Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER // statement (partial_database_recovery clause) has been deprecated. // *Action: If you want to recover the standby database to a consistent point, // but no further, use the statement ALTER DATABASE RECOVER MANAGED // STANDBY DATABASE UNTIL CONSISTENT. / 19970, 00000, "multi-instance standby role transition in progress" // *Cause: ALTER DATABASE MOUNT failed because a multi-instance standby // role transition was in progress. // *Action: Retry after the multi-instance standby role transition finishes. 19971, 00000, "event 10875 or 10879 is set" // *Cause: Event 10875 or event 10879 was set which prevented the operation // from completing with multiple instances running in Oracle RAC. // *Action: Shutdown all but one instance, then retry the command. 19972, 00000, "ALTER DATABASE RECOVER TO LOGICAL requires one instance left" // *Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to // be left running. // *Action: Shutdown all but one instance, then retry the command. 19973, 00000, "flashback database is not enabled" // *Cause: Physical standby transition to snapshot standby required only one // instance left running if flashback database logging was not // enabled. // *Action: Shutdown all but one instance, then retry the command. 19974, 00000, "database name has changed" // *Cause: Physical standby role transition required only one instance left // running if database name was changed and flashback database // logging was enabled. // *Action: Shutdown all but one instance, then retry the command. 19975, 00000, "database must not be started in any other instance" // *Cause: The physical standby role transition command failed because // a certain condition required the database to be mounted in this // instance and not started in any other instance. // *Action: See associated error message for detailed explanation. 19976, 00000, "a concurrent standby role transition in progress" // *Cause: The standby role transition operation failed because a // concurrent standby role transition was already in progress. // *Action: None / / Error numbers / / 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 - 23599: Replication Packages / 23600 - 23999: Log Based Replication Packages / 24000 - 24099: AQ admin interface / 24100 - 24119: DBMS_SCHEDULER package / 24120 - 24140: DBMS_REPAIR package / 24141 - 24179: DBMS_RULE package / 24190 - 24199: AQ JMS / 24200 - 24229: DBMS_AQADM package / 24230 - 24264: Miscellaneous DBMS* packages / 24265 - 24269: DBMS_SQLTUNE package / 24270 - 24279: DBMS_HO package / / MODIFIED / mahrajag 04/04/11 - Backport bug 10150436 from main / huntran 02/08/11 - Backport huntran_bug-11678106 from main / atomar 01/07/11 - Backport atomar_bug-10111363 from main / atomar 12/15/10 - Backport atomar_bug-10102731 from main / yberezin 11/27/10 - Backport yberezin_bug-9686001 from main / jamferna 11/19/10 - Backport jamferna_bug-9476520 from main / yifeng 06/19/10 - bug 9491716: modify error 22843 / jstewart 05/24/10 - added error msg 21528 / yifeng 03/26/10 - bug 9491716: add error 22843 / shbose 11/05/09 - bug 8843855: Add errors 24174 and 24175 / skabraha 10/02/09 - add 22350 / yifeng 10/31/08 - add event 22842 / kgiyer 11/11/08 - bug 6331369: new error for subset rule buffer overflow / skabraha 10/10/08 - add mesg 22374 / akruglik 10/01/08 - (4227938): add msg 22841 / yberezin 09/25/08 - bug 7112727: new error 23661 for capture / achoi 08/18/08 - add message 22348 / mcoulter 07/30/08 - bug 7281890 kse/kge messages wrongly using %d / gagarg 04/03/08 - Change error message of 24005 / msakayed 04/03/08 - add directory execute privilege / jstewart 03/31/08 - update of msg 22635 / rpingte 02/23/08 - add 22635 / yifeng 12/17/07 - bug 6490005, add ORA-22936 / jstewart 10/09/07 - adding msg 22141 / yifeng 09/26/07 - bug 2691510 remove "nested table" in ORA-22901 / yifeng 09/25/07 - add 22866 / atomar 09/19/07 - bug 4683748 / tianli 08/22/07 - add ORA-23658 to ORA-23660 / sjanardh 08/02/07 - ORA-24085 cause changes / yizhang 05/02/07 - Fix bug 5040073 / skabraha 03/14/07 - add 22373 / cschmidt 04/10/07 - add ORA-23644 to ORA-23656 / shbose 03/30/07 - Backward compatible propagation / legao 03/02/07 - add ORA-23642 and ORA-23643 / skabraha 03/01/07 - add type dict upgrade event / jstewart 02/27/07 - remove 22635 error / tianli 02/05/07 - add ORA-23637 to ORA-23641 be the reasons of ORA-23630 / yifeng 01/10/07 - add ORA-22839 for direct updating SYS_NC columns / yizhang 12/21/06 - Fix bug 5394563 / cschmidt 12/14/06 - add ORA-23630 to ORA-23634 / juyuan 11/15/06 - add ORA-23629 for DBMS_COMPARISON / yifeng 11/15/06 - add ORA-22837 for relational hint or keyword for / user level DML. add event 22838 to avoid throwing / this error. / kchen 10/31/06 - add ORA-24277 to ORA-24279 / rpingte 09/07/06 - add ORA-22635 for 8.0 image pickling / rpang 08/30/06 - add ORA-24245 for DBMS_NETWORK_ACL_ADMIN / slynn 08/09/06 - LOCAL to SMARTFILE / rpang 05/15/06 - add ORA-24243 and 24244 for DBMS_NETWORK_ACL_ADMIN / rvenkate 04/19/06 - add comparison error messages / kkunchit 11/01/05 - project-18204: inode: LOCAL/NOLOCAL support / mbaloglu 12/19/05 - Project 18207: Adding [A]SYNC property for LOBs / rpang 03/15/06 - add message ORA-24242 for embedded PL/SQL gateway / gtarora 12/05/05 - event 22935: ucs2 lobs / yuli 10/31/05 - remove unused error numbers / molagapp 08/22/05 - molagapp_dbhygiene_rman_3 / molagapp 08/16/05 - split e19400.msg / molagapp 08/16/05 - Creation / 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/KOKD/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. 21527, 00000, "internal OMS driver error" // *Cause: A process has encountered an exceptional condition. This is the // generic internal error number for Oracle object management // services exceptions. // *Action: Report this as a bug to Oracle Support Services. 21528, 00000, "internal error, image could not be understood" // *Cause: The format of the image passed to the pickler is incorrect and // cannot be understood. // *Action: Contact Oracle Support Services. / / / 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. 21780, 00000, "Maximum number of object durations exceeded." // *Cause: This typically happens if there is infinite recursion in the PL/SQL // function that is being executed. // *Action: User should alter the recursion condition in order to prevent // infinite recursion. / / / Error numbers from 21800 to 21998 are reserved. / / / Error numbers from 22000 to 22298 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. / 22141, 00000, "given size [%s] must be even in UTF-16 environment" // *Cause: The given resize size is odd. In a UTF-16 environment, all // characters are 2 bytes in length. // *Action: Ensure that the given size is even. / 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 [%s] 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; (5) the locator is for a // BFILE/BLOB and the routine expects a CLOB/NCLOB locator; // (6) the locator is for a CLOB/NCLOB and the routine expects // a BFILE/BLOB locator; // *Action: For (1), initialize the LOB locator by selecting into the locator // variable or by setting the LOB locator to empty. For (2),(3), // (5) and (6)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. / 22283, 00000, "filename contains characters that refer to parent directory" // *Cause: Filename contains a path "../" which references a parent directory // *Action: Ensure that the filename does not contain characters which // reference a parent directory. / 22284, 00000, "duplicate LONG binds are not supported" // *Cause: LOB access layer could not handle duplicate LONG binds. // *Action: Provide distinct LONG or VARCHAR binds. / 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. 22298, 00000, "length of directory alias name or file name too long" // *Cause: The length of directory alias name or file name given for a BFILE // is too long. // *Action: Use a shorter alias or file name. // 22299, 00000, "Synonym compile without validating base object" // *Document: No // *Cause: // *Action: No validation of the base object. / 22300, 00000, "acquiring DML lock in WAIT mode on table that is locked by KGL or KQR" // *Document: NO // *Cause: An attempt was made to acquire a DML lock in WAIT mode on a table // that is locked by KGL or KQR. // *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 22301 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 %s 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 / 22342, 00000, "dependent VARRAY column exceeds the maximum inline column size" // *Cause: An attempt was made to alter a type (add or modify attribute) // which causes the size of its dependent VARRAY column to exceed the // maximum inline column size. 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. / 22343, 00000, "Compilation error for type invalidated by ALTER TYPE" // *Cause: Compilation failed for a type which was invalidated by ALTER TYPE. // We throw this error and rollback the compilation effort so that // the user may be able to fix whatever is causing the compilation // error and try again. It is important that we do not chnage status // here and modify the dependency information as this will affect // the creation of versions. // *Action: Check what is causing teh compilation error and correct it and // try again. / 22344, 00000, "can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change" // *Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for // ALTER TYPE other than NOT FINAL change. // *Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT // FINAL change. / 22345, 00000, "recompile type %s.%s before attempting this operation" // *Cause: An attempt was made to perform an operation which requires the // specified datatype to be valid, but the datatype is invalid // *Action: Recompile the specified type and retry the operation / 22346, 00000, "Type has cyclical dependency. Should use CASCADE option" // *Cause: An attempt was made to alter a type which has a cyclical // dependency, with invalidate option. // *Action: Give CASCADE option instead of INVALIDATE / 22347, 00000, "No changes to type specified for ALTER TYPE" // *Cause: The ALTER TYPE does not contain any changes to the type. // *Action: If any change is required for the type, modify the ALTER TYPE to // specify the change. Else no need for the ALTER. / 22348, 00000, "The object type DDL is not supported in Editioned schema" // *Cause: The object type DDL was not supported in an Editioned schema. // *Action: Do not perform this DDL on an Editioned schema object. / / Error numbers from 22350 to 22370 are reserved for ORT/KOT (Opaque Types). / 22350, 00000, "Incomplete opaque type cannot be used here" // *Cause: An incomplete SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is // being used inappropriately. // *Action: Check the documentation for correct usage. / / 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. / 22372, 00000, "Event for type dictionary upgrade" // *Cause: This is an internally used event for type dictionary upgrades // from 8.0 to 8.1. // *Action: None. / 22373, 00000, "Older version hashcode encountered" // *Cause: An older version HC is encountered when creating a new version // hahscode. Currently this is handled internally. // *Action: None. / 22374, 00000, "cannot reset the version of a type with table dependents" // *Cause: The type for which reset version was requested has table // dependents. // *Action: None. / / 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. / 22635, 00000, "time stamp with time zone type not supported " // *Cause: OCIAnyData did not support conversion of time stamp with time // zone when the version of time zone files differ. // *Action: Use same version of time zone files. / / Error numbers from 22700 to 22799 are reserved for debugging event numbers. / // NLS_DO_NOT_TRANSLATE [22700,22700] 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, "remote implementation type not supported" // *Cause: Remote type reference was not supported / with user-defined aggregate function. // *Action: Use local implementation type with user-defined // aggregate function. 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. 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, INSERT with subquery, // and INSTEAD OF Triggers. // *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 22824, 00000, "Event to lookup remote objects using DDFNET for snapshots" // *Document: NO // *Cause: N/A // *Action: Enables lookup of remote objects through DDFNET for snapshots // rather than using the remote transfer KGL mechanism. 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. 22830, 00000, "Event enabling VARRAYs columns to be created as OCTs" // *Document: NO // *Cause: N/A // *Action: Enables all VARRAY columns to be created as Ordered // Collection in Tables (ie with table storage) 22831, 00000, "Offset or offset+amount does not land on character boundary" // *Document: NO // *Cause: (1) Source offset for BFILE (in bytes) does not start // from a complete character. // (2) Starting offset to read or write a LOB cuts into // a surrogate pair. // (3) The end of a LOB write (offset+amount) cuts into // a surrogate pair. // *Action: (1) Make sure offset land on character boundary. // (2) Try to adjust the offset by (+/-)1 UCS2 codepoint. // (3) Try to adjust the amount by (+/-)1 UCS2 codepoint. 22832, 00000, "Event enabling LOB columns to share the same segment" // *Document: NO // *Cause: N/A // *Action: Enables all LOB columns to share the same segment 22833, 00000, "Must cast a transient type to a persistent type" // *Cause: An attempt was made to use the transient type in the query // result. // *Action: Cast the transient type to a structurally equivalent persistent // type. 22834, 00000, "Event to turn off smon cleanup for transient types" // *Document: NO // *Cause: N/A // *Action: Turn off SMON cleanup for transient types. // 22835, 00000, "Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: %s, maximum: %s)" // *Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where // the LOB size was bigger than the buffer limit for CHAR and RAW // types. // Note that widths are reported in characters if character length // semantics are in effect for the column, otherwise widths are // reported in bytes. // *Action: Do one of the following: // 1. Make the LOB smaller before performing the conversion, // for example, by using SUBSTR on CLOB // 2. Use DBMS_LOB.SUBSTR to convert CLOB to CHAR or BLOB to RAW. 22836, 00000, "Event to turn on lob to char/raw silent truncation" // *Document: NO // *Cause: N/A // *Action: Do not throw error 22835 for truncation during LOB to CHAR/RAW // conversion. Truncate the data instead. 22837, 00000, "Relational hint or keyword is disallowed for user-level DML" // *Document: YES // *Cause: An attempt was made to use relational hint or keyword in user- // level DML. // *Action: Avoid using DML with relational hint or keyword. 22838, 00000, "Event to enable to allow user-level relational hint or keyword and direct updates on SYS_NC columns" // *Document: NO // *Cause: N/A // *Action: Do not throw error 22837 for user-level relational hint or // keyword, or 22839 for direct updating SYS_NC columns. 22839, 00000, "Direct updates on SYS_NC columns are disallowed" // *Document: YES // *Cause: An attempt was made to update SYS_NC columns directly. // *Action: Avoid direct updates on SYS_NC columns. 22840, 00000, "REF column being indexed is not scoped" // *Document: NO // *Cause: N/A // *Action: Index creation on REF column should be scoped. 22841, 00000, "DML on PL/SQL collections not supported" // *Document: NO // *Cause: An attempt was made to perform a DML operation on a collection // type in a PL/SQL block. // *Action: Feature not supported yet. 22842, 00000, "Event to enable image conversion for evolved ADT inside an AnyData column" // *Document: NO // *Cause: N/A // *Action: Convert an old version ADT image inside an AnyData column into // its most updated version. 22843, 00000, "Renaming or direct DML on out-of-line tables is not allowed." // *Document: NO // *Cause: Rename or a DML was invoked directly on out-of-line tables. // *Action: Avoid renaming out-of-line tables. Use DML on base tables. 22844, 00000, "ERROR LOGGING not supported with INSTEAD OF triggers." // *Document: NO // *Cause: ERROR LOGGING clause was not supported for DML operation // on views that have an INSTEAD OF trigger defined. // *Action: Avoid using ERROR LOGGING clause. / / / 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, SECUREFULE/BASICFILE, [A]SYNC) 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, [A]SYNC or DATA SYNC 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 (INITRANS, 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, "cannot replace a type with table dependents" // *Cause: An attempt was made to replace a type that has table dependents. // *Action: Drop all table(s) depending on the type, then retry // the operation. 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 VARRAY or LOB attributes of an object type" // *Cause: Comparison of 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 a nested table's storage table to ADD/MODIFY columns" // *Cause: An attempt was made to ADD or MODIFY columns of a nested table's // storage table. // *Action: Columns cannot be added or modified for a nested table's storage // 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, WRITE and EXECUTE 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. 22933, 00000, "cannot change object with type or table dependents" // *Cause: Attempt to replace, drop or rename an object with type // or table dependents. // *Action: Drop depending objects or use FORCE option if available. 22934, 00000, "event to store lob columns with very small headers" // *Document: NO // *Cause: N/A // *Action: Supports LOB column with small header 22935, 00000, "event to create LOBs as UCS2" // *Document: NO // *Cause: N/A // *Action: Creates LOB as UCS2 on little endian machines 22936, 00000, "cannot replace a system predefined type" // *Cause: An attempt was made to replace a system predefined type. // *Action: Use other names for newly created system types. / / 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. // / 22952, 00000, "Nested Table equality requires a map method on the element ADT" // *Cause: Nested Table equality was tried where the element ADT did not have // a map method defined on it. // *Action: Define a map method on the element ADT.. // / 22953, 00000, "Cardinality of the input to powermultiset exceeds maximum allowed" // *Cause: The cardinality of the input nested table to the powermultiset // should not exceed 32 elements // *Action: Reduce the number of elements to the input. // / 22954, 00000, "This multiset operation is not supported for this element type." // *Cause: The multiset operation attempted was not supported for the // nested table element type. // *Action: Use a supported element type. // / 22955, 00000, "The cardinality parameter is not within the allowed limits" // *Cause: The cardinality parameter has to be greater than 1 and less than // or equal to the cardinality of the input. // *Action: Give a valid cardinality value. // / 22956, 00000, "The set contains no elements" // *Cause: An empty set was given as input to the powermultiset function. // *Action: Give a non-empty set as input // / 22957, 00000, "NULL is an invalid input to powermultiset and COLLECT functions" // *Cause: NULL was given as input to the powermultiset or COLLECT function. // *Action: Give a non-null value as input // / 22958, 00000, "This operation is not allowed in check constraints or triggers" // *Cause: An invalid operation is used in a check constraint or trigger // *Action: Do not use the operation // / / 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 4000 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 | OPAQUE stored as LOB is not specified at the table level" // *Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored // as LOB at the partition/subpartition/template level. However // the VARRAY|OPAQUE column was not specified to be stored as LOB at // the table level when the table was created. // *Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table // level when the table is created. Alternatively, do not specify the // VARRAY | OPAQUE column to be stored as LOB at the // partition/subpartition/template 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, 00000, "CLOB or NCLOB data may have been corrupted" // *Cause: CLOB or NCLOB contains invalid character data. // One possible cause is that the wrong csid was specified for the // external file when calling DBMS_LOB.LOADCLOBFROMFILE or // DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from // external files. // *Action: Reload the CLOB/NCLOB data with the correct csid specified // for the external file. / / 22999 IS THE MAXIMUM ERROR NUMBER for object SQL / / / 23000 - 23299 Reserved for object Management Subsystem (OMS) / / FOR NOW 23290 to 23299 is being taken by RENAME COLUMN/CONSTRAINT / / 23290, 00000, "This operation may not be combined with any other operation" // *Cause: ALTER TABLE RENAME COLUMN/CONSTRAINT operation was given in // conjunction with another ALTER TBALE Operation. This is not // allowed. // *Action: Ensure that RENAME COLUMN/CONSTRAINT is the only operation // specified in the ALTER TABLE. / 23291, 00000, "Only base table columns may be renamed" // *Cause: Tried to rename a column of a non-base table, like object table/ // nested table/ materialized view table. // *Action: None. This is not allowed. / 23292, 00000, "The constraint does not exist" // *Cause: The given constraint name does not exist. // *Action: Give an existing constraint's name. / 23293, 00000, "Cannot rename a column which is part of a join index" // *Cause: The column participates in a join index. // *Action: If you need to rename the column, you need to drop the join index. / / / 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-23599 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 parameters. 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 parameter 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 parameter 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. // 23497, 00000, "repgroup name cannot be null" // *Cause: The array of Repgroup names contains a null value. // *Action: Ensure that the array of Repgroup names is dense and is not // null terminated. 23498, 00000, "repgroups specified must have the same masters" // *Cause: The Repgroup names specified do not have the same masters. // *Action: Ensure that the Repgroup names specified have the same masters. 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. // 23538, 00000, "cannot explicitly refresh a NEVER REFRESH materialized view (\"%s\")" // *Cause: An attempt was made to explicitly refresh a NEVER REFRESH MV. // *Action: Do not perform this refresh operation or // remove the MV(s) from the list. // 23539, 00000, "table \"%s\".\"%s\" currently being redefined" // *Cause: An attempt was made to redefine a table which is currently involved // in an ongoing redefinition. // *Action: Do not perform this redefinition operation on this table or wait // till the ongoing redefinition of the table is completed. // 23540, 00000, "Redefinition not defined or initiated" // *Cause: An attempt was made to continue or complete a redefinition which // was not defined or initiated. // *Action: Define or initiate the redefinition before performing this // operation. 23541, 00000, "tables do not match tables used while defining the redefinition" // *Cause: An attempt was made to continue or complete a redefinition by // providing different tables than those used while defining or // initiating the redefinition. // *Action: Repeat this operation and specify the same tables as those that // were specified while defining or initiating the redefinition. // 23542, 00000, "dependent object \"%s\".\"%s\" already registered" // *Cause: An attempt was made to register an already registered dependent // object to an ongoing redefinition. // *Action: Do not attempt to register an already registered dependent object // to an ongoing redefinition. // 23543, 00000, "materialized view log on \"%s\".\"%s\" is in an inconsistent state" // *Cause: There was an error while creating the materialized view log and // the log is currently in an inconsistent state. A possible cause // could be that schema redefinition has occurred on the master table // while the log was being created. Another possible cause could be // that there were DMLs being applied on the master table concurrently // in another session at the time the materialized view log creation // started and those DML transactions haven't committed even after a // very long period of time. // *Action: Drop the materialized view log and recreate it. // /////////////////////////////////////////////////////////////////////////////// // 23600-23999 Reserved for Log Based Replication PL/SQL packages /////////////////////////////////////////////////////////////////////////////// // 23600, 00000, "cannot create PROPAGATION, %s already exists" // *Cause: The propagate_name already exists. // *Action: Drop the propagate_name usign DROP_PROPAGATEcommand or // specify propagate_name. 23601, 00000, "PROPAGATION_NAME %s does not exist" // *Cause: Propagation does not exist. // *Action: Query DBA_PROPAGATION view to find existing propagation_name // 23602, 00000, "Invalid %s process type %s" // *Cause: Specified GoldenGate, XStream or Streams process type is not valid. // *Action: Specify either capture or apply. 23603, 00000, "%s enqueue aborted due to low SGA" // *Cause: An attempt to enqueue a GoldenGate, XStream or Streams message was aborted because // ORACLE is running low on memory allotted. // *Action: Either start consuming messages by enabling any GoldenGate, XStream or Streams // propagation or apply which might be disabled. // An alternative is to allot more // memory to STREAMS, which can be done by increasing the // streams_pool_size initialization parameter if one was defined // or by increasing the shared_pool_size. 23605, 00000, "invalid value \"%s\" for %s parameter %s" // *Cause: An attempt was made to specify an invalid parameter value. // *Action: Specify a valid value for the parameter. Check the documentation // for valid parameter values. 23606, 00000, "invalid object %s" // *Cause: An attempt was made to specify an invalid object. // *Action: Specify a valid object. 23607, 00000, "invalid column \"%s\"" // *Cause: An invalid column was specified in the column list. // *Action: Check the columns in the object and specify the right column name. 23608, 00000, "invalid resolution column \"%s\"" // *Cause: An invalid column was specified as the resolution column. The // resolution column must belong to the list of columns specified in // the 'column_list' parameter. // *Action: Check the columns in the column_list and specify the right // resolution column name. 23609, 00000, "unable to find directory object for directory %s" // *Cause: There was no entry in ALL_DIRECTORIES corresponding to the // specified directory. // *Action: Grant to the current user appropriate privileges on either a new // directory object or an existing directory object. 23610, 00000, "internal dbms_streams_tablespaces error: [%s] [%s] [%s] [%s]" // *Cause: Streams detected an erroneous result. // *Action: Look for information in the session trace file and contact // customer support. 23611, 00000, "tablespace \"%s\" has more than one data file" // *Cause: The specified tablespace had more than one data file and hence // did not qualify as a simple tablespace. // *Action: Choose a self-contained tablespace with a single data file, or // use a procedure that supports any tablespace. 23612, 00000, "unable to find tablespace \"%s\"" // *Cause: Either the tablespace did not exist, or the current user did // not have sufficient privileges on the tablespace. // *Action: Grant appropriate privileges on the tablespace to the current // user or choose a different tablespace. 23613, 00000, "Script %s already exists" // *Cause: A script for the specified invoking package already existed. // *Action: Complete the previous invocation or drop the previous invocation // before proceeding with the current invocation. 23614, 00000, "Script %s does not exist" // *Cause: The named script did not exist. // *Action: Create the script. 23615, 00000, "Block number %s does not exist for script %s" // *Cause: The specified block number did not exist for the script. // *Action: Add the block or check the block number and reexecute. 23616, 00000, "Failure in executing block %s for script %s with \n%s" // *Cause: The execution of specified block failed. // *Action: Check the error. Query DBA_RECOVERABLE_SCRIPT_BLOCKS to view // the failed block. Rectify and rerun the block or script. 23617, 00000, "Block %s for script %s has already been executed" // *Cause: The specified block was already executed. // *Action: Check the block number and reissue the command. 23618, 00000, "Generation of script %s is not complete." // *Cause: Script generation for the specified script was not completed in // a prior invocation. // *Action: Purge the specified script by calling the RECOVER_OPERATION API // in the package DBMS_STREAMS_ADM and reattempt the entire // operation. 23619, 00000, "non-Oracle system error: %s" // *Cause: A non-Oracle database has returned an error message to STREAMS // when attempting to apply a DML statement. The non-Oracle system // error message is a parameter to this Oracle error. // *Action: Corrective action may or may not be possible (depending on the // non-Oracle system error). If corrective action is possible, // correct the problem and try applying the transaction again. 23620, 00000, "bind value size too large for PL/SQL CALL operation" // *Cause: In a PL/SQL CALL to a stored procedure, the bind string // size exceeded 4K. // *Action: Either make the bind string size shorter (less than 4K) or use // BEGIN-END to call the procedure instead of CALL. 23621, 00000, "Operation corresponding to script %s is in progress." // *Cause: The script was already being run in a different session or was // terminated before status for the script was updated to ERROR or // EXECUTED. // *Action: Make sure the script is not being run in a parallel session. // Then call the RECOVER_OPERATION API in the DBMS_STREAMS_ADM // package with the appropriate OPERATION_MODE argument. 23622, 00000, "Operation %s.%s.%s is in progress." // *Cause: An attempt was made to execute a procedure which was being // executed in a parallel session or failed execution. // *Action: Query the DBA_RECOVERABLE_SCRIPT view to identify the operation // that is currently in progress for the specified invoking // procedure. Complete the operation before proceeding. 23623, 00000, "internal DBMS_COMPARISON error: [%s] [%s] [%s] [%s]" // *Cause: DBMS_COMPARISON detected an erroneous result. // *Action: Look for information in the session trace file and contact // Oracle Support Services. 23624, 00000, "A comparison operation is currently in progress for %s." // *Cause: Another session was already performing an operation on this object. // *Action: Retry the operation once other sessions are done with the specific // comparison object. 23625, 00000, "Table shapes of %s.%s and %s.%s@%s did not match." // *Cause: Table shapes of local and remote tables to compare did not match. // *Action: Retry by explicitly specifying columns that match in column_list // or create views on the tables as appropriate. 23626, 00000, "No eligible index on table %s.%s" // *Cause: Table did not have an eligible index to use for comparison. // *Action: For a table to be compared using DBMS_COMPARISON, the table must // have an appropriate index on a column of certain data types. // Check the documentation for supported data types. 23627, 00000, "Comparison object %s already existed." // *Cause: A comparison object by the specified name already exists. // *Action: Retry with a different name. // 23628, 00000, "Comparison query too long (actual %s, allowed %s)." // *Cause: A generated query for comparison was too long. // *Action: Comparison is unsupported for very large tables with long column // names. Retry with a subset of columns or with shorter column names. // 23629, 00000, "%s.%s is not an eligible index on table %s.%s for comparison" // *Cause: The specified index was not an eligible index to use for // comparison. // *Action: For a table to be compared using DBMS_COMPARISON, the table must // have an appropriate index. Please specify an eligible index for the // table to be compared. 23630, 00000, "Cannot switch to apply-state checkpoint mode (value \"%s\", %s parameter %s), due to the following reason:" // *Cause: Could not switch to apply-state checkpoint mode, or already in // apply-state checkpoint mode. // *Action: Can switch to apply-state checkpoint mode only if the capture is new // (it never ran), the capture wasn't cloned from a capture with // checkpoints, the capture doesn't include any extra attributes, // and combined capture and apply is enabled. // 23631, 00000, "apply-state checkpoint mode cannot change (value \"%s\", %s parameter %s)" // *Cause: Could not switch to checkpoints because apply-state checkpoint mode // was set. // *Action: Drop the apply-state checkpoint capture and create a new one that will /// take checkpoints. // 23632, 00000, "Cannot force checkpoints in apply-state checkpoint mode (value \"%s\", %s parameter %s)" // *Cause: The capture process was in apply-state checkpoint mode. // *Action: Cannot take checkpoints in apply-state checkpoint mode. // 23633, 00000, "Cannot turn off combined capture and apply mode in apply-state checkpoint mode (value \"%s\", %s parameter %s)" // *Cause: The capture was running in apply-state checkpoint mode and had to run in // combined capture and apply mode also. // *Action: Ensure that this capture runs in combined capture and apply // by dropping additional propagation or apply processes for the same // queue. // 23634, 00000, "Cannot include extra attributes in apply-state checkpoint mode" // *Cause: The capture process was in apply-state checkpoint mode. // *Action: Extra attributes are not supported in apply-state checkpoint mode. // 23635, 00000, "MAINTAIN_TTS: tablespace(s) already exist(s) in target database." // *Cause: The tablespaces were already in existence in the target database // when the streams MAINTAIN_TTS APIs were called." // *Action: Check whether you can drop the tablespaces to be maintained in the // target database. If not, don't use streams MAINTAIN_TTS APIs to // setup streams. Check the Oracle documentation on how to setup // streams. 23636, 00000, "MAINTAIN_TTS: Invalid tablespace name, reason: %s." // *Cause: The tablespace name was either NULL or too long when the streams // MAINTAIN_TTS APIs were called. // *Action: Check that the specified tablespace names are not NULL and are // spelled correctly. If there are too many tablespaces, group them // together and call the streams MAINTAIN_TTS APIs for the group. // 23637, 00000, "Capture started in checkpoint mode" // *Cause: // *Action: 23638, 00000, "Capture cloned from a capture with checkpoints" // *Cause: // *Action: 23639, 00000, "Extra Attribute included" // *Cause: // *Action: 23640, 00000, "Combined capture and apply disabled" // *Cause: // *Action: 23641, 00000, "Capture started in apply-state checkpoint mode already" // *Cause: // *Action: 23642, 00000, "Cannot switch to checkpoint mode (value \"%s\", %s parameter %s)" // *Cause: Capture was cloned from a capture in apply-state checkpoint mode. // *Action: Clone from a capture with checkpoints. 23643, 00000, "Capture cloned from a capture in apply-state checkpoint mode" // *Cause: // *Action: 23644, 00000, "Cannot switch to apply-state checkpoint mode (Capture %s)" // *Cause: Switch to apply-state checkpoint mode was prevented by a previous error. // *Action: See the previous error for the appropriate action. 23645, 00000, "Cannot switch to checkpoints (Capture %s)" // *Cause: Switch to checkpoints was prevented by a previous error. // *Action: See the previous error for the appropriate action. 23646, 00000, "%s %s process %s does not exist" // *Cause: Capture or Apply did not exist. // *Action: Create a Capture or Apply process, then try again. 23647, 00000, "%s %s process %s is not running" // *Cause: Capture or Apply were not running. // *Action: Start Capture or Apply process, then try again 23648, 00000, "Capture %s is for Change Data Capture" // *Cause: Capture was for Change Data Capture, and checkpoints were required. // *Action: None. 23649, 00000, "Capture %s is for Audit Vault" // *Cause: Capture was for Audit Vault, and checkpoints were required. // *Action: None. 23650, 00000, "No progress Capture %s" // *Cause: Capture was not capturing changes. // *Action: Make sure Capture is running and capturing changes. 23651, 00000, "Capture %s is already in %s mode" // *Cause: Capture was already in the desired mode. // *Action: None. 23652, 00000, "The oldest SCN could not be updated at Apply %s" // *Cause: The oldest SCN was not updated before the switch was performed. // *Action: Make sure Apply is running and the switch package version is // the same at both databases. 23653, 00000, "LogMiner session does not exist" // *Cause: LogMiner session did not exist. // *Action: Make sure the Capture process exists. 23654, 00000, "Attempting to set the oldest SCN to a greater value (%s) than the current one (%s) at Apply %s" // *Cause: The new value for the oldest SCN was not computed correctly. // *Action: Make sure Capture and Apply are running, and Capture is // making progress. 23655, 00000, "The SCN range cannot be smaller than 0, (SCN range = %s)" // *Cause: The function was invoked with a negative SCN range. // *Action: Use a positive SCN range. 23656, 00000, "Timeout occurred while %s %s process %s" // *Cause: The GoldenGate, XStream or Streams process could not be stopped or started. // *Action: Call the switch procedure again. 23657, 00000, "the converted file %s already exists" // *Cause: The converted file was already in existence. // CONVERT FILE call does not overwrite the existing file. // *Action: Check whether the existing file can be deleted. // If the existing file can be deleted, delete it. Otherwise, // specify a different directory or file extension. 23658, 00000, "Invalid character set specified when converting column '%s' in '%s.%s'" // *Cause: The conversion between two character sets for the column in the given table // is not supported. // *Action: Check if the implicit conversion between source and destination column // is supported. 23659, 00000, "Destination buffer is not large enough when converting column '%s' in '%s.%s' (actual length: %s; maximum length: %s)" // *Cause: The conversion between two character sets failed because a source column // value is too large for the destination column. // *Action: Check if size of the source and destination column matches. 23660, 00000, "Unable to load NLS data object when converting column '%s' in '%s.%s'" // *Cause: It may be caused by invalid NLS environment setting. // *Action: Check your NLS environment setting. 23661, 00000, "Canon capture name \"%s\" not found" // *Cause: There's no such capture process // *Action: Pass the right parameter to the function 23662, 00000, "subset rule length exceeds maximum allowed value" // *Cause: The length of an insert, update, or delete subset rule computed // from the DML condition input exceeded the maximum allowed length. // *Action: Make the DML condition shorter. 23663, 00000, "local object %s.%s is not a single table view" // *Cause: The view was based either on another view or multiple tables or // views. // *Action: For comparison, specify a view based on a single table. 23664, 00000, "remote object %s.%s is not a single table view" // *Cause: The view was based either on another view or multiple tables or // views. // *Action: For comparison, specify a view based on a single table. 23665, 00000, "DML conflict handler \"%s\" not found" // *Cause: The DML conflict handler was not found for modification or removal. // *Action: Make sure the name of the conflict handler is correct and that it // exists. 23666, 00000, "Default column group in use by DML conflict handler \"%s\"" // *Cause: A default column group was found for the specified Apply name, // operation name, and conflict type. // *Action: Remove the existing default column group and retry. 23667, 00000, "Column \"%s\" already used by conflict handler \"%s\"" // *Cause: The column was already in the column group of another conflict // handler for the specified Apply name, operation name, and conflict // type. // *Action: Remove the column from the other conflict handler or specify a // different column. 23668, 00000, "Column \"%s\" does not have a numeric data type." // *Cause: The specified column did not have a numeric data type. Delta // conflict resolution requires numeric columns. // *Action: Check the data type of the column and specify only numeric columns. 23669, 00000, "Duplicate conflict handler name" // *Cause: A DML conflict handler with the specified name was found. // *Action: Remove the current DML conflict handler or specify a different // name. 23670, 00000, "Duplicate column name \"%s\"" // *Cause: The specified value was duplicated in the column group list. // *Action: Remove duplicated entries from the column group list. 23671, 00000, "Default column group required" // *Cause: A default column group was not specified. The specified Apply name, // operation name, and conflict type is only supported on default // column groups. // *Action: Specify a default column group. 23672, 00000, "Column not specified in column group for DML conflict handling for table \"%s\".\"%s\"" // *Cause: The specified table contained a column that was not specified as // part of a column group. // *Action: Add the column to a column group. 23673, 00000, "Invalid resolution column \"%s\" for table \"%s\".\"%s\"" // *Cause: The specified resolution column was not valid. // *Action: Set the resolution column to a valid column. 23674, 00000, "Unable to handle delta conflict resolution for table \"%s\".\"%s\"" // *Cause: The specified table or the LCR contained a null value in one of the // columns belonging to a delta conflict group. // *Action: Correct each delta column in the table or the error LCR if it // currently has a null value. 23675, 00000, "Unsupported OPERATION_NAME, CONFLICT_TYPE, and METHOD_NAME" // *Cause: The specified OPERATION_NAME, CONFLICT_TYPE, and METHOD_NAME was // not a valid set of parameters. // *Action: Retry with a valid set of parameters. /////////////////////////////////////////////////////////////////////////////// // 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, "Inappropriate utilities used to perform DDL on AQ table %s.%s" // *Cause: An attempt was made to use the SQL command DROP TABLE or TRUNCATE // TABLE or ALTER TABLE on queue metadata or tables. // *Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE to DROP TABLE, // DBMS_AQADM.PURGE_QUEUE_TABLE to TRUNCATE TABLE. // ALTER TABLE redefinition based on only ALTER_TABLE_PROPERTIES and // ALTER_TABLE_PARTITIONING clauses are allowed. // 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 24029, 00000, "operation not allowed on a single-consumer queue" // *Cause: Tried an operation not allowed on a single-consumer queue. // *Action: Specify the operation on a multi-consumer queue. 24030, 00000, "Only one of rule or rule-set must be specified" // *Cause: Specified both a rule and rule-set for the operation. // *Action: Specify only one of rule or rule-set. 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 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 attribute. Propagation of object type payloads // that have a REF 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 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 or rules associated with queue subscribers got altered or dropped. // *Action: Drop the queue table setting the force option to true. 24086, 00000, "cannot create a 8.0 compatible %s queue" // *Cause: An attempt was made to create a 8.0 compatible queue table and // enable a feature that is supported only on 8.1 style queue tables // *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, "AQ Agent %s does not exist" // *Cause: This AQ Agent does not exist // *Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view // for a list of valid aq agents // 24089, 00000, "AQ Agent %s already exists" // *Cause: This AQ agent has already been created // *Action: Specify another agent name or use the ALTER api to modify the agent // 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. // 24091, 00000, "Destination queue %s is the same as the source queue" // *Cause: Propagation cannot be scheduled when the destination queue is the // same as the source queue. // *Action: Specify a different destination queue. 24092, 00000, "invalid value %s specified" // *Cause: A queue, queue table, rule, or ruleset name that requires double // quotes was specifed when the database compatibility was less // than 10.0. // *Action: Specify a value that does not require double quotes and // retry the operation. / 24093, 00000, "AQ agent %s not granted privileges of database user %s" // *Cause: The specified AQ agent does not have privileges of the // specified database user // *Action: Specify a valid combination of AQ agent and database user. Check // the DBA_AQ_AGENT_PRIVS or USER_AQ_AGENT_PRIVS view for user/agent // mappings // 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: // / 24101 - 24119 ERROR MESSAGES FOR THE DBMS_SCHEDULER PACKAGE / 24101, 00000, "stopped processing the argument list at: %s" // *Cause: One of the arguments of the requested operation contained a list of // scheduler objects. While processing this list an error was // encountered with the specified item. // *Action: Resolve the error for this element of the list and then re-issue // the command with the remainder of the argument list. See the rest // of the error stack to find out what the exact error is. 24102, 00000, "invalid prefix for generate_job_name" // *Cause: generate_job_name was called with a prefix longer than 18 characters // or a prefix ending in a digit. // *Action: Re-issue the command using a prefix no longer than 18 characters // and not ending in a digit. / / 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 - 24179 ERROR MESSAGES FOR THE DBMS_RULE PACKAGE / 24141, 00000, "rule set %s.%s 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 evaluation context name" // *Cause: An attempt to create a rule/ruleset on an invalid evaluation name // was made. The evaluation_context can not be more than 30 // characters. The evaluation context with the name specified must // exist. // *Action: Retry the create with a valid evaluation context 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. 24145, 00000, "evaluation context %s.%s already exists" // *Cause: An evaluation context of the given name already exists // *Action: Specify another name for the evaluation context being created 24146, 00000, "rule %s.%s already exists " // *Cause: A rule of the given name already exists // *Action: Specify another name for the rule being created. 24147, 00000, "rule %s.%s does not exist " // *Cause: The rule of the given name does not exist // *Action: create the rule or specify one that exists 24148, 00000, "cannot drop rule %s.%s with dependents" // *Cause: The rule still belongs to some rulesets, cannot be dropped // *Action: do not drop a rule that belongs to rulesets without force option 24149, 00000, "invalid rule name" // *Cause: An attempt to create a rule with an invalid name was made. // The rule name can not be NULL, and can not be more // than 30 characters 24150, 00000, "evaluation context %s.%s does not exist" // *Cause: The evaluation context of the given name does not exist // *Action: create the evaluation context or specify one that exists 24151, 00000, "no evaluation context is associated with rule %s.%s or rule set %s.%s" // *Cause: Whening adding a rule to a rule set, either the rule or the rule // set must have an evaluation context associated with it // *Action: do not add a rule without an evaluation context to a ruleset that // does not have a default evaluation context 24152, 00000, "cannot drop evaluation context %s.%s with dependents" // *Cause: The evaluation context still belongs to some rules or rule sets, // cannot be dropped // *Action: do not drop an evaluation context with dependents without force // option 24153, 00000, "rule set %s.%s already exists " // *Cause: A rule set of the given name already exists // *Action: Specify another name for the rule set being created. 24154, 00000, "rule %s.%s already in rule set %s.%s" // *Cause: a rule can be added to a rule set only once // *Action: do not add a rule to a rule set that already contains this rule 24155, 00000, "rule %s.%s not in rule set %s.%s" // *Cause: the rule to be removed from the rule set is not in the rule set // *Action: do not remove a rule from a rule set that does not contain the rule 24156, 00000, "duplicate table alias %s" // *Cause: there is a table alias of the same name in the evaluation context // *Action: do not add two table aliases of the same name to an evaluation // context 24157, 00000, "duplicate variable name %s" // *Cause: there is a variable of the same name in the evaluation context // *Action: do not add two variables of the same name to an evaluation // context 24158, 00000, "invalid table alias" // *Cause: table alias name or base table name is not specified in the table // alias definiton // *Action: specify both alias name and alias base table in the table alias // structure 24159, 00000, "invalid variable definiton" // *Cause: variable name or variable type is not specified in the variable // definiton // *Action: specify both variable name and variable type in the variable // definition structure 24160, 00000, "name %s already exists in the name value pair list" // *Cause: there is already a name-value pair with the same name in the NVlist // *Action: try another name. 24161, 00000, "name %s does not exist in the name value pair list" // *Cause: there is not such a name-value pair in the NVlist // *Action: check the name-value pair exists in the NVList. 24162, 00000, "name value pair list is full, cannot add another entry" // *Cause: The NVList is full (1024 elements) and cannot hold more elements // *Action: do not add elements to a full list. 24163, 00000, "dblink is not supported in rules engine DDLs" // *Cause: the object name has a database link in it, which is not supported // *Action: Do not specify remote objects in rules engine DDLs. 24164, 00000, "invalid rule engine system privilege: %s" // *Cause: no such system privilege number for rule engine objects // *Action: check specfication of dbms_rule_adm for valid system privilege // numbers 24165, 00000, "invalid rule engine object privilege: %s" // *Cause: no such object privilege number for rule engine objects // *Action: check specfication of dbms_rule_adm for valid object privilege // numbers 24166, 00000, "evaluation context %s.%s has errors" // *Cause: cannot resolve the table aliases and the variable types specified // in the evaluation context // *Action: make sure all base tables exist and all variable types correct 24167, 00000, "incompatible rule engine objects, cannot downgrade" // *Cause: there are rule engine objects in the database that cannot be // downgraded. // *Action: check utlincmp.sql and remove all incompatible rules engine objects // before downgrade. 24168, 00000, "rule %s.%s cannot have default evaluation context" // *Cause: If a rule is added to a rule set with more than one evaluation // contexts, it must not have an evaluation context itself. // *Action: Do not set the evaluation context of such rules to a not-null // value 24169, 00000, "rule condition has unrecognized variables" // *Cause: The rule references variables not in the evaluation context. // *Action: Modify the rule condition to remove illegal reference. 24170, 00000, "%s.%s is created by AQ, cannot be dropped directly" // *Cause: This object is created by AQ, thus cannot be dropped directly // *Action: use dbms_aqadm.drop_subscriber to drop the object 24171, 00000, "creation properties are only for internal use" // *Cause: user specified not null creation properties when creating rules // engine objects, which are not for external use // *Action: do not set creation properties when creating rules engine objects 24172, 00000, "rule set %s.%s has errors" // *Cause: The rule references variables not in the evaluation context. // *Action: Modify the rule condition to remove illegal reference. 24173, 00000, "nested query not supported for rule condition" // *Cause: user specified nested query in rule condition. // *Action: do not use nested query in rule condition. 24174, 00000, "The number of %s per evaluation context is more than %s" // *Cause: Number of tables or variables were more than the defined // upper limit. // *Action: Reduce the number of tables or variables per evaluation context. 24175, 00000, "The number of %s exceeds limit %s as there exists at least one nonsimple rule condition" // *Cause: Upper limit of tables or variable per evaluation context exceeded // as there exists at least one nonsimple rule condition. // *Action: Reduce the number of tables or variables per evaluation context. / / / 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: The named transformation already exists. // *Action: Specify another name for the transformation being created. 24185, 00000, "transformation %s.%s does not exist" // *Cause: The specified transformation 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. / / 24190 - 24199 ERROR MESSAGES FOR AQ JMS / 24190, 00000, "length of payload exceeds %s" // *Cause: the length of payload being taken exceeds the limit of varchar2 or raw. // *Action: use clob type or blob type to call get_text or get_bytes. 24191, 00000, "the property name %s has existed" // *Cause: the property name being set has existed. // *Action: use another property name. 24192, 00000, "the property name cannot be null" // *Cause: the property name cannot be null. // *Action: make sure the property name not null. 24193, 00000, "the property value exceeds the valid range %s" // *Cause: the property valus being set exceeds the valid range. // *Action: make sure the property value is within the valid range. 24194, 00000, "attempt to read data in a message as the wrong type" // *Cause: According to JMS specification, some type conversions were not allowed. // *Action: Make sure to use the correct READ function to retrieve message data. 24195, 00000, "attemp to retrieve the name list of a map message with size exceeding 1024" // *Cause: The GET_NAMES function returns the names in a varray with a size limit of 1024. // *Action: Retrieve in several smaller steps using the GET_NAMES function with OFFSET and LENGTH parameters. 24196, 00000, "access the message in a wrong access mode" // *Cause: StreamMessage and BytesMessage could not be read when they were in write only mode and vice versa. // *Action: Change the access mode using PREPARE, CLEAR_BODY and RESET procedures. 24197, 00000, "JAVA stored procedure throws JAVA exceptions" // *Cause: The JAVA stored procedure threw some exceptions that could not be catergorized. // *Action: Use GET_EXCEPTION procedure to see what the exception is about. 24198, 00000, "attempt to use an invalid operation ID" // *Cause: An attempt was made to use an invalid operation ID to access messages. // *Action: Use the correct operation ID returned by PREPARE or CLEAR_BODY procedure. 24199, 00000, "message store is overflow" // *Cause: An attemp was made to access too many messages at the same time. // *Action: Use the CLEAN procedure to clean up some of the messages. / / 24200 - 24229 ERROR MESSAGES FOR THE DBMS_AQADM PACKAGE / 24201, 00000, "duplicate publisher, publisher already added to the queue" // *Cause: Attempted to add a publisher to the queue again. // *Action: Specify another publisher or user DBMS_AQADM.ALTER_PUBLISHER // to alter the publisher's properties. 24202, 00000, "publisher does not exist for the queue" // *Cause: Attempted to alter or drop a non existent publisher from a queue. // *Action: Specify another publisher. // 24203, 00000, "operation failed, queue table %s.%s has errors" // *Cause: An operation attempt was made to a queue table which has errors. // *Action: Drop the queue table setting the force option to true. // 24204, 00000, "existing %s propagation schedules" // *Cause: A propagation administrative interface was called when the // existing propagation schedules were running in different // mode (10.2/11g). // *Action: Set appropriate internal parameter and unschedule existing // schedules if required. / / 24230 - 24264 ERROR MESSAGES FOR MISC DBMS_ PACKAGES / 24230, 00000, "input to DBMS_DDL.WRAP is not a legal PL/SQL unit" // *Cause: The input supplied to DBMS_DDL.WRAP or DBMS_DDL.CREATE_WRAPPED // did not specify a legal PL/SQL package specification, // package body, type specification, type body, function or // procedure. This error can occur if you used incorrect // syntax in the CREATE OR REPLACE statement or specified // a unit that cannot be wrapped (e.g., a trigger or anonymous // block). // *Action: Provide a legal PL/SQL unit as input. // 24231, 00000, "database access descriptor (DAD) %s not found" // *Cause: The specified Database Access Descriptor (DAD) did not exist. // *Action: Make sure the name of the Database Access Descriptor (DAD) is // correct and the DAD exists. // 24232, 00000, "unknown Embedded PL/SQL Gateway attribute %s" // *Cause: The specified Embedded PL/SQL Gateway attribute was not known. // *Action: Make sure the name of the Embedded PL/SQL Gateway attribute is // correct. // 24233, 00000, "argument passed to DBMS_UTILITY.VALIDATE is not legal" // *Cause: One or more input arguments to the DBMS_UTILITY.VALIDATE // routine was not legal. This error occurred because the // object name or owner or namespace arguments (if specified) // were NULL or illegal. // *Action: Identify and correct the illegal argument. / 24234, 00000, "unable to get source of %s \"%s\".\"%s\", insufficient privileges or does not exist" // *Cause: The specified PL/SQL object in a DBMS_PREPROCESSOR subprogram // did not exist or you did not have the privileges necessary to // view its source. // *Action: Make sure the specified object exists and you have the // privileges necessary to view its source. / 24235, 00000, "bad value for object type: %s" // *Cause: The specified object type was not appropriate. // *Action: Make sure the specified object type is one of the following: // package, package body, procedure, function, trigger, type, // and type body. / 24236, 00000, "source text is empty" // *Cause: The input source text supplied to a DBMS_PREPROCESSOR // subprogram was empty. // *Action: Pass a non-empty input source text as the input. / 24237, 00000, "object id argument passed to DBMS_UTILITY.INVALIDATE is not legal" // *Cause: This error occurred because the p_object_id argument passed to // the DBMS_UTILITY.INVALIDATE routine was NULL, there was no // object with the specified object id, or the user calling the // routine did not have sufficient privileges to invalidate the // object. // *Action: Correct the illegal argument. / 24238, 00000, "object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal" // *Cause: This error occurred because the p_plsql_object_settings argument // passed to the DBMS_UTILITY.INVALIDATE routine was NULL or // malformed. // *Action: Correct the illegal argument. / 24239, 00000, "object could not be invalidated" // *Cause: A call to the DBMS_UTILITY.INVALIDATE routine failed. This error // occurred because the object type of the object specified by the // p_object_id argument is not one of the types that can be handled // by this routine. Alternately, the object was an object type // specification with table dependents, or the object was the // specification of the STANDARD, DBMS_STANDARD, DBMS_UTILITY // package, or the body of the DBMS_UTILITY package. // *Action: Call DBMS_UTILITY.INVALIDATE only on supported object types. / 24240, 00000, "invalid database access descriptor (DAD) name" // *Cause: The specified Database Access Descriptor (DAD) name was invalid. // *Action: Make sure the name of the Database Access Descriptor (DAD) is // valid and its length does not exceed its limit. / 24241, 00000, "source text is in wrapped format" // *Cause: The input source text supplied to a DBMS_PREPROCESSOR // subprogram was in wrapped format. // *Action: Pass a nonwrapped source text as the input. // / 24242, 00000, "anonymous access through a dynamically authenticated Database Access Descriptor (DAD) prohibited" // *Cause: An attempt to allow anonymous access through a dynamically // authenticated Database Access Descriptor (DAD) was prohibited. // *Action: Make sure the Database Access Descriptor (DAD) is not dynamically // authenticated before allowing anonymous access through it. / 24243, 00000, "access control entry (ACE) already exists" // *Cause: An access control entry (ACE) for the principal with the same // grant or deny attribute in the IS_GRANT argument already existed. // *Action: Add the privilege to the existing access control entry (ACE) // instead. / 24244, 00000, "invalid host or port for access control list (ACL) assignment" // *Cause: The host or port to which the access control list (ACL) was // assigned was invalid. // *Action: Ensure the host and port to which you are assigning the access // control list (ACL) are valid. / 24245, 00000, "invalid network privilege" // *Cause: The network privilege being added to the access control list // (ACL) was invalid. // *Action: Ensure the network privilege that you are adding to the access // control list (ACL) is valid. / 24246, 00000, "empty access control list (ACL) not allowed" // *Cause: An attempt was made to store an empty access control list (ACL). // *Action: Ensure that the access control list (ACL) has at least one / privilege assignment. / 24247, 00000, "network access denied by access control list (ACL)" // *Cause: No access control list (ACL) has been assigned to the target // host or the privilege necessary to access the target host has not // been granted to the user in the access control list. // *Action: Ensure that an access control list (ACL) has been assigned to // the target host and the privilege necessary to access the target // host has been granted to the user. / 24248, 00000, "XML DB extensible security not installed" // *Cause: XML DB extensible security necessary for this operation has // not been installed. // *Action: Ensure that XML DB has been installed. / 24249, 00000, "Authentication scheme \"%s\" not supported" // *Cause: An unsupported authentication scheme was used. // *Action: Retry with a supported authentication scheme. / 24250, 00000, "No supported authentication scheme found" // *Cause: A supported authentication scheme was not found. // *Action: Retry with a supported authentication scheme. / 24251, 00000, "This statement is not supported by EXPAND_SQL_TEXT." // *Cause: EXPAND_SQL_TEXT did not support the specified statement. // EXPAND_SQL_TEXT supports only SELECT statements. // *Action: Submit only a SELECT statement. / / 24265 - 24269 ERROR MESSAGES FOR THE DBMS_SQLTUNE PACKAGE / 24265, 00000, "Insufficient privileges for SQL profile operation" // *Cause: A DDL operation was attempted on a SQL profile by a session without // the proper privileges. // *Action: Grant the user the appropriate privilege. / / 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. 24277, 00000, "invalid database link %s " // *Cause: The database link did not exist. // *Action: Make sure the database link name is correct. 24278, 00000, "remote table %s not found " // *Cause: The table did not exist in the remote database. // *Action: Make sure the remote table name is correct. 24279, 00000, "view %s is not a parallel access view" // *Cause: The view was not created by CREATE_OR_REPLACE_VIEW API. // *Action: Provide the correct view name that was created by CREATE_OR_REPLACE_VIEW API. / / / / 24280 -24290 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. / / 24291 - 24299 Reserved for Sorted Hash Clusters / 24291, 00000, "Sort Hash Cluster error %s" // *Cause: // *Action: / 24292, 00000, "no more tables permitted in this sorted hash cluster" // *Cause: A sorted hash cluster only supports a maximum of 2 tables // *Action: / 24295, 00000, "max key length (%s) for sorted hash cluster exceeded" // *Cause: Sorted hash clusters have a maximum key size // *Action: / / / 24300 - 24999 Reserved for OCI/UPI/TTC/OPI/RPI/PSDs etc / / 24500 - 24549 Reserved for OCI codepoint length semantics and UTF16 / 24550 - 24574 Reserved for OCI et al Diagnosability / 24750 - 24800 Reserved for Transaction OCI / 24800 - 24849 Reserved for OCI Lob/File related Calls / 24850 - 24874 Reserved for Shared OCI / 24900 - 24939 Reserved for OCI Notification / 24940 - 24949 Reserved for Generic 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 or OCI_ROWCBK_DONE. Any other value // will cause this error. // *Action: Please insure that OCI_CONTINUE or OCI_ROWCBK_DONE 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 OCI 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. / / Session Pooling OCI error messages / 24411, 00000, "Session pool already exists." // *Cause: A session pool has already been created for the specified // pool handle. // *Action: 1) Specify a different pool handle to create a new session pool. // 2) If you wish to modify the pool parameters, call // OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode. 24412, 00000, "Cannot reinitialize non-existent pool" // *Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this // pool handle. // *Action: Create a session pool prior to reinitializing it. 24413, 00000, "Invalid number of sessions specified" // *Cause: An invalid combination of minimum, maximum and increment number // of sessions was specified in the OCISessionPoolCreate call. // *Action: Specify a valid combination of parameters. 24414, 00000, "Only %d sessions could be started." // *Cause: The number of sessions specified by the minSess parameter of // OCISessionPoolCreate could not be started, possibly because the // value supplied was larger than that supported by the server." // *Action: This is a warning. Check the maximum number of sessions allowed // on the server. 24415, 00000, "Missing or null username." // *Cause: Username and password must be specified when pool is created in // this mode. // *Action: Specify a valid username and password. 24416, 00000, "Invalid session Poolname was specified." // *Cause: An attempt was made to use a Session Pool that does not exist. // *Action: Create a Session Pool before using it. 24417, 00000, "Session pool size has exceeded the maximum limit" // *Cause: The number of sessions has exceeded the maximum size of the // Session Pool. // *Action: This is a warning. You can tune the session pool with // appropriate minimum and maximum parameters. 24418, 00000, "Cannot open further sessions." // *Cause: Sufficient number of sessions are not present in the pool to // execute the call. No new sessions can be opened as the // sessMax parameter supplied in OCISessionPoolCreate has been // reached. // *Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and // increase the value of the sessMax parameter. 24419, 00000, "Proxy sessions are not supported in this mode." // *Cause: A proxy session was requested for from a Session Pool which does // not support proxy sessions. // *Action: Do not specify mode OCI_CRED_PROXY. 24420, 00000, "OCISessionRelease must be used to release this session." // *Cause: The session was retrieved using OCISessionGet, and an attempt // has been made to release it using a call other than // OCISessionRelease. // *Action: Call OCISessionRelease. 24421, 00000, "OCISessionRelease cannot be used to release this session." // *Cause: The session was not retrieved using OCISessionGet, and an attempt // has been made to release it using OCISessionRelease. // *Action: Release the session using an appropriate call. 24422, 00000, "error occurred while trying to destroy the Session Pool" // *Cause: An attempt was made to destroy the session pool while some // sessions in the pool were busy. // *Action: Ensure that no sessions from the pool are being used OR call // OCISessionPoolDestroy with mode set to OCI_SPD_FORCE. / / ROWID define at position 0 - OCI error messages / 24423, 00000, "Cannot set the ROWID attribute - OCI_ATTR_FETCH_ROWID" // *Cause: An attempt was made to set the implicit ROWID attribute. // *Action: Use a SELECT ... FOR UPDATE statement that has not previously been // described or executed before setting this ROWID attribute. 24424, 00000,"Invalid attempt to define at position 0" // *Cause: An invalid attempt was made to call OCIDefineByPos for position 0. // *Action: Ensure that the implicit ROWID attribute, OCI_ATTR_FETCH_ROWID, is // set on the statement handle before doing the execute. 24425, 00000,"Invalid mode passed when defining at position 0" // *Cause: An invalid mode was passed to OCIDefineByPos. // *Action: Ensure a valid mode is passed to OCIDefineByPos when defining // at position 0. / / Error message for tracing OCI Session pool. / 24426, 00000, "Event to enable tracing in OCI Session Pool" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to obtain trace information // for OCI Session Pool. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / / OCISessionGet in pooled mode with security attrs 24427, 00000, "Invalid attributes on user handle" // *Cause: Some of the attributes set on the user handle were not allowed in // pooled mode. // *Action: Unset the attributes on the user handle and call OCISessionGet or // use sessions that are not pooled. 24428, 00000, "Sessions with SYSDBA privileges are not supported in this mode." // *Cause: A session with SYSDBA privileges was requested from a Session Pool // which does not support sessions with SYSDBA privileges. // *Action: Do not specify mode OCI_SESSGET_SYSDBA. 24429, 00000, "External authentication is not supported in this mode." // *Cause: An externally authenticated session was requested from a Session // Pool which does not support external authentication. // *Action: Do not specify mode OCI_SESSGET_CREDEXT. / / / Statement Caching OCI error messages / 24430, 00000, "Null values for sqltext and key were specified." // *Cause: An attempt was made to call OCIStmtPrepare2 and neither // sqltext nor key were specified. // *Action: Specify valid values for sqltext or key or both. 24431, 00000, "Statement does not exist in the cache" // *Cause: The statement that was requested for does not exist in the // statement cache. // *Action: Please request for a valid statement. 24432, 00000, "The statement that was returned is not tagged." // *Cause: A tagged statement was requested for, but an untagged statement // has been returned. // *Action: This is a warning. Please modify and tag the statement as // desired. 24433, 00000, "This statement has already been prepared using OCIStmtPrepare2." // *Cause: A statement that was earlier prepared using OCIStmtPrepare2 is // now being reprepared using OCIStmtPrepare." // *Action: Please use a different statement handle. 24434, 00000, "OCIStmtRelease called before OCIStmtPrepare2." // *Cause: An attempt was made to release a statement without first // preparing it using OCIStmtPrepare2. // *Action: Call OCIStmtPrepare2 before OCIStmtRelease. 24435, 00000, "Invalid Service Context specified." // *Cause: The statement was prepared using a service context that is // different from the one specified in OCIStmtExecute. // *Action: Please specify the same service context that the statement // was prepared with. 24436, 00000, "Invalid statement Handle." // *Cause: OCIHandleFree called on a statement that was prepared using // OCIstmtPrepare2. // *Action: Release the statement using OCIStmtRelease. 24437, 00000, "OCIStmtExecute called before OCIStmtPrepare2." // *Cause: An attempt was made to execute a statement without first // preparing it using OCIStmtPrepare2. // *Action: Call OCIStmtPrepare2 before OCIStmtExecute. 24438, 00000, "Invalid Authentication Handle specified." // *Cause: The statement was prepared using an authentication handle // that is different from the one specified in OCIStmtExecute. 24439, 00000, "success with PLSQL compilation warning" // *Cause: A plsql compilation warning occurred. // *Action: Return OCI_SUCCESS_WITH_INFO along with the error code. 24440, 00000, "OCI Easy Install mode cannot be initialized" // *Cause: An internal OCI error has occurred. // *Action: Please contact Oracle customer support. // 24441, 00000, "Invalid cookie, resend sql text" // *Cause: An internal OCI error has occurred. // *Action: Please contact Oracle customer support. // 24450, 00000, "Cannot pre-process OCI statement" // *Cause: An error occured during statement pre-processing. // E.g., SQL statement has invalid usage of N' or Q' literals. // *Action: Correct the SQL statement. // 24451, 00000, "%s, Maximum call depth exceeded" // *Cause: Your program has too many levels of recursion. // *Action: Restructure your program to eliminate some levels of recursion. // / 24460 - 24470 Reserved for OCI Native Net / 24460, 00000, "Native Net Internal Error" // *Cause: Internal error . // *Action: This error should not normally occur. If it persists, // please contact your customer service representative. / / 24471 - 24479 Reserved for OCI Objects / 24471, 00000, "KOH tracing event" // *Document: NO // *Cause: N/A // *Action: Event to trace KOH memory events // bit 0x1: KOH_TRACE_LEVEL_MEM: trace memory alloc and free // bit 0x2: KOH_TRACE_LEVEL_DUR: trace duration start & end // bit 0x4: KOH_TRACE_LEVEL_ZEROCACHE: cache max & opt size = 0 // bit 0x8: KOH_TRACE_LEVEL_KOHIH: trace duration list mgmt // bit 0x10: KOH_TRACE_LEVEL_INS: dump memory or instance / 24472, 00000, "KOC tracing event" // *Document: NO // *Cause: N/A // *Action: Event to trace KOC cache events // bit 0x1: KOC_TRACE_EVENT_PIN: trace pin operations // bit 0x2: KOC_TRACE_EVENT_DUR: trace duration operations // bit 0x4: KOC_TRACE_EVENT_TXN: trace transaction operations / 24473, 00000, "KOD tracing event" // *Document: NO // *Cause: N/A // *Action: Event to trace KOD data events // bit 0x1: KOD_TRACE_EVENT_PIC: trace pickle operations // bit 0x2: KOD_TRACE_EVENT_UPIC: trace unpickle operations // bit 0x4: KOD_TRACE_EVENT_TYPE: trace pickle/unpickle a type // bit 0x00004000: KOD_TRACE_LEVEL_MEDIUM: generate medium amount of tracing // bit 0x00008000: KOD_TRACE_LEVEL_HIGH: generate high amount of tracing / 24474, 00000, "KOL tracing event" // *Document: NO // *Cause: N/A // *Action: Event to trace KOL collection events // bit 0x1: KOL_TRACE_EVENT_PIC: trace pickle operations // bit 0x2: KOL_TRACE_EVENT_UPIC: trace unpickle operations // bit 0x40: KOL_TRACE_LEVEL_MEDIUM: generate medium amount of tracing // bit 0x80: KOL_TRACE_LEVEL_HIGH: generate high amount of tracing / 24475, 00000, "KOKC tracing event" // *Document: NO // *Cause: N/A // *Action: Event to trace KOKC events // bit 0x1: KOkc_TRACE_LEVEL_BASIC: basic dumps // bit 0x2: KOKC_TRACE_LEVEL_TIME: dump time // bit 0x4: KOKC_TRACE_LEVEL_KOKCD: dump kokcd structure // bit 0x8: KOKC_TRACE_LEVEL_ASSERT: enforce asserts // bit 0x1000: KOKC_TRACE_LEVEL_STACK: dump short stack // bit 0x2000: KOKC_TRACE_LEVEL_LSTACK: dump full stack / / Codepoint length semantics and UTF16 related OCI error messages / 24476, 00000, "KOPF tracing event" // *Document: NO // *Cause: N/A // *Action: Event to trace KOPF operations (FDO) // bit 0x1: KOPF_TRACE_EVENT_FDO: dump FDO's in kopfupdate() / / Codepoint length semantics and UTF16 related OCI error messages / 24480, 00000, "invalid OCI mode" // *Cause: An attempt was made to invoke OCI API with an invalid mode. // *Action: Provide the OCI API with legitimate mode. 24481, 00000, "Failed to initialize multithreaded environment" // *Cause: Operating system did not support multithreaded mode. // *Action: Use single thread mode instead. 24482, 00000, "Pool size was less than 1 in shared mode" // *Cause: Pool size must be positive in shared mode. // *Action: Set a positive pool size. 24483, 00000, "Invalid parameters were passed into environment creation call" // *Cause: Invalid parameters were passed into the environment creation call. // Check the passed in parameters for the following conditions: // -envp should not be NULL // -xtramem_sz should not be negative // -Either both xtramem_sz and usrmempp have to be provided. Or, neither // should be provided. // *Action: Pass in legitimate parameters. 24484, 00000, "Setting authentication handle not allowed after pool create" // *Cause: An attempt was made to set the authentication handle on session pool // handle after OCISessionPoolCreate. // *Action: Set the authentication handle on session pool handle before calling // OCISessionPoolCreate. 24485, 00000, "Invalid attributes in session pool authentication handle" // *Cause: Some of the attributes set on the authentication handle being set on // the session pool handle are invalid. // *Action: Unset the illegal attributes on the authentication handle being set // on session pool handle and then call OCIAttrSet. Refer to OCI documentation // for details. 24486, 00000, "Conflicting attributes in session pool authentication handle" // *Cause: Some attributes could not be set both on the authentication handle // passed to OCISessionGet and the authentication handle set on session pool // handle. // *Action: Unset the conflicting attributes on the authentication handle and // call OCISessionGet. 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. 24507, 00000, "invalid combination of character set ids" // *Cause: Attempts to set one character set id as zero // *Action: Set both charset and ncharset as zero or non-zero // in OCIEnvNlsCreate() 24508, 00000, "Buffer is not aligned correctly." // *Cause: Alignment error ocurred in buffer when converting between // character sets. // *Action: Align buffer appropriately. For UTF16 buffer, pass a ub2 pointer. 24509, 00000, "OCI function currently not supported in UTF16 mode." // *Cause: Attempt to call an OCI function that was not supported in // OCI_UTF16ID mode. // *Action: Remove the offending function or do not create an OCI environment // with OCI_UTF16ID mode or OCI_UTF16ID character set ID. / / Column authorization Related OCI error messages (24530 - 24540) / 24530, 00000, "User not authorized to access column value." // *Cause: Column security is enabled and column value is not authorized. // *Action: The program needs to handle this error and take appropriate action. 24531, 00000, "Column value authorization is unknown." // *Cause: Column security is unknown for the column. // *Action: Verify the fetched data. It may or may not contain a meaningful // value because it is probably the result of an expression that // operated on unauthorized values. 24536, 00000, "Warning - column authorization unknown." // *Cause: Column security is unknown for one or more columns. // *Action: Verify the fetched data. It may or may not contain a meaningful // value because it is probably the result of an expression that // operated on unauthorized values. 24541, 00000, "Event to test OCI attribute-level security." // *Document: NO // *Cause: N/A // *Action: Set this event to get different security status for // fetched columns. / / Diagnosability Related OCI error messages (24550 - 24574) / 24550, 00000, "unhandled signal #%ld received. %s" // *Cause: Serious error: signal received // *Action: Refer to the platform-specific signal code, and see if the // application code caused the error. Otherwise, record // all error state and notify Oracle Support Services. 24551, 00000, "internal error %s" // *Document: NO // *Cause: There is not enough memory on the system or the application // was leaking memory. // *Action: Restart application. If error persists, record // all error state and notify Oracle Support Services. 24552, 00000, "%s parameter exceeds limit of %d" // *Document: NO // *Cause: Number of parameters specified in OCI trace event have exceeded // the limit. // *Action: Record all error state and notify Oracle Support Services. 24553, 00000, "internal error parsing OCI trace event string(%s)" // *Document: NO // *Cause: internal use only 24554, 00000, "trace directory exceeds %d bytes(%.*s)." // *Document: NO // *Cause: internal use only 24555, 00000, "trace file %s cannot be opened in %s directory" // *Document: NO // *Cause: internal use only 24556, 00000, "invalid OCI trace event string(%s)" // *Document: NO // *Cause: internal use only 24557, 00000, "error %s encountered while handling error %s; exiting server process" // *Cause: A second-level error occurred in an Oracle server process that // required that process to exit. // *Action: None. If an excessive number of incidents are dumped, contact // Oracle Support Services. / / 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 only one of the following values is specified: // OCI_TRANS_NEW, OCI_TRANS_JOIN, OCI_TRANS_RESUME, or OCI_TRANS_PROMOTE. 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 branch prepare returns read-only" // *Cause: The transaction is read-only, or this is the outcome of an // optimization for two-phase commit protocol. // *Action: None. Informational only. 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. 24789, 00000, "start not allowed in recursive call" // *Cause: Oracle RM will not start/resume a branch in a recursive call // *Action: Reconsider your application stack design 24790, 00000, "cannot mix OCI_TRANS_RESUME and transaction isolation flags" // *Cause: An attempt was made to change the isolation level of an // existing transaction. // *Action: No action required 24791, 00000, "invalid transaction start flags" // *Cause: An invalid transaction start flag was passed. // *Action: Verify that OCI_TRANS_LOOSE was not passed along with // OCI_TRANS_JOIN, OCI_TRANS_RESUME. Also, verify that other flags // (such as OCI_TRANS_SEPARABLE) passed by the client are supported // by the version of the Oracle server. 24792, 00000, "cannot mix services in a single global transaction" // *Cause: Oracle RM will not serve global (distributed) transaction // requests if branches are created using different services // *Action: Configure clients such that those participating in the same // distributed transaction use the same service name. 24793, 00000, "DTP(Distriubted Transaction Processing) test and debug" // *Document: NO // *Cause: internal use only // *Action: none. 24794, 00000, "no active DTP service found" // *Cause: Oracle RM will not serve global (distributed) transaction // requests until DTP services are configured in RAC. It is // possible that a service was stopped while transactions were // in-flight. // *Action: Provision/Start DTP services first. 24795, 00000, "Illegal %s attempt made" // *Cause: An illegal attempt was made to commit/rollback current transaction // *Action: Use appropriate commit/rollback mechanism 24796, 00000, "operation completed; resume of original transaction rolled back" // *Cause: The commit, rollback, or prepare completed successfully, but // the current transaction for this thread was rolled back. // *Action: If desired, retry the current transaction. If the operation // was prepare, then end transaction appropriately with a commit // or rollback operation. 24797, 00000, "cannot promote the current transaction to a distributed transaction" // *Cause: An illegal attempt was made to promote the current transaction. // *Action: Verify that OCI_ATTR_XID, OCI_ATTR_INTERNAL_NAME, and OCI_ATTR_EXTERNAL_NAME // attributes have been set properly, and verify that the current // transaction has neither performed IDL or PDML operations, nor already // been a distributed transaction. Also, verify that the local transaction // is in the same isolation level if the isolation flag value is set. 24798, 00000, "cannot resume the distributed transaction branch on another instance" // *Cause: An attempt was made to resume a distributed transaction branch that is // physically located on another RAC instance. // *Action: Get a connection to the instance where the transaction branch is located. / / / / OCI Lob/File Related Error message (24800 - 24849) / 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, "Lob read/write functions called while another OCI LOB read/write streaming is in progress" // *Cause: Internal error. // *Action: Wait for the ongoing LOB streaming call to finish before // issuing the next server call, or use OCIBreak() abort the // current LOB streaming call. 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. / 24814, 00000, "operation not allowed for temporary LOBs" // *Cause: Temporary LOB locators are not allowed in the operation. // For example: // OCILobAssign only takes persistent LOB locators as parameters, // not temporary LOBs. // *Action: Use OCILobLocatorAssign for temporary LOBs instead. // Note that OCILobLocatorAssign can also be used for persistent // LOBs, in which case it will behave the same as OCILobAssign. / 24815, 00000, "Invalid character set form" // *Cause: An invalid character set form was passed into an OCI LOB function. // For example, the only valid cs form for OCILobCreateTemporary() // is OCI_DEFAULT(0), SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2). // *Action: Specify a valid character set form. 24816, 00000, "Expanded non LONG bind data supplied after actual LONG or LOB column" // *Cause: A Bind value of length potentially > 4000 bytes follows binding for // LOB or LONG. // *Action: Re-order the binds so that the LONG bind or LOB binds are all // at the end of the bind list. 24817, 00000, "Unable to allocate the given chunk for current lob operation " // *Cause: The given size is increased to accomodate the number of bytes from // server due to varying width db char/nchar set. // *Action: Use smaller chunk sizes when you have character set conversion // between client/server or perform piece-wise read or write. / 24818, 00000, "Operation not permitted on Abstract LOBs" // *Cause: Abstract LOB locators were not allowed in the operation. // For example, OCILobAssign only takes persistent LOB locators // as parameters, not Abstract (i.e., client-side created) LOBs. // *Action: Avoid the operation on Abstract LOBs. / 24819, 00000, "Illegal reference count encountered for a temporary LOB" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // contact Oracle Support Services. / 24820, 00000, "Differnt LOB function called while another OCI LOB call is in progress" // *Cause: An attempt was made to execute a new OCI LOB call while // another OCI LOB call was in progress. // *Action: Wait for the ongoing LOB streaming call to finish before // issuing the next server call, or use OCIBreak() to abort the // current LOB streaming call. / / 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. / 24854, 00000, "invalid pieceinfo provided" // *Cause: While making the first call to write LOB data, an invalid // pieceinfo value provided. // *Action: Correct the call to use OCI_ONE_PIECE or OCI_FIRST_PIECE. // If using OCCI, make sure to call writeBuffer before calling // writeLastBuffer. / / / / OCI Notification Related Error message (24900 - 24939) / / 24900, 00000, "invalid or unsupported mode parameter 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 recipient protocol attribute passed into OCI call" // *Cause: The subscription handle passed into the OCI call did not have // a proper recipient protocol attribute. // *Action: Please set the recipient protocol attribute using the OCIAttrSet() // call. / 24906, 00000, "invalid recipient attribute passed into OCI call" // *Cause: The subscription handle passed into the OCI call did not have // a proper recipient attribute. // *Action: Please set the recipient attribute using the OCIAttrSet() // call. / 24907, 00000, "invalid pair of callback and recipient protocol attributes" // *Cause: The subscription handle passed into the OCI call can't have // both the callback defined and a recipient protocol other than // OCI_SUBSCR_PROTO_OCI at the same time. // *Action: Please set the appropriate callback and recipient 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 24909, 00000, "call in progress. Current operation cancelled" // *Cause: The OCI call was invoked when another call on the connection was // in progress. // *Action: Check if the OCI call is supported when the call is in progress // under special conditions; for example, if it is being used by a // signal handler. // NLS_DO_NOT_TRANSLATE [24910,24910] 24910, 00000, "Event to enable optimized fetch protocol" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to obtain better fetch // performance // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. 24911, 00000, "Cannot start listener thread at specified port" // *Cause: Thread already running at a different port. // *Action: Set the correct port in the environment handle or let the system // choose the port. 24912, 00000, "Listener thread failed. %s" // *Cause: Thread listening for event notification exited because of an error. // The error encountered is appended to the error message. // *Action: The client needs to be restarted. 24913, 00000, "Event to enable NLS validation" // *Cause: N/A // *Action: Set this event in your environment to enable NLS character // validation even when character sets are the same for client/server. // NLS_DO_NOT_TRANSLATE [24914,24914] 24914, 00000, "Notification crash test" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / 24915, 00000, "Cannot start Listener at specified IP address" // *Cause: Thread was already listening at a different IP address. // *Action: Set the correct IP address in the environment handle or // let the system choose the correct IP address. / 24916, 00000, "cannot use IP address attribute before release 11.2 compatible notifications" // *Cause: An attempt was made to use OCI_ATTR_SUBSCR_IPADDR attribute // before release 11.2 compatible notifications. // *Action: Change the compatibility to 11.2. / // NLS_DO_NOT_TRANSLATE [24917,24917] 24917, 00000, "OCI notification client trace event" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / / Generic Notification Related Error message (24940 - 24949) / 24940, 00000, "invalid combination of %s namespace, %s presentation and %s receive protocol" // *Cause: An invalid combination of namespace, presentation and receive // protocol was specified during notification registration. Currently, // only AQ namespace is supported with XML presentation. Non-AQ // namespace is not supported for e-mail and HTTP receive protocols. // *Action: Please change the register call appropriately. 24941, 00000, "invalid combination of notification grouping attributes" // *Cause: An invalid combination of notification grouping attributes was // specified. Currently, only TIME notification grouping class is // supported. If notification grouping class is zero, all other // notification grouping attributes must be zero. // *Action: Refer to documentation and change the attributes appropriately. 24942, 00000, "cannot use ntfn grouping attributes on before release 11.0 compatible ntfns" // *Cause: An attempt was made to use notification grouping on before release // 11.0 compatible notifications. // *Action: Change the compatibility to 11.0. 24943, 00000, "cannot use ntfn grouping with this receive protocol, presentation and/or QoS" // *Cause: An attempt was made to use notification grouping with e-mail or HTTP // receive protocol or XML presentation or payload delivery or reliable // QoS. Currently, only OCI and PLSQL receive protocols and default // presentation are supported with notification grouping. // *Action: Refer to documentation and change the call appropriately. 24944, 00000, "cannot use timeout or grouping with ANONYMOUS namespace" // *Cause: An attempt was made to use timeout or grouping with ANONYMOUS // namespace. Currently, timeout and grouping are supported only with // AQ and DBCHANGE namespaces. // *Action: Refer to documentation and change the call appropriately. 24945, 00000, "cannot use context, QOS and timeout attributes of notification on lower than 10.2 compatible notifications" // *Cause: An attempt was made to use context, QOS and timeout attributes of // notification on lower than 10.2 compatible notifications. // *Action: Change the database compatibility to 10.2. 24946, 00000, "invalid registration callback" // *Cause: An attempt was made to use a reserved callback for notification // registration. // *Action: Choose a different name for the notification callback and // change the register call appropriately. 24947, 00000, "Invalid namespace attribute specified for the subscription %s" // *Cause: An attempt was made to register with invalid namespace attribute. // *Action: Refer to documentation and change the namespace appropriately. / / / / PL/SQL Notification Related Error message (24950 - 24959) / 24950, 00000, "unregister failed, registration not found" // *Cause: The registration 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. / // NLS_DO_NOT_TRANSLATE [24951,24951] 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. 24952, 00000, "register, unregister or post has incorrect collection count" // *Cause: The register, unregister or post function was invoked with a // collection that was smaller than the size specified by the parameter // to the function. // *Action: Please check the function's use and ensure that the size parameter // is correct. / / / / More General OCI Related messages (24960 - 24980) / / 24960, 00000, "the attribute %s is greater than the maximum allowable length of %d" // *Cause: The user attempted to pass an attribute that is too long // *Action: Shorten the specified attribute and retry the operation. / / / 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 this type of view" // *Cause: INSTEAD OF triggers can be created on any view which is not an // Editioning View, while BEFORE and AFTER triggers may only be // created on Editioning Views. // *Action: Change the trigger type to INSTEAD OF or change the view on which // you are attempting to create a DML trigger. 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. // 25011, 00000, "cannot create trigger on internal AQ table" // *Cause: An attempt was made to try to create a trigger on a table that is // used internally to support the Advanced Queueing (AQ) feature. // *Action: Do not create the trigger. 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 // 25021, 00000, "cannot reference a trigger defined on another table" // *Cause: Referenced trigger in the FOLLOWS clause was defined // on another table. // *Action: Create the referenced trigger on the same table 25022, 00000, "cannot reference a trigger of a different type" // *Cause: Referenced trigger in the FOLLOWS or PRECEDES clause was either // a different type or not a compound trigger. // *Action: Create the referenced trigger as the same type or a compound // trigger. 25023, 00000, "Cyclic trigger dependency is not allowed" // *Cause: A cycle of trigger dependency can be formed. // *Action: Do not create a trigger that can formed a cyclic dependency. 25024, 00000, "cannot specify FOLLOWS for a REVERSE CROSSEDITION trigger" // *Cause: The FOLLOWS clause was specified when creating the // REVERSE CROSSEDITION trigger. // *Action: Do not create a REVERSE CROSSEDITION trigger with a FOLLOWS clause. 25025, 00000, "cannot specify PRECEDES clause" // *Cause: The PRECEDES clause was specified when creating a FORWARD // CROSSEDITION trigger or a regular trigger. // *Action: Do not create a FORWARD CROSSEDITION or a regular trigger with // a PRECEDES clause. 25026, 00000, "FOR EACH ROW was specified with compound triggers" // *Cause: FOR EACH ROW is not allowed with compound triggers. // *Action: Remove the FOR EACH ROW clause. // 25027, 00000, "compound triggers cannot be used as system triggers" // *Cause: Compound trigger was defined as system trigger. // *Action: Do not use compound trigger as system trigger. // 25028, 00000, "regular trigger body can not start with keyword COMPOUND" // *Cause: Regular triggers body should start with BEGIN/DECLARE etc . // *Action: Fix the syntax and recompile. // 25029, 00000, "compound triggers should always start with keyword COMPOUND" // *Cause: Compound trigger body was started with incorrect keyword. // *Action: Fix the syntax and recreate. // 25030, 00000, "crossedition trigger cannot be owned by a non-editioned user" // *Cause: An attempt was made to create crossedition trigger in a // non-editioned schema. // *Action: Enable editions for the user and then create the crossedition // trigger. // 25031, 00000, "only a crossedition trigger may be specified" // *Cause: The trigger specified was not a crossedition trigger. // *Action: Specify a crossedition trigger. // 25032, 00000, "crossedition trigger cannot be created in ORA$BASE" // *Cause: An attempt was made to create crossedition trigger // in the ORA$BASE edition. // *Action: Do not create a crossedition trigger in the ORA$BASE edition. // 25033, 00000, "triggers cannot be executed at this time" // *Cause: An attempt was made to execute a trigger // when the session was almost finished. // *Action: Do not attempt to DML with triggers that are expected // to execute when session has almost ended. 25034, 00000, "cannot bypass trigger owned by another user" // *Cause: An attempt was made to do DML from a crossedition trigger on an // object that has a non-crossedition trigger owned by another user. // DML from a crossedition trigger bypasses the running of // non-crossedition triggers; this cannot be allowed for triggers // owned by other users. // *Action: Permit the non-crossedition trigger to be bypassed by attaching it // to the editioning view rather than the table, moving one // of the triggers to be in the same schema as the other, // or explicitly disabling the non-crossedition trigger. 25035, 00000, "cannot perform DML on remote object from a crossedition trigger" // *Cause: An attempt was made to do DML from a crossedition trigger that // would modify data in a remote database. DML from a crossedition // trigger has special rules applied regarding what triggers will fire // as part of that DML; these special rules cannot be applied across // database links and therefore the DML cannot be allowed. // *Action: Perform the DML in a helper function separate from the crossedition // trigger itself; the special rules are not applied when the DML // is not issued from within the crossedition trigger itself. / / 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/FLASH_CACHE/CELL_FLASH_CACHE storage option not allowed" // *Cause: An attempt was made to specify the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE // storage option. This option may only be specified during // - CREATE or ALTER TABLE // - CREATE or ALTER CLUSTER // - CREATE or ALTER INDEX // *Action: Remove this option and retry the statement. 25126, 00000, "Invalid name specified for BUFFER_POOL/FLASH_CACHE/CELL_FLASH_CACHE" // *Cause: The name of the cache hints specified by was invalid. // The only valid names for BUFFER_POOL are KEEP, RECYCLE and DEFAULT. // The only valid names for FLASH_CACHE and CELL_FLASH_CACHE // are KEEP, NONE and DEFAULT. // *Action: Use a valid name or remove the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE 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. / 25158, 00000, "Cannot specify RELY for foreign key if the associated primary key is NORELY" // *Cause: RELY is specified for the foreign key contraint, when the // associated primary key constraint is NORELY. // *Action: Change the option of the primary key also to RELY. / 25159, 00000, "Must specify a valid tablespace number" // *Cause: A valid tablespace number was missing. // *Action: Specify a valid tablespace number. / 25160, 00000, "Must specify a valid relative data block address" // *Cause: A valid relative data block address was missing. // *Action: Specify a valid relative data block address. / 25161, 00000, "Cannot have both DBA and RDBA options" // *Cause: Both the DBA and RDBA options were passed to ALTER SYSTEM DUMP REDO. // *Action: Use either the DBA option or the RDBA option but not both. / 25162, 00000, "Must specify both RDBA MIN and RDBA MAX options" // *Cause: Only one RDBA option was passed to ALTER SYSTEM DUMP REDO. // *Action: Specify both RDBA MIN and RDBA MAX. / 25163, 00000, "Invalid tablespace number or relative data block address" // *Cause: The relative data block adress is invalid for the given tablespace // number or the table space number is invalid. // *Action: Specify a valid tablespace number or relative data block // address. / 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 or sorted hash cluster" // *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, list, 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-25325 Reserved for AQ / 25350-25375 Reserved for V8 Transaction OCI / 25400-25425 Reserved for Application Failover / 25426-25435 Reserved for Dblink Concentration / 25436-25476 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: 25214, 00000, "cannot specify delay or expiration for enqueue to exception queue" // *Cause: A message was enqueued to the exception queue with either delay // or expiration specified. // *Action: Enqueue a message without delay or expiration. 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. // 25224, 00000, "sender name must be specified for enqueue into secure queues" // *Cause: An attempt was made to enqueue into a secure queue without // specifying a sender name. // *Action: Enqueue the message with sender name specified. // / / 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. // 25227, 00000, "Propagation job %s doesn't exist" // *Cause: The job doesn't exist in AQ$_SCHEDULES or cache. // // *Action: // 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 from %s.%s" // *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. 25274, 00000, "AQ Buffered Queue event" // *Cause: N/A. // *Action: event used for AQ Buffered Queue mode. 25275, 00000, "Test support for buffered queues" // *Cause: internal use only // *Action: none. / / 25276-25320 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. 25289, 00000, "Buffer Already Exists" // *Cause: Buffer already exists for the specified queue. // *Action: None 25290, 00000, "Cannot complete operation on queue %s with existing messages" // *Cause: Queue already has messages. Cannot complete operation // *Action: Truncate the queue before adding/dropping a buffer 25291, 00000, "Buffer does not exist for the specified queue" // *Cause: Buffer does not exist for the specified queue // *Action: Operation on the buffer cannot be performed. create the buffer 25292, 00000, "Buffer operations are not supported on the queue" // *Cause: Buffer operations are not supported on the specified queue type // *Action: Buffered operations are only supported on to 8.1 style // queues, which do not have transaction grouping. 25293, 00000, "Lob attributes must be null for buffered operations" // *Cause: Enqueue of a buffered message with a non-null lob attribute was attempted // *Action: Set the lob attributes to null before enqueuing the buffered message 25294, 00000, "Cannot propagate user buffered messages to a database with version lower than 10.2" // *Cause: Propagation of user buffered messages was attempted to a database with version lower than 10.2. // *Action: Do not propagate buffered messages to the database. 25295, 00000, "Subscriber is not allowed to dequeue buffered messages" // *Cause: Subscriber is only allowed to dequeue persistent messages // *Action: Drop the subscriber and re-create it, or dequeue only persistent messages for the subscriber 25296, 00000, "Queue Table %s has a buffered queue %s" // *Cause: Cannot downgrade the queue table because it has a buffered queue // *Action: Drop the buffer or the buffered queue //25297, 00000, "Enqueue of buffered message failed, attempted to enqueue buffered message with %s" // *Cause: Buffered message was enqueued by specifying delay or sequence deviation. // *Action: Do not specify delay of sequence deviation when enqueuing buffered messages. 25298, 00000, "Only immediate visibility mode supported for buffered message enqueue or dequeue" // *Cause: A visibility of dbms_aq.ON_COMMIT was supplied with the buffered message enqueue or dequeue // *Action: Supply a visibility of dbms_aq.IMMEDIATE 25299, 00000, "Invalid message delivery_mode " // *Cause: Invalid value was specified for delivery mode // *Action: Specify dbms_aq.BUFFERED or dbms_aq.PERSISTENT during Enqueue or dbms_aq.BUFFERED, dbms_aq.PERSISTENT or dbms_aq.PERSISTENT_OR_BUFFERED during Dequeue and Listen. 25300, 00000, "Cannot drop buffer for queue with buffered subscribers" // *Cause: Cannot drop buffer for queue with buffered subscribers // *Action: Either drop buffered subscribers or forcibly drop the buffer 25301, 00000, "Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2" // *Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a database with version lower than 10.2. // *Action: Do not attempt to enqueue or dequeue user buffered messages. 25302, 00000, "Operation not possible for non-buffered queue %s" // *Cause: Last enqd/ackd message is only supported for buffered queues // *Action: The operation is not supported. 25303, 00000, "Buffered operation allowed only on the owner instance" // *Cause: Operation was not performed on the owner instance. // *Action: Perform operation on the owner instance. 25304, 00000, "Cannot use priority order queues for capture LCRs" // *Cause: Capture LCRs can only use commit time or enqueue time ordered queues. // *Action: Use the appropriate type of queue for captured LCRs. 25305, 00000, "enqueue failed, expiration must be zero for queue %s.%s" // *Cause: An attempt was made to enqueue to a buffered // queue with expiration greater than zero seconds. // *Action: Set expiration to zero. / 25306, 00000, "Cannot connect to buffered queue's owner instance" // *Cause: cannot connect to the owner instance of the buffered queue // *Action: set listener information in REMOTE_LISTENERS or LOCAL_LISTENERS initialization parameter. / 25307, 00000, "Enqueue rate too high, flow control enabled" // *Cause: Subscribers could not keep pace with the enqueue rate. // *Action: Try enqueue after waiting for some time. 25308, 00000, "AQ canonicalization event" // *Document: NO // *Cause: // *Action: / 25309, 00000, "Unable to lock deq IOT, skip retry count increment" //*Document: NO // *Cause: // *Action: / 25310, 00000, "Subscriber is Notification only; dequeue not supported" // *Cause: Notification only subscribers are not allowed to dequeue. // *Action: Recreate subscriber if necessary. / 25311, 00000, "%s not supported for non-persistent queue" // *Cause: Specified QOS is not supported for non-persistent queues. // *Action: Specify the right QOS. / 25312, 00000, "Cannot specify nonzero sender protocol" //*Document: Yes // *Cause: Sender protocol was specified during an enqueue operation. // *Action: Specify the enqueue sender protocol as null or zero. / 25313, 00000, "a queue may not subscribe to itself for propagation" // *Cause: The specified subscriber had a NULL name and an address equal to // the queue name. // *Action: Provide a valid subscriber and retry the operation. / 25314, 00000, "a commit-time queue table cannot be migrated to 8.0" // *Cause: An attempt was made to migrate a commit-time queue table to an // unsupported compatibility level. // *Action: Provide an appropriate compatibility level, and retry the // operation. / 25315, 00000, "unsupported configuration for propagation of buffered messages" // *Cause: An attempt was made to propagate buffered messages with the // database link pointing to an instance in the destination database // which is not the owner instance of the destination queue. // *Action: Use queue to queue propagation for buffered messages. / 25316, 00000, "Late in the current transaction to begin an Enqueue/Dequeue operation" // *Cause: Check if the Enqueue/Dequeue operation is performed via triggers // on Materialized Views which isn't supported. // *Action: Triggers on materialized views aren't supported. Workarounds are // on-demand materialized views or execution of trigger code // within an autonomous txn. / 25317, 00000, "Propagation stopped because of instance shutdown" // *Cause: A propagation job has stopped because the instance is // shutting down. // *Action: No user action is required. / 25318, 00000, "Propagation stopped because of instance affinity change" // *Cause: A propagation job has stopped because its instance affinity // has changed. // *Action: No user action is required. The job will restart on the // appropriate instance. / 25319, 00000, "Queue table repartitioning aborted" // *Cause: During instance restart in an Oracle RAC environment, queue table // repartitioning aborted due to errors. // *Action: Look at the incident generated for this error and report the // problem to Oracle Support Services. / 25320, 00000, "Failed to create, alter, or remove Subscriber" // *Cause: There is a pending enqueue or dequeue operation on // this queue from the same session. // *Action: Either COMMIT or ROLLBACK pending enqueue or dequeue operation // before attempting to create, alter, or remove the subscriber. / / 25321-25325 Reserved for enq/deq user properties / 25321, 00000, "enqueue failed, user property specified but queue %s.%s is not an 8.1 style queue" // *Cause: user properties can only be specified when enqueueing into 8.1 // style queues. // *Action: Specify an 8.1 style queue or pass user property as NULL. / / 25326-25350 Reserved for AQ Array/Miscellaneous Errors / 25326, 00000, "Array %s operation failed for message at index %s" // *Cause: Array operation fails for the message at specified index. Look // at the remainder of the error stack to see what the problem was. // *Action: Fix cause of error and retry array operation. 25327, 00000, "Array size is invalid" // *Cause: Array size must be a positive, non-zero integer. // *Action: Use corrected array size and retry array operation. 25328, 00000, "%s argument size %s is smaller than array size" // *Cause: The size of the argument is smaller than the given array size. // *Action: Lower array size or use a larger sized input argument. 25329, 00000, "AQ array operations not allowed on 8.0 queues" // *Cause: An array enqueue/dequeue was attempted on an 8.0 queue. // *Action: Use single enqueue/dequeue with this queue. 25330, 00000, "PL/SQL associative arrays may not be used with AQ array operations" // *Cause: A PL/SQL associative array was provided for the payload parameter // in an enqueue/dequeue array operation. // *Action: Use VARRAY or NESTED TABLE types with AQ array operations. 25331, 00000, "cannot downgrade because there are commit-time queue tables" // *Cause: An attempt was made to downgrade a database that has commit-time // queue tables. // *Action: Drop all commit-time queue tables before attempting the downgrade. 25332, 00000, "Invalid release value %s for queue table compatible parameter" // *Cause: The release level given for the queue table compatible parameter // is invalid // *Action: Specify a valid release value for the queue table compatible // parameter 25333, 00000, "Buffered Queue to Queue propagation did not connect to the correct instance" // *Cause: Queue to Queue propagation for buffered messages didn't // connect to the correct instance, most likely because service was // not started for the destination queue. // *Action: No user action is required. Propagation will start the service for // the destination queue and retry. 25334, 00000, "Buffered propagation must restart as the destination queue was recreated/moved" // *Cause: Buffered propagation destination queue was recreated or its // ownership was moved to another instance during propagation. // *Action: No user action is required. Propagation will reinitialize its // metadata and retry. 25335, 00000, "AQ array operations not allowed for buffered messages" // *Cause: An array enqueue/dequeue was attempted for buffered messages // *Action: Use single enqueue/dequeue for buffered messages or an array // size of one. 25336, 00000, "Cannot contact instance %s during Streams AQ operation" // *Cause: The specified instance was not responding to AQ requests. // *Action: Set parameter aq_tm_processes to a non-zero value. If the problem // persists, contact Oracle Support Services. 25337, 00000, "Cannot propagate in queue-to-queue mode to a database with version lower than 10.2" // *Cause: Remote subscriber with queue_to_queue mode set to TRUE was added. // The remote subscriber is on a database version lower than 10.2. // Propagation was scheduled to a destination database with version // lower than 10.2. // *Action: Remove the remote subscriber with queue_to_queue mode and add the // subscriber back with queue_to_queue set to FALSE. Unschedule the // queue-to-queue propagation and schedule propagation in // queue-to-dblink mode. 25338, 00000, "operation '%s' is not allowed for sync_capture '%s'" // *Cause: An attempt was made to execute the specified operation for a // sync_capture process. // *Action: Remove the offending call. 25339, 00000, "STREAMS '%s' must be sync_capture" // *Cause: The specified capture STREAMS did not exist or was not a // sync_capture process. // *Action: Remove the offending call. 25340, 00000, "must use commit-time queue for sync_capture" // *Cause: An attempt was made to create a sync_capture without using // a commit-time queue. // *Action: Rerun statement with a commit-time queue. 25341, 00000, "sync_capture does not support \"%s\".\"%s\" because of the following reason:" // *Cause: sync_capture encountered a table with an unsupported // property. The most common reason is an unsupported column // data type. // *Action: Revise the Capture rules to skip over the table in // question. One option is to remove the rule that captures changes // from the unsupported table. Check DBA_STREAMS_TABLE_RULES to // determine the rule on the table specified in the error. // // Also query the DBA_STREAMS_UNSUPPORTED view to determine // which tables are not supported by STREAMS and for what // reason. // // For potential workarounds to certain unsupported properties, see // Metalink. 25342, 00000, "cannot downgrade because there are apply processes for user buffered messages" // *Cause: An attempt was made to downgrade a database that has apply process // for user-buffered messages. // *Action: Drop all the apply processes for user-buffered messages before // attempting the downgrade. 25343, 00000, "Streams error queue cannot be exported" // *Cause: An attempt was made to export a database that has apply errors. // *Action: Delete or reexecute errors before attempting the export. 25344, 00000, "statement has bind variables" // *Cause: Current API could not handle a statement with bind variables. // *Action: Use alternative API which handles bind variables. / / 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. // 25409, 00000, "failover happened during the network operation,cannot continue" // *Cause: The connection was lost when fetching a LOB column. // *Action: Failover happened when fetching LOB data directly or indirectly. // Please replay the top level statement. // 25425, 00000, "connection lost during rollback" // *Cause: The connection was lost while issuing a rollback and the // application failed over. // *Action: The connection was lost and failover happened during rollback. // 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. / 25427, 00000, "cannot downgrade database links after database link data dictionary has been upgraded " // *Cause: An attempt was made to downgrade after the upgrade of the // database link data dictionary. // *Action: Drop the database links before attempting the downgrade. / / 25436-25476 Reserved for Rules Engine / 25436, 00000, "invalid table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the table values specified had an invalid alias. // *Action: Check the valid table aliases in the evaluation context, // and try again with a valid alias. 25437, 00000, "duplicate table value for table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // some of the table values specified had the same table alias. // *Action: Check the table values specified, and try again with only // one value per table. 25438, 00000, "invalid variable name: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the variable values specified had an invalid name. // *Action: Check the valid variable names in the evaluation context, // and try again with a valid name. 25439, 00000, "duplicate variable value for variable: %s" // *Cause: An attempt to evaluate was made, which failed because // some of the variable values specified had the same variable name. // *Action: Check the variable names specified, and try again with only // one value per variable. 25440, 00000, "invalid table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the column values specified had an invalid table alias. // *Action: Check the valid table aliases in the evaluation context, // and try again with a valid name. 25441, 00000, "duplicate column value for table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the column values supplied a value for a // table alias, which already had a table value supplied. // *Action: Check the table and column values specified, and try again with // either a table value or column values for each table alias. 25442, 00000, "too many column values for table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // too many column values were supplied for the specified // table alias. // *Action: Check the column values specified, and try again with // the right number of column values. 25443, 00000, "duplicate column value for table alias: %s, column number: %s" // *Cause: An attempt to evaluate was made, which failed because // duplicate column values were supplied for the specified // table alias and column number. // *Action: Check the column values specified, and try again with // only one column value for each table alias, and column number. 25444, 00000, "invalid ROWID: %s for table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // an invalid ROWID was supplied for the specified // table alias. // *Action: Check the column values specified, and try again with // only one column value for each table alias, and column number. 25445, 00000, "invalid column number: %s for table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // an invalid column number was supplied for the specified // table alias as a part of a column value. // *Action: Check the column values specified, and try again with // a valid column number. 25446, 00000, "duplicate column value for table alias: %s, column: %s" // *Cause: An attempt to evaluate was made, which failed because // duplicate column values were supplied for the specified // table alias and column name. // *Action: Check the column values specified, and try again with // only one column value for each table alias, and column name. 25447, 00000, "encountered errors during evaluation of rule %s.%s" // *Cause: An attempt to evaluate was made, which failed during the // evaluation of the specified rule. // *Action: Check the rule and the values passed to evaluate, and try // again with valid values. 25448, 00000, "rule %s.%s has errors" // *Cause: An attempt to load the specified rule failed due to errors // in the rule. // *Action: Check the rule and retry the operation. 25449, 00000, "invalid variable name: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the attribute values specified had an invalid // variable name. // *Action: Check the valid variable names in the evaluation context, // and try again with a valid name. 25450, 00000, "error %s during evaluation of rule set %s.%s" // *Cause: The specified error occurred during evaluation of the // rule set. // *Action: Check the error and take appropriate action. 25451, 00000, "too many attribute values for variable: %s" // *Cause: An attempt to evaluate was made, which failed because // too many attribute values were supplied for the specified // variable. // *Action: Check the attribute values specified, and try again with // the right number of attribute values. 25452, 00000, "duplicate attribute value for variable: %s, attribute: %s" // *Cause: An attempt to evaluate was made, which failed because // duplicate attribute values were supplied for the specified // variable and attribute name. // *Action: Check the attribute values specified, and try again with // only one attribute value for each variable, and attribute name. 25453, 00000, "invalid iterator: %s" // *Cause: An attempt to get rule hits or to close an iterator was made, // which failed because an invalid iterator was passed in. // *Action: Check the iterator, and try again with a valid iterator. 25454, 00000, "error during evaluation of rule set: %s.%s for iterator: %s" // *Cause: An attempt to get rule hits for an iterator was made, // which failed because of an error in evaluation of the specified // rule set. // *Action: Check the validity of the rule set and try again. 25455, 00000, "evaluation error for rule set: %s.%s, evaluation context: %s.%s" // *Cause: An attempt to evaluate the specified rule set using the // evaluation context specified failed due to some errors. // *Action: Check additional errors signalled to determine the problem. 25456, 00000, "rule set was modified or evaluation terminated for iterator: %s" // *Cause: An attempt to get rule hits was made, which failed because // the underlying rule set was modified after the iterator was // returned. // *Action: Try again after re-evaluating the rule set. 25457, 00000, "evaluation function %s returns failure" // *Cause: The specified evaluation function returned a failure during // evaluation, causing evaluation to terminate. // *Action: Check arguments to evaluate and retry. 25461, 00000, "rule set not specified" // *Cause: An attempt to evaluate was made, which failed because // the ruleset name specified was null. // *Action: Check the rule set name, and try again with a valid name. 25462, 00000, "evaluation context not specified" // *Cause: An attempt to evaluate was made, which failed because // the evaluation context specified was null. // *Action: Check the evaluation context name, and try again with a // valid name. 25463, 00000, "table alias not specified" // *Cause: An attempt to evaluate was made, which failed because // one of the table values specified had a NULL alias name. // *Action: Check the list of table values, and try again with a // valid alias name. 25464, 00000, "ROWID not specified for table alias: %s" // *Cause: An attempt to evaluate was made, which failed because // the table value for the specified table alias had a NULL ROWID. // *Action: Check the list of table values, and try again with a // valid ROWID. 25465, 00000, "variable name not specified" // *Cause: An attempt to evaluate was made, which failed because // one of the variable values specified had a NULL variable name. // *Action: Check the list of variable values, and try again with a // valid variable name. 25466, 00000, "data not specified for variable name: %s" // *Cause: An attempt to evaluate was made, which failed because // the variable value for the specified variable name had NULL // data. // *Action: Check the list of variable values, and try again with // valid data. 25467, 00000, "table alias not specified" // *Cause: An attempt to evaluate was made, which failed because // one of the column values specified had a NULL alias name. // *Action: Check the list of column values, and try again with a // valid alias name. 25468, 00000, "column name not specified for alias: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the column values for the specified alias name // had a NULL column name. // *Action: Check the list of column values, and try again with a // valid column name. 25469, 00000, "data not specified for alias: %s column name: %s" // *Cause: An attempt to evaluate was made, which failed because // the column value for the specified alias and column name // had NULL data. // *Action: Check the list of column values, and try again with // valid data. 25470, 00000, "duplicate attribute value for variable: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the attribute values supplied a value for a // variable, which already had a variable value supplied. // *Action: Check the variable and attribute values specified, // and try again with either a variable value or // attribute values for each variable. 25471, 00000, "attribute name not specified for variable: %s" // *Cause: An attempt to evaluate was made, which failed because // one of the attribute values for the specified variable // had a NULL attribute name. // *Action: Check the list of attribute values, and try again with a // valid attribute name. 25472, 00000, "maximum open iterators exceeded" // *Cause: The open rule hit iterators in the session exceeded // 2 * OPEN_CURSORS. // *Action: Close some rule hit iterators. // 25473, 00000, "cannot store %s in rule action context" // *Cause: The user attempted to put unsupported data types, such as LOBs // and evolved ADTs, into the rule action context. // *Action: Use only supported data types in rule action context. / 25474 is reserved for dumping info / 25475 is reserved for debug mode 25476, 00000, "use pre-5523578 behaviour when looking up enabled roles" // *Cause: N/A // *Action: Derive the enabled roles under the rules engine using the old // method that existed before the fix to bug 5523578. / / / 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 / / 25526-25550 Reserved for MTTR advisory / 25526, 00000, "bad format of _DB_MTTR_SIM_TARGET: %s" // *Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR. // *Action: Alter the value of _DB_MTTR_SIM_TARGET. 25527, 00000, "bad format of _DB_MTTR_SIM_TARGET" // *Cause: One value in _DB_MTTR_SIM_TARGET is empty. // *Action: Set the value of _DB_MTTR_SIM_TARGET properly. 25528, 00000, "too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET" // *Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET. // *Action: Alter the value of _DB_MTTR_SIM_TARGET. 25530, 00000, "FAST_START_MTTR_TARGET is not specified" // *Cause: An attempt to start MTTR advisory was made, which failed because // FAST_START_MTTR_TARGET was not specified. // *Action: Set FAST_START_MTTR_TARGET. 25531, 00000, "MTTR specified is too small: %s" // *Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR // setting is too small for MTTR advisory. // *Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR. 25532, 00000, "MTTR specified is too large: %s" // *Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR // setting is too large for MTTR advisory. // *Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR. 25533, 00000, "FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified" // *Cause: An attempt to start MTTR advisory was made, which failed because // either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL was // specified. // *Action: Set FAST_START_IO_TARGET and LOG_CHECKPOINT_INTERVAL to 0. / / 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. 25963, 00000, "join index must be created on tables\n" // *Cause: An attempt to create a join index was made, which failed // because the from clause contains non table object. // *Action: Ensure that the from clause only contains tables. 25964, 00000, "column type incompatible with join column type\n" // *Cause: The datatype of the join column is incompatible with the // datatype of the joined column. // *Action: Select a compatible datatype for the join column. 25965, 00000, "fact table must be included in the from clause\n" // *Cause: An attempt to create a join index was made, which failed // because the from clause does not contain the fact table. // *Action: Ensure that the from clause contains the fact table. 25966, 00000, "join index cannot be based on an index organized table\n" // *Cause: An attempt to create a join index was made, which failed // because one of the tables was an index organized table. // *Action: Ensure no underlying tables are index organized. / / 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, "invalid value for SETID or OID column\n" // *Cause: The value passed in a Direct Path API stream for a column // containing a SETID or OID has an invalid value. SETIDs and // Object IDs must be either 16 bytes of RAW data or 32 bytes of // hexidecimal characters. // *Action: Regenerate the Direct Path API stream with a valid value for the // SETID column. 26008, 0, "Invalid syntax or bind variable in SQL string for column %s.\n%s\n" // Cause: See following error message for more information. // A SQL string cannot have quoted strings improperly terminated. // A bind variable in a SQL string cannot have a length of 0, cannot // exceed maximum length of 30 characters, and cannot be missing a // double quote. // Action: Fix the SQL string. See following error for more information. 26009, 00000, "stream verification error: %s\n" // *Cause: An error has occurred in a Data Pump stream verification // operation. // *Action: Contact Oracle Support Services. 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, 0, "header in file %s has an incompatible version number\n" // *Cause: A dump file was specified for a load operation whose version // number is incompatible with the dump file version currently // produced by the Oracle server on the system. Usually this // message indicates that the dump file was produced by a newer // version of the Oracle server. // *Action: Load this dump file using the same version of the Oracle // server that created the file. 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, "unexpected error on %s %s while retrieving %s\n%s" // *Cause: The SQL error was returned from an OCIStmtExecute call. // *Action: Correct the SQL error that was returned. 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, "Virtual column %s in table %s.%s cannot be loaded by direct path\n" // *Cause: You attempted to load an virtual column using the direct path. // *Action: Virtual columns cannot be loaded using the direct path. 26017, 00000, "global indexes not allowed for direct path load of table partition %s" // *Cause: Global indexes are defined on a table when direct path loading a // single partition of the table. 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. Informational only. 26021, 00000, "index %s.%s partition %s loaded successfully with %s keys" // *Cause: Partitioned index information put to loader log file. // *Action: None. Informational 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, "column %s.%s encryption properties differ for source or target table" //* Cause: The source and destination columns did not have the same //* encryption properties. //* Action: For security reasons, check that the source and target table have //* the same encryption properties. //* 26034, 00000, "Column %s does not exist in stream\n" // *Cause: Column specified in the column list does not exist in the stream. // *Action: Make sure the column exists or remove it from the list. 26035, 0000, "Error attempting to encrypt or decrypt column" //* Cause: An error occurred while attemping to encrypt or decrypt //* a database column. // *Action: Verify correct encryption key was specified. //* 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, "must specify partition name(s) for system partitioned table %s\n" // *Cause: An attempt was made to load a system partitioned table with no // partition name(s) specified. // *Action: Specify the partition name(s) explicitly. 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. 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. / 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. / 26052, 0000, "Unsupported type %d for SQL expression on column %s.\n" //* Cause: The direct path api does not support a SQL expression on a // column of that type. //* Action: Make sure the types are correct. / / do NOT translate or document message 26053 - it is never displayed // NLS_DO_NOT_TRANSLATE [26053,26053] 26053, 0000, "Row was not loaded due to conversion error.\n" / //* Cause: The current row was not loaded due to a conversion error. //* Action: Continue with the load anyways. // 260xx - 260xx Direct Path API 26054, 0000, "Direct Path Context prepared for a different mode than operation requested.\n" //* Cause: The user prepared the direct path context for one operation // (Load, Unload, Convert), but then tried to perform a different // operation. //* Action: Make sure the direct path context mode and operation matches. / 26055, 0000, "Invalid buffer specified for direct path unload\n" //* Cause: The user specified a zero length or null buffer to be used for // the Direct Path Unload operation. //* Action: Specify a valid buffer and length. / 26056, 00000, "Requested direct path operation on a view is not supported.\n" // *Cause: An attempt was made to load into a view using direct path that has // user-defined types, XML data, object type table or SQL expressions. // *Action: Do not attempt to use direct path when loading a view that has // nonscalar columns or when using SQL expressions on input columns. / / do NOT translate or document message 26057 - it is for internal use only // NLS_DO_NOT_TRANSLATE [26057,26057] 26057, 00000, "Conversion is not necessary for this direct path stream.\n" // *Cause: User attempted to convert a direct path stream that does not // require conversion. // *Action: Load the stream without conversion it. / 26058, 0000, "unexpected error fetching metadata for column %*s in table %*s\n" //* Cause: The direct path API encountered an unexpected error while // retrieving metadata for a column. //* Action: Contact Oracle support. / 26059, 0000, "Data is too large for column %s\n" //* Cause: The direct path API encountered a column that can not be loaded // because the input data is too large for a column. //* Action: Make the target column larger. / 26060, 0000, "Can not convert type identifier for column %s\n" //* Cause: The direct path API encountered a type identifier for a column that // can not be loaded because a mapping can not be found for the input // value. //* Action: Verify the input data. / 26061, 0000, "Concurrent direct unloads is not allowed.\n" //* Cause: User attempted a direct unload when another is still in progress. //* Action: Complete the current direct unload before starting another. / 26062, 0000, "Can not continue from previous errors.\n" //* Cause: User attempted to continue a direct path load after receiving an // error which indicates the load can not continue. //* Action: Address the original error that was returned. / 26063, 0000, "Can not flashback to specified SCN value - Wrap: %s Base: %s.\n" //* Cause: User specified an SCN which occurs before the last time the // table definition was modified. //* Action: Specify a more recent SCN. / 26064, 0000, "Invalid SCN specified - Wrap: %s Base: %s.\n" //* Cause: User specified an invalid SCN. //* Action: Specify a valid SCN. / 26065, 0000, "check constraint cannot reference column, %s, in direct path load\n" //* Cause: An enabled check constraint was found on a column stored as a lob. //* Action: Either disable the check constraint before loading the table data //* using the direct path mode, or use the conventional path mode //* instead. / 26076, 0000, "cannot set or reset value after direct path structure is allocated" //* Cause: Client attempted to set or reset the number of rows in a direct path //* structure after it has already been allocated and initialized. //* Attributes used is one of the following: //* - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array //* - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache //* (default is 0) //* - OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be //* disabled on overflow (default is FALSE) //* Action: Set the following attributes before: //* - OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array //* - OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare //* - OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare 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. 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 %s" //* 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. 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, "input data column size (%d) exceeds the maximum input size (%d)" //* Cause: The user attempted to specify a column size (%d) that exceeded //* the maximum allowable input size (%d)." //* Action: Make sure the input column metadata matches the column definition. 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 - 26649 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" // *Document: NO // *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: 26577, 00000, "PRESERVE TABLE can not be used when dropping old style materialized view %s.%s\n" // *Cause: The materialized view consists of a view and a container table. // *Action: Drop the materialized view without PRESERVE TABLE option. / / / 26650 - 26999 Reserved for Log Based Replication Replication (KN) / 26650, 00000, "%s %s background process %s might not be started successfully" // *Cause: An error occurred during creation of a capture or apply // background process. // *Action: Review V$STREAMS_CAPTURE and V$STREAMS_APPLY_COORDINATOR views for // the status of these processes. Also check the trace file for more // information. 26651, 00000, "Unable to start or stop capture process %s" // *Cause: An attempt was made to start or stop a capture process while // another capture process was concurrently starting or stopping. // *Action: You cannot concurrently start or stop capture processes. Wait // before attempting to start or stop additional capture processes. 26652, 00000, "Capture %s did not start properly and is currently in state %s" // *Cause: An attempt to restart a capture process failed. // *Action: Review V$STREAMS_CAPTURE view for the state of the capture // process. Also check the trace files for more information. 26653, 00000, "Apply %s did not start properly and is currently in state %s" // *Cause: An attempt to restart an apply process failed. // *Action: Review V$STREAMS_APPLY% views for the state of the apply // process. Also check the trace files for more information. 26654, 00000, "Capture %s attempted to connect to apply %s already configured for %s" // *Cause: An attempt was made by a GoldenGate, XStream or Streams Capture or XStream In to connect to an // Apply that is already connected in the other mode. // *Action: You cannot connect a capture to an apply already configured for // another apply mode. Create or connect to another apply. 26655, 00000, "Invalid %s specified for %s procedure" // *Cause: An attempt was made to execute the specified procedure with an // invalid SCN value. // *Action: Resubmit procedure with a valid SCN value. 26660, 00000, "Invalid action context value for %s" // *Cause: The value specified in the action context is invalid for // use in GoldenGate, XStream or Streams. // *Action: Check that the type and value are correct. 26661, 00000, "STREAMS tracing event" // *Document: NO // *Cause: // *Action: Check that the type and value are correct. 26662, 00000, "unable to process %s Data Dictonary information for object" // *Cause: The database is unable to process GoldenGate, XStream or Streams Data // Dictionary for this object. // *Action: Check that the compatibility for the database supports the object, // and check the trace file for information about the object. 26663, 00000, "error queue for apply process %s must be empty" // *Cause: The error queue for this apply process contains error entries. // *Action: Execute or delete errors in the error queue. 26664, 00000, "cannot create %s process %s" // *Cause: An attempt was made to create a GoldenGate, XStream or Streams process // when another was being created concurrently. // *Action: Wait for the creation of the other GoldenGate, XStream or Streams // process to finish before attempting to create the process. 26665, 00000, "%s process %s already exists" // *Cause: An attempt was made to create a GoldenGate, XStream or Streams process // that already exists. // *Action: Either specify another process or remove the existing // GoldenGate, XStream or Streams process. 26666, 00000, "cannot alter %s process %s" // *Cause: An attempt was made to alter a GoldenGate, XStream or Streams process // that is currently running. // *Action: Stop the GoldenGate, XStream or Streams process with FORCE parameter // set to TRUE and reissue the command. 26667, 00000, "invalid %s parameter %s" // *Cause: An attempt was made to specify an invalid parameter. // *Action: Check the documentation for valid parameters. 26668, 00000, "%s process %s exists" // *Cause: An attempt to remove the component failed because it // is associated with the GoldenGate, XStream or Streams process. // *Action: Either remove the process manually or specify the "cascade" // option in dbms_streams_adm.remove_queue. 26669, 00000, "parameter %s inconsistent with parameter %s" // *Cause: An attempt was made to specify a subprogram parameter value // that is inconsistent with another parameter value. // *Action: Check the documentation for valid parameter values. 26670, 00000, "No capture is found for queue '%s'" // *Cause: An attempt was made to add an XStream outbound server to a // queue using uncommitted data mode when no co-located Streams capture // was configured for that queue. // *Action: Change to committed data mode or configure a local Streams capture // for the specified queue then retry the operation. 26671, 00000, "maximum number of %s processes exceeded" // *Cause: Cannot create additional GoldenGate, XStream or Streams processes since // the maximum number of processes has been reached. // *Action: Remove existing GoldenGate, XStream or Streams processes and retry the operation. 26672, 00000, "timeout occurred while stopping %s process %s" // *Cause: Timeout occurred while waiting for a GoldenGate, XStream or Streams // process to shut down. // *Action: Retry the operation. If the error persists, try stopping the // process with the FORCE option, or contact Oracle Support Services. 26673, 00000, "duplicate column name %s" // *Cause: An attempt was made to specify a duplicate column name in an LCR. // *Action: Remove the duplicate column and retry the operation. 26674, 00000, "Column mismatch in '%s.%s' (LCR: %s type=%s; DB: %s type=%s)" // *Cause: The columns in the LCR were not the same or not found in the // database table. // *Action: Alter the database table. 26675, 00000, "cannot create %s capture process %s" // *Cause: GoldenGate, XStream or Streams capture process could not be created // because one or more parameters contain invalid value. // *Action: Refer to trace file for more details. 26676, 00000, "Table '%s.%s' has %s columns in the LCR and %s columns in the replicated site" // *Cause: The number of columns in the LCR was not the same as the // the replicated site. // *Action: Alter the table structure 26677, 00000, "%s downstream capture process %s cannot proceed" // *Cause: Database global name has been set to a value which is same as the // source database name of the downstream capture process. // *Action: Change database global name to a value other than // the source database name for the downstream capture. 26678, 00000, "%s downstream capture process for source database %s must be created at database %s first" // *Cause: A GoldenGate, XStream or Streams downstream capture process was // nonexistent when this operation was attempted. // *Action: Create a GoldenGate, XStream or Streams downstream capture process, // then retry the operation. 26679, 00000, "operation not allowed on LOB or LONG columns in LCR" // *Cause: Certain operations on LOB/LONG columns of the LCR // through rule-based transformations, DML handlers, or error // handlers were not allowed. // *Action: Do not perform restricted operations on LOB or LONG columns in // LCRs. See the documentation for operations that are restricted // on LOB/LONG columns in LCRs. 26680, 00000, "object type not supported" // *Cause: The specified object type is not supported. // *Action: Retry with a supported object type. 26681, 00000, "command type not supported" // *Cause: The specified command type is not supported. // *Action: Retry with a supported command type. 26682, 00000, "invalid value for publication_on" // *Cause: The publication_on parameter should be either 'Y' or 'N' // *Action: Retry with a proper value for publication_on. 26683, 00000, "invalid value for value_type" // *Cause: The value_type parameter should be either 'OLD' or 'NEW' // *Action: Retry with proper value_type. 26684, 00000, "invalid value for value_type" // *Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*' // *Action: Retry with proper value_type. 26685, 00000, "cannot apply transactions from multiple sources" // *Cause: Transactions from multiple sources were sent to the same apply // process. // *Action: Create multiple apply processes and create appropriate rules // so that transactions from only one source reach an apply // process. 26686, 00000, "cannot capture from specified SCN" // *Cause: An attempt was made to specify an invalid SCN. // *Action: Retry with a valid SCN. 26687, 00000, "no instantiation SCN provided for \"%s\".\"%s\" in source database \"%s\"" // *Cause: Object SCN was not set. If the object is a table, // then both fields will be filled, for example "SCOTT"."EMP". // If the object is a schema, only one field will be set, for // example "SCOTT"."". And if the object is the entire // database, no fields will be set, for example ""."". // *Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_SCN 26688, 00000, "missing key in LCR" // *Cause: Metadata mismatch, or not enough information in the user // generated LCR. // *Action: Alter the database object, or provide all defined keys // in the LCR. 26689, 00000, "column datatype mismatch in LCR" // *Cause: The datatypes of columns in the LCR are not the same as // the datatypes in the database object. // *Action: Alter the database object. 26690, 00000, "datatype not supported at non-Oracle system" // *Cause: One of the columns of the LCR being applied was of a datatype // not supported by either the target non-Oracle system or by the // Oracle transparent gateway through which the apply is being done. // *Action: Do not apply data of this type. If possible, filter out // columns containing such datatypes before applying. 26691, 00000, "operation not supported at non-Oracle system" // *Cause: The apply process attempted an operation that is either // not supported by the non-Oracle system or by the Oracle // transparent gateway through which the apply is being done. Some // kinds of DML (like procedure and function calls) and all DDL // will cause this error to be raised. // *Action: Do not attempt to apply such LCRs to non-Oracle systems. If // possible, filter out such LCRs before applying. 26692, 00000, "invalid value %s, %s should be in %s format" // *Cause: The parameter specified was not in the correct format. // *Action: Specify the parameter value in the correct format. 26693, 00000, "%s %s process dropped successfully, but error occurred while dropping rule set %s" // *Cause: An attempt to drop an unused rule set failed after dropping the // GoldenGate, XStream or Streams proccess successfully. // *Action: Check existence of rule set and manually drop if necessary. 26694, 00000, "error while enqueueing into queue %s.%s" // *Cause: An error occurred while enqueueing a message. // *Action: If the situation described in the next error on the stack // can be corrected, do so. 26695, 00000, "error on call to %s: return code %s" // *Cause: A locking related call failed. // *Action: Try the call again after fixing the condition indicated by // the return code. 26696, 00000, "no %s data dictionary for object with number %s and version number %s from source database %s" // *Cause: An attempt to access the database object failed because the // data dictionary for the object was either never populated // or it was purged. // *Action: Make sure the GoldenGate, XStream or Streams data dictionary is created by calling // DBMS_CAPTURE_ADM.PREPARE_%_INSTANTIATION. 26697, 00000, "LCR contains extra column '%s'" // *Cause: The LCR contained more columns than the replicated table. // *Action: Alter the database object. 26698, 00000, "%s did not have a %s rule set" // *Cause: The GoldenGate, XStream or Streams client does not have a rule set of the indicated type. // *Action: Verify that the GoldenGate, XStream or Streams client has a rule set of the specified // type, and retry the operation. 26699, 00000, "%s message consumer %s already exists" // *Cause: An attempt was made to create a GoldenGate, XStream or Streams // message consumer that already exists. // *Action: Either specify another message consumer or remove the // existing GoldenGate, XStream or Streams message consumer. 26700, 00000, "STREAMS tracing event" // *Document: NO // *Cause: // *Action: 26701, 00000, "%s process %s does not exist" // *Cause: An attempt was made to access a GoldenGate, XStream or Streams process // which does not exist. // *Action: Check with the relevant security views for the correct name of // the object. 26702, 00000, "shut the STREAMS/CDC apply engine down" // *Document: NO // *Cause: // *Action: 26703, 00000, "event for configuring STREAMS rules cache" // *Document: NO // *Cause: Not Applicable // *Action: Set this event only under the supervision of Oracle support. 26704, 00000, "The Owner instance %s of the queue table is not up or the QMN0 process is down." // *Cause: // *Action: Try again once the owner instance is up, and the QMN0 process on // that instance is up. 26705, 00000, "cannot downgrade capture process after Streams data dictionary has been upgraded" // *Cause: An attempt was made to downgrade a capture process after it has // upgraded the GoldenGate, XStream or Streams data dictionary. // *Action: Drop the capture process before attempting the downgrade. 26706, 00000, "cannot downgrade capture process" // *Cause: An attempt was made to downgrade a capture process that has a // higher version than the downgrade release version. // *Action: Drop the capture process after capture has finished consuming all // the redo logs before attempting the downgrade. 26707, 00000, "STREAMS or_expand complexity" // *Document: NO // *Cause: Not Applicable. // *Action: Set this event only under the supervision of Oracle Support. 26708, 00000, "remote DDL not supported by STREAMS : dblink %s" // *Cause: The apply process attempted to apply a DDL LCR via a dblink. // This is not supported. // *Action: Do not attempt to apply DDL LCRs via a dblink. If // possible, filter out DDL LCRs before applying. 26709, 00000, "Streams RFS restart" // *Cause: Remote file server (RFS) process was restarted to reflect a change // in DOWNSTREAM_REAL_TIME_MINE option of the GoldenGate, XStream or Streams capture process. // *Action: No action required. This is an informational message only. 26710, 00000, "incompatible version marker encountered during Capture" // *Cause: Capture process cannot mine redo from a version higher than the // current software release version. // *Action: Drop and recreate the capture process. 26711, 00000, "remote table does not contain a primary key constraint" // *Cause: The master table for remote apply does not constain 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. 26712, 00000, "remote object is \"%s\".\"%s\"\@\"%s\"" // *Cause: See the preceding error message to identify the cause. // This message names the remote object, usually a table or view, // for which an error occurred when GoldenGate, XStream or Streams tried to access it // for remote apply. // *Action: See the preceding error message. 26713, 00000, "remote object does not exist or is inaccessible" // *Cause: GoldenGate, XStream or Streams replication could not access the named table // or view at a remote database to apply changes. // *Action: Confirm that the given remote table or view exists and is // accessible through the given database link. When using a // Heterogeneous Services database link to access a non-Oracle system, // it may be necessary to check administration details for // network connections at the non-Oracle system. 26714, 00000, "User Error %s encountered during apply process" // *Cause: An error was encountered during an apply process. // *Action: Query the DBA_APPLY_ERROR view to determine the error and // take the appropriate action. 26715, 00000, "time limit reached" // *Cause: The specified time limit was reached for the GoldenGate, XStream or Streams process. // *Action: Restart the GoldenGate, XStream or Streams process, increasing the TIME_LIMIT // parameter if necessary. 26716, 00000, "message limit reached" // *Cause: The specified message limit was reached for the Capture process. // *Action: Restart the Capture process, increasing the MESSAGE_LIMIT // parameter if necessary. 26717, 00000, "SCN limit reached" // *Cause: The specified SCN limit was reached for the GoldenGate, XStream or Streams process. // *Action: Change the MAXIMUM_SCN parameter, then restart the // GoldenGate, XStream or Streams process. 26718, 00000, "transaction limit reached" // *Cause: The specified transaction limit was reached for the Apply process. // *Action: Restart the Apply process, increasing the // TRANSACTION_LIMIT parameter if necessary. 26719, 00000, "STREAMS tracing event" // *Document: NO // *Cause: // *Action: 26720, 00000, "STREAMS assemble lobs event" // *Document: NO // *Cause: // *Action: 26721, 00000, "enqueue of the LCR not allowed" // *Cause: An apply process attempted to enqueue an LCR with a LONG column. // This is not supported. // *Action: Modify rules or unset the enqueue destination to prevent // LCRs with LONG columns from being enqueued by the apply process. 26722, 00000, "STREAMS canonicalization event" // *Document: NO // *Cause: // *Action: 26723, 00000, "user \"%s\" requires the role \"%s\"" // *Cause: The caller did not have the specified role or called the procedure // from a definer's rights package or procedure. // *Action: Grant the specified role to the caller. If the procedure is called // from a definer's rights package or procedure, change the definer's // rights package or procedure to an invoker's rights package or // procedure. // Or grant all the privileges for the specified role explicitly. 26724, 00000, "only SYS is allowed to set the Capture or Apply user to SYS." // *Cause: The Capture or Apply user was specified as SYS by a user other // than SYS. // *Action: Set SYS as the Capture or Apply user while logged in as SYS. 26725, 00000, "cannot downgrade apply handlers" // *Cause: An attempt was made to downgrade apply handlers that are not // associated with a local database object, or the apply handlers // are associated with a specific apply process. // *Action: Drop the associated apply handlers before attempting the downgrade. 26726, 00000, "standby and DOWNSTREAM_REAL_TIME_MINE are incompatible" // *Cause: An attempt was made to set the standby database and // DOWNSTREAM_REAL_TIME_MINE option of the Oracle GoldenGate, XStream // or Oracle Streams capture process on the same database. // *Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a // Oracle GoldenGate, XStream or Oracle Streams capture process on a // standby database. Do not attempt to change a database role to // standby if there exists a capture process with the // DOWNSTREAM_REAL_TIME_MINE parameter set to Y. 26727, 00000, "Cannot alter queue_to_queue property of existing propagation." // *Cause: The queue_to_queue property was specified for an existing // propagation. // *Action: Pass NULL for the queue_to_queue argument. 26728, 00000, "event for configuring STREAMS apply segcol mapping cache" // *Document: NO // *Cause: Not Applicable // *Action: Set this event only under the supervision of Oracle support. 26729, 00000, "event for configuring STREAMS apply destination object cache" // *Document: NO // *Cause: Not Applicable // *Action: Set this event only under the supervision of Oracle support. 26730, 00000, "%s '%s' already exists" // *Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP // FILE failed because the item in question already exists. // *Action: Remove the object if appropriate and re-attempt the operation. 26731, 00000, "%s '%s' does not exist" // *Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was // specified that does not exist. // *Action: Make sure the object exists and re-attempt the operation. 26732, 00000, "invalid file group %s privilege" // *Cause: The specified privilege number that was specified is invalid. // *Action: Check specification of dbms_file_group for valid privileges. 26733, 00000, "timed-out waiting for file group lock" // *Cause: The procedure waited too long while getting a lock to perform a // file group repository operation. // *Action: Retry the operation. 26734, 00000, "different datafiles_directory_object parameter must be specified" // *Cause: The attempted operation involved datafiles platform conversion // which required the datafiles_directory_object parameter to be // specified for placing the converted data files. // *Action: Retry the operation after specifying a valid // datafiles_directory_object parameter. This directory must be // different from the directory objects for any of the datafiles for // the specified file group version. 26735, 00000, "operation not allowed on the specified file group version" // *Cause: One or more datafiles or export dump file(s) were missing from // the specified file group version. // *Action: Retry the operation after adding all the data files and Data Pump // dump file(s) to the specified version. 26736, 00000, "Data Pump error" // *Cause: A Data Pump error occurred when the procedure performed a // File Group Repository operation. // *Action: Check the error stack and trace file for error details. 26737, 00000, "version %s already has an export dump file" // *Cause: A Data Pump dump file was added to a file group version that already // has a dump file. // *Action: Remove the existing dump file if appropriate, and retry the // operation. 26738, 00000, "%s '%s' is not empty" // *Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained // objects. // *Action: Remove the child objects, then retry the operation. 26739, 00000, "FILE GROUP tracing event" // *Document: NO // *Cause: // *Action: 26740, 00000, "cannot downgrade because there are file groups" // *Cause: An attempt was made to downgrade a database that has file groups. // *Action: Drop all file groups before attempting the downgrade. 26741, 00000, "cannot assemble lobs" // *Cause: An attempt was made to assemble lobs, but the compatibility // of the source database for the LOB information is lower than 10.2.0. // *Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while // this handler is processing LOB information from a source // database with a compatibility level lower than 10.2.0. 26742, 00000, "Maximum number of ignored transactions exceeded" // *Cause: An attempt was made to add more than the allowed number of ignored // transactions. // *Action: Please clear the current list of ignored transactions. 26743, 00000, "Streams tracing event" // *Document: NO // *Cause: // *Action: 26744, 00000, "%s capture process \"%s\" does not support \"%s\".\"%s\" because of the following reason: %s" // *Cause: GoldenGate, XStream or Streams capture encountered a table with an unsupported // property. The most common reason is an unsupported column // data type. // *Action: Revise the Capture rules to skip over the table in // question. One way might be to add a negative rule // excluding changes from the unsupported table from being // captured. // // Also query the DBA_STREAMS_UNSUPPORTED view to determine // which tables are not supported by GoldenGate, XStream or Streams and for what // reason. Consider adding negative rules for any tables // that may be captured, but are present in this view. // // For potential workarounds to certain unsupported properties, see // Metalink. 26745, 00000, "cursors (%s) are not sufficient" // *Cause: The maximum number of open cursors was too small for GoldenGate, XStream or Streams Apply. // *Action: Increase the value of open_cursors. 26746, 00000, "DDL rule \"%s\".\"%s\" not allowed for this operation" // *Cause: A DDL rule was specified for this operation. // *Action: Specify a non-DDL rule for this operation. 26747, 00000, "The one-to-many transformation function %s encountered the following error: %s" // *Cause: The specified transformation function encountered an error. // *Action: Ensure that the function does not process or return DDL LCRs. // Also ensure that the function does not return NULL. 26748, 00000, "The one-to-one transformation function %s encountered the following error: %s" // *Cause: The specified transformation function encountered an error. // *Action: Ensure that the function does not return an LCR that has a // different type from the LCR which was passed to the function. // Also ensure that the function does not return NULL. // For DDL transformation functions, creating and returning a // new DDL LCR is not allowed. 26749, 00000, "STREAMS propagation batch size" // *Document: NO // *Cause: // *Action: 26750, 00000, "STREAMS internal transformation" // *Document: NO // *Cause: // *Action: 26751, 00000, "STREAMS testing event" // *Document: NO // *Cause: // *Action: Check that the type and value are correct. 26752, 00000, "Unsupported LCR received for \"%s\".\"%s\"" // *Cause: GoldenGate, XStream or Streams capture process received an LCR with unsupported // operation from LogMiner. // *Action: If this object is listed in DBA_STREAMS_UNSUPPORTED view, // modify rules to prevent changes made to this object from // getting captured. 26753, 00000, "Mismatched columns found in '%s.%s'" // *Cause: The columns in the LCR were not the same as the table in the // database. // *Action: Alter the database table. 26754, 00000, "cannot specify both one-to-one transformation function %s and one-to-many transformation function %s" // *Cause: Both a one-to-one transformation function and a one-to-many // transformation function were specified for a rule. // *Action: Remove either the one-to-one transformation function, or the // one-to-many transformation function. 26755, 00000, "STREAMS apply spill table partitioning event" // *Document: NO // *Cause: // *Action: 26756, 00000, "STREAMS apply spill table partition ceiling event" // *Document: NO // *Cause: // *Action: 26757, 00000, "Timed out waiting for remote operation on instance %s to finish" // *Cause: // *Action: Retry the operation at a later time. 26758, 00000, "%s skip LCR requested" // *Document: NO // *Cause: Internal error to handle skip LCR event. // *Action: 26759, 00000, "Maximum number of skip LCR requests exceeded" // *Document: NO // *Cause: // *Action: 26760, 00000, "Could not find message number %s for transaction with id %s" // *Cause: Error // *Action: Contact Oracle support" 26761, 00000, "Standby Redo Logs not available for real time mining" // *Cause: Standby Redo Logs required for real time mining by downstream // capture process were not available. // *Action: Check the configuration of Standby Redo Logs and retry the // operation at a later time. To start the capture process without // real time mining property, reset DOWNSTREAM_REAL_TIME_MINE // parameter of the capture process and retry the operation. 26762, 00000, "Cannot autogenerate name for parameter %s because of the following reason: %s" // *Cause: An error was encountered while attempting to generate a name for // a parameter which was passed a NULL value. // *Action: If possible, fix the error, otherwise specify the // parameter name explicitly. 26763, 00000, "invalid file type \"%s\"" // *Cause: An invalid file type was specified for the ASM file. // *Action: Check documentation for valid ASM file types. 26764, 00000, "invalid parameter \"%s\" for local capture \"%s\"" // *Cause: An invalid parameter was specified for the local capture process. // *Action: Check documentation for valid parameters. 26765, 00000, "invalid parameter \"%s\" for downstream capture \"%s\"" // *Cause: An invalid parameter was specified for the downstream capture // process. // *Action: Check documentation for valid parameters. 26766, 00000, "Unexpected redo pattern encountered by LogMiner" // *Cause: LogMiner encountered an unexpected redo pattern. This is usually // caused by tables with unsupported data types or newer table features. // *Action: Remove the capture rule for the table and restart capture. 26767, 00000, "Not enough redo log information for LogMiner" // *Cause: Direct-path SQL with NOLOGGING option or a SQL*Loader operation with // UNRECOVERABLE clause was specified for the table. // *Action: Remove the capture rule for the table and restart capture. 26768, 00000, "Maximum number of unsupported tables exceeded" // *Cause: An attempt was made to add more than the allowed number of // unsupported tables. // *Action: Clear the current list of unsupported tables. 26769, 00000, "STREAMS force lob assembly event" // *Document: NO // *Cause: // *Action: 26770, 00000, "Index-organized table not supported" // *Cause: // *Action: 26771, 00000, "User-defined column type not supported" // *Cause: // *Action: 26772, 00000, "Encrypted column not supported" // *Cause: // *Action: 26773, 00000, "Invalid data type for column \"%s\"" // *Cause: // *Action: 26774, 00000, "Queue table not supported" // *Cause: // *Action: 26775, 00000, "Temporary table not supported" // *Cause: // *Action: 26776, 00000, "Subordinate object not supported" // *Cause: // *Action: 26777, 00000, "External table not supported" // *Cause: // *Action: 26778, 00000, "File column not supported" // *Cause: // *Action: 26779, 00000, "Materialized view not supported" // *Cause: // *Action: 26780, 00000, "Object table not supported" // *Cause: // *Action: 26781, 00000, "Nested table not supported" // *Cause: // *Action: 26782, 00000, "Function-based index not supported" // *Cause: // *Action: 26783, 00000, "Column data type not supported" // *Cause: // *Action: 26784, 00000, "STREAMS internal event" // *Document: NO // *Cause: // *Action: Check that the type and value are correct. 26785, 00000, "Object has a NULL value" // *Cause: A method was invoked on a NULL object. // *Action: Initialize the object with a non-NULL value. 26786, 00000, "A row with key %s exists but has conflicting column(s) %s in table %s" // *Cause: The row to update or delete exists in the table but had // conflicting value for some columns. // *Action: For Streams, please define a conflict resolution, or resolve the // conflict and execute the error transaction using // DBMS_APPLY_ADM.EXECUTE_ERROR. // For logical standby, please verify the status of the database guard // to ensure local modifications are not allowed, then re-instantiate // the table and contact support if the problem persists. 26787, 00000, "The row with key %s does not exist in table %s" // *Cause: The row to update or delete does not exist in the table. // *Action: For Streams, please define a conflict resolution, or resolve the // conflict and execute the error transaction using // DBMS_APPLY_ADM.EXECUTE_ERROR. // For logical standby, please verify the status of the database guard // to ensure local modifications are not allowed, then re-instantiate // the table and contact support if the problem persists. 26788, 00000, "The column %s is not encrypted in the local database." // *Cause: The column in the destination database is NOT encrypted while // it is encrypted in the source database. // *Action: Set the corresponding column property in the destination database to // 'encrypted' or change the apply parameter, PRESERVE_ENCRYPTED_COLS, // to 'N' to supress the error. 26789, 00000, "Cannot split propagation %s because only one propagation originates from its source queue \"%s\".\"%s\"" // *Cause: Only one propagation originated from the propagation source queue. // *Action: Please do not split this propagation. 26790, 00000, "Requesting a lock on %s \"%s\" timed out" // *Cause: Could not get a lock on the object because another process was // holding the lock. // *Action: Please try later. 26791, 00000, "Cannot split or merge propagation \"%s\"" // *Cause: A process tried to split or merge this propagation, but failed and // left STREAMS in an inconsistent state. // *Action: Query DBA_RECOVERABLE_SCRIPT_BLOCKS view, and roll back the script // which tried to split or merge this propagation. 26792, 00000, "Invalid source database name %s" // *Cause: The value for the source database global name was not valid. // *Action: Specify a valid database global name. If the source database // is not the local database, check the listener is up and running. 26793, 00000, "Number of capture processes that enqueued message to queue \"%s\".\"%s\" not equal to one" // *Cause: Split-merge API requires only one capture process enqueued message // to the queue where the propagation originated // *Action: Please drop one capture, or split or merge another propagation. 26794, 00000, "Hierarchically enabled tables not supported" // *Cause: Hierarchically enabled tables are not supported. // *Action: Disable hierarchy for the table. 26795, 00000, "Cannot modify an LCR received from an XStream outbound server" // *Cause: An attempt was made to modify an LCR generated by an XStream outbound // server. // *Action: Clone the LCR generated by the XStream outbound server by // using the provided OCILCR* functions, such as OCILCRNew, // OCILCRHeaderSet, and OCILCRRowColumnInfoSet. Then modify the // cloned LCR. 26796, 00000, "STREAMS excessive IO event" // *Document: NO // *Cause: // *Action: 26797, 00000, "XStream Out feature unsupported below compatible 10.2.0" // *Cause: An attempt was made to create an XStream outbound server at // compatibility below 10.2.0. // *Action: Upgrade database compatibility to 10.2.0 or higher then retry. 26798, 00000, "LOB logical change record (LCR) missing LOB column in table \"%s\".\"%s\"" // *Cause: The apply slave could not fill update LOB because of missing LOB column. // *Action: Check that all LOB columns have been sent correctly. 26800, 00000, "Apply not the only subscriber for \"%s\".\"%s\"." // *Cause: The combined capture and apply optimization could not be used // since Apply was not the lone subscriber to the queue. // *Action: Apply has to be the only subscriber to the queue. 26801, 00000, "More than one subscriber for \"%s\".\"%s\"." // *Cause: Multiple subscribers were found when the combined capture and apply // optimization was configured to only work for one subscriber. // *Action: Configure a single subscriber, apply or propagation for the queue, // or enable the optimization for multiple subscribers. 26802, 00000, "Queue \"%s\".\"%s\" has messages." // *Cause: The combined capture and apply optimization could not be used // since the queue had messages. // *Action: Make sure queue is empty before starting apply and capture. 26803, 00000, "Subscribers have changed for queue \"%s\".\"%s\"." // *Cause: The combined capture and apply optimization could not be used // since the subscribers had changed. // *Action: Optimization can be used only if the queue has a single subscriber. 26804, 00000, "Apply \"%s\" is disabled." // *Cause: The apply process was disabled or aborted. // *Action: Start the apply process. 26805, 00000, "Queue \"%s\".\"%s\" has rule based subscribers." // *Cause: The combined capture and apply optimization could not be used // since the queue had rule based subscribers. // *Action: Make sure queue has no rule based subscribers before starting // apply and capture. 26806, 00000, "Remote database could not support combined capture and apply optimization." // *Cause: The remote database has a version lower than Oracle 11.0 and hence // does not understand combined capture and apply optimization. // *Action: Upgrade the remote database to Oracle 11.0 or above in order to // use the combined capture and apply optimization. 26807, 00000, "Database link is not NULL for Apply with the name \"%s\" ." // *Cause: The combined capture and apply optimization could not be used // since apply_database_link was not NULL. // *Action: Drop and recreate the apply with NULL value for apply_database_link. 26808, 00000, "Apply process %s died unexpectedly." // *Cause: Apply process died unexpectedly. // *Action: Check your system for anomalies and restart apply. // If this error persists, contact Oracle Support Services. // See trace file for more details. 26809, 00000, "Capture aborted: checkpoint-free mode requires combined capture and apply mode." // *Cause: The requirements for combined capture and apply mode were broken. // *Action: Restore the combined capture and apply mode and then // restart the capture. If combined capture and apply mode is no // longer desired, drop the existing checkpoint-free capture and // create another one that will take checkpoints. 26810, 00000, "Apply \"%s\" on database \"%s\" is in the mode of combined capture and apply." // *Cause: The combined capture and apply optimization could not be used // because Apply was already in the mode of combined capture and // apply. // *Action: Do not configure two captures for one apply. 26811, 00000, "Client has already attached to %s apply \"%s\"." // *Cause: The client has already attached to the specified apply process. // *Action: Detach apply process before reattach. 26812, 00000, "An active session currently attached to XStream server \"%s\"." // *Cause: An attempt was made to attach to the specified XStream server while // another session was attached to it. // *Action: Retry when there is no session attaching to the specified XStream // server. 26813, 00000, "The value for argument \"ARRAY_SIZE\" is too small" // *Cause: The value for argument "ARRAY_SIZE" was less than the number of // columns in the requested column list. // *Action: Check the return value for "NUM_COLUMNS" parameter then allocate // all input arrays to at least that size and invoke the same // OCI function again. 26814, 00000, "The value for argument %s exceeds maximum %s" // *Cause: The value for specified value exceeded the maximum allowed. // *Action: Correct the value of specified argument. 26815, 00000, "Error from Apply Network Receiver for Apply \"%s\" and Capture \"%s\"." // *Cause: The Apply Network Receiver aborted due to an unexpected error. // *Action: Query DBA_APPLY_ERROR to determine the error and then restart // the Capture and Apply. / 26816, 00000, "%s apply process \"%s\" (OS id %s) is exiting due to ORA-%s." // *Cause: An apply process encountered an unexpected error. // *Action: Query DBA_APPLY to examine the status of Apply and // restart Apply if needed. / 26817, 00000, "%s capture process \"%s\" is unable to communicate with capture server %s during initialization." // *Cause: Capture server might not be started properly // *Action: Fix any errors during capture server creation and re-start capture process / 26818, 00000, "%s capture process %s receives an error from capture server." // *Cause: Capture server received an error. // *Action: Check log for error details. / 26819, 00000, "%s capture server for apply \"%s\" and capture \"%s\"encounters disabled or aborted propagation \"%s\"." // *Cause: Propagation was disabled or aborted. // *Action: Start propagation. / 26820, 00000, "%s capture server for apply \"%s\" and propagation \"%s\" becomes active and needs join capture process \"%s\"." // *Cause: Capture server was waiting for propagation or apply to start // *Action: Capture process needs restart (done automatically). / 26821, 00000, "No propagation process found between source queue \"%s\".\"%s\" and destination queue \"%s\".\"%s\"." // *Cause: Propagation has not been configured. // *Action: Configure a propagation between specified queues and restart capture. / 26822, 00000, "Failure in creating capture servers (ksv error code %s)." // *Cause: Failure in ksv slave creation. // *Action: Identify the actual ksv error and act accordingly. / 26823, 00000, "%s capture server %s is unable to communicate with capture process \"%s\"." // *Cause: Capture process was not started properly or was aborted. // *Action: If Oracle GoldenGate, XStream or Streams capture process was stopped, then restart the // capture process. Otherwise, fix any errors during the capture // process creation and restart the capture process. / 26824, 00000, "user-defined XStream callback error" // *Cause: A value other than OCI_CONTINUE or OCI_SUCCESS was returned for // the user-defined XStream callback function. Any returned value // other than OCI_CONTINUE or OCI_SUCCESS is invalid. // *Action: Verify that either OCI_CONTINUE or OCI_SUCCESS is returned from // the user-defined XStream callback function. / 26825, 00000, "STREAMS process \"%s\" is not configured as an XStream outbound server." // *Cause: An attempt was made to attach to a STREAMS apply process, which was // not configured as an XStream outbound server. // *Action: Check the apply name or re-create the apply process as an XStream // outbound server. / 26826, 00000, "%s apply coordinator and apply slave are unable to communicate." // *Cause: GoldenGate, XStream or Streams Apply process may have died unexpectedly. // *Action: Check your system for anomalies and restart apply. // If this error persists, contact Oracle Support Services. // See trace file for more details. / 26827, 00000, "Insufficient privileges to attach to XStream outbound server \"%s\"." // *Cause: Sufficient privileges were not granted to attach to the specified // XStream outbound server. // *Action: Query DBA_XSTREAM_OUTBOUND view to get the connect_user value for // the specified outbound server. Then modify the application to // connect to the outbound server's database using this value. / 26828, 00000, "XStream outbound server \"%s\" requires combined capture and apply mode." // *Cause: The specified XStream outbound server was not in combined capture // and apply mode. // *Action: Restore the combined capture and apply mode and then // restart the capture. / 26829, 00000, "Cannot set \"DISABLE_ON_ERROR\" parameter to 'N'." // *Cause: An attempt was made to change the "DISABLE_ON_ERROR" parameter for // an XStream outbound server to 'N'. // *Action: Remove invalid statement. / 26830, 00000, "Cannot define handler for an XStream outbound server." // *Cause: An attempt was made to define a handler for an XStream outbound // server. // *Action: Remove invalid statement. / 26831, 00000, "Cannot delete or execute error transaction from XStream outbound server \"%s\"." // *Cause: An attempt was made to delete or execute an error transaction // from the specified XStream outbound server. // *Action: Remove invalid statement. / 26832, 00000, "Unable to create XStream outbound server \"%s\" due to existing handler." // *Cause: An attempt was made to create the specified XStream outbound server // while there was a handler defined for the specified server. // *Action: Use DBMS_APPLY_ADM.SET_DML_HANDLER procedure to remove all // handlers defined on the specified server then retry statement. / 26833, 00000, "%s failed to update acknowledgment SCN for propagation \"%s\" from capture \"%s\" to apply \"%s\"." // *Cause: propagation might have been modified after GoldenGate, XStream or Streams was started. // *Action: Ensure propagation is configured properly and restart GoldenGate, XStream or Streams. / 26834, 00000, "Unable to alter parameter '%s' because %s capture process is not configured to run locally" // *Cause: An attempt was made to alter the specified capture parameter when // the GoldenGate, XStream or Streams capture process was not configured to run on the local // database. // *Action: Remove the invalid parameter or use DBMS_CAPTURE_ADM.ALTER_CAPTURE // procedure to alter the parameter. / 26835, 00000, "The source database for XStream outbound server \"%s\" is invalid" // *Cause: An attempt was made to add an XStream outbound server with a // source database that was different from the associated capture's // source database. // *Action: Correct the value for the 'source_database' parameter in the call. / 26836, 00000, "The specified rules must be created from the same subsetting condition" // *Cause: An attempt was made to remove an outbound server's subset rules // when the specified INSERT, UPDATE, and DELETE rules were not // created from the same subsetting condition. // *Action: Correct the rules in the statement. / 26837, 00000, "Server \"%s\" is not an XStream inbound server" // *Cause: An attempt was made to execute a procedure not appropriate on // an XStream inbound server. // *Action: Replace with a procedure appropriate for an XStream inbound server // and resubmit. / 26838, 00000, "Setting apply parameter \"%s\" is not permitted for XStream Outbound Server" // *Cause: An attempt was made to set an apply parameter that was not applicable // for XStream Outbound Server. // *Action: Configure XStream Outbound Server using valid parameters. Check the // documentation for valid parameter values. / 26839, 00000, "Apply tag for apply \"%s\" is not permitted for XStream Outbound Server" // *Cause: An attempt was made to set an apply tag that was not applicable // for XStream Outbound Server. // *Action: Do not set the apply tag when using XStream Outbound Server. / 26840, 00000, "Combined capture and apply optimization is disabled because %s is unable to identify an apply for the source database \"%s\"." // *Cause: There were multiple Streams apply processes using the same queue // which made combined capture and apply (CCA) optimization not // possible. // *Action: If Streams performance is an issue, check the // "Combined Capture and Apply Optimization" chapter in the // "Oracle Streams Concepts and Administration" book. Then reconfigure // the Streams processes to meet this optimization's requirements. / 26841, 00000, "No subscribers are found for queue \"%s\".\"%s\"." // *Cause: No propagation or apply was configured for the specified queue. // *Action: Configure propagation or apply for the specified queue. / 26842, 00000, "Setting apply directive \"%s\" is not permitted for XStream Outbound Server" // *Cause: An attempt was made to set an apply directive that was not applicable // for XStream Outbound Server. // *Action: Configure XStream Outbound Server using valid directives. Check the // documentation for valid directives. / 26843, 00000, "Local propagation \"%s\" found for capture queue \"%s\".\"%s\"." // *Cause: The combined capture and apply optimization could not be used // because a local propagation was attached to the capture queue. // *Action: Remove the local propagation and restart capture. / 26844, 00000, "Found \"%s\" active automatic split jobs for %s Capture \"%s\" in DBA_STREAMS_SPLIT_MERGE" // *Cause: Only one active split job is allowed for each GoldenGate, XStream or Streams Capture, but // multiple active automatic split jobs were found in // DBA_STREAMS_SPLIT_MERGE. // *Action: Check trace to see how the jobs were submitted and drop them. / 26845, 00000, "Found \"%s\" active split rows with the same cloned %s Capture \"%s\" in DBA_STREAMS_SPLIT_MERGE" // *Cause: In DBA_STREAMS_SPLIT_MERGE, for active split rows, the column // CLONED_CAPTURE_NAME should be unique. However, multiple rows were // found whose ACTION_TYPE column is 'SPLIT', ACTIVE column is 'ACTIVE' // and have the same CLONED_CAPTURE_NAME. // *Action: Check trace to see how the rows were inserted and call // DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery. / 26846, 00000, "Found \"%s\" active automatic merge jobs for cloned %s Capture \"%s\" in DBA_STREAMS_SPLIT_MERGE" // *Cause: Only one active merge job is allowed for each cloned GoldenGate, XStream or Streams Capture // , but multiple active automatic merge jobs were found in // DBA_STREAMS_SPLIT_MERGE. // *Action: Check trace to see how the jobs were submitted and drop them. / 26847, 00000, "Found invalid %s type: \"%s\"" // *Cause: Invalid GoldenGate, XStream or Streams type to split off was found. Type should // only be 'PROPAGATION'(1) or 'APPLY'(2). // *Action: Check trace to see how the invalid GoldenGate, XStream or Streams type was created and // correct it. / 26848, 00000, "Split a nonexistent Streams Capture process \"%s\" in job \"%s\"" // *Cause: The job attempted to split a non-existent original Streams Capture. // *Action: Drop the split job, or wait until the Streams Capture comes to // existence. / 26849, 00000, "Split a nonsplittable %s Capture process \"%s\" in job \"%s\"" // *Cause: The job tried to split a GoldenGate, XStream or Streams Capture that was not splittable. // That is, the Capture either had less than two subscribers, // or it was not the only Capture of its queue. // *Action: Drop the split job, or wait untill the GoldenGate, XStream or Streams Capture becomes // splittable. / 26850, 00000, "Changes to queue subscribers were detected by %s capture process." // *Cause: The subscribers for capture queue might have changed. // *Action: Capture process will restart automatically. / 26851, 00000, "Unable to connect to apply \"%s\" because it has connected to another capture." // *Cause: Another capture process is already connected to apply. // *Action: Wait for the connected capture process to terminate or // abort the connected capture process. / 26852, 00000, "Invalid NULL value for column_value parameter." // *Cause: NULL is not allowed to be passed as the column value. // *Action: Replace NULL with a proper AnyData instance containing NULL, // e.g., sys.AnyData.ConvertVarchar2(NULL), as the column // value if the column value is NULL. // / 26853, 00000, "invalid cca maximum percentage %s" // *Cause: Specified percentage value was not in range 0 - 100. // *Action: Specify a percentage value in the range 0 - 100. / 26854, 00000, "STREAMS %s has no enqueue or dequeue privileges to the queue." // *Cause: The GoldenGate, XStream or Streams user did not have enqueue or dequeue // privilege to the queue. // *Action: Grant GoldenGate, XStream or Streams user enqueue or dequeue privileges to the queue. / 26855, 00000, "STREAMS %s has insufficient database privilege to access the queue." // *Cause: The GoldenGate, XStream or Streams user did not have sufficient database privilege to // access the queue. // *Action: Grant GoldenGate, XStream or Streams user database privileges to access the queue. / 26856, 00000, "STREAMS %s has insufficient database privilege to access the queue." // *Cause: The GoldenGate, XStream or Streams user did not have sufficient database privilege to // access the queue. // *Action: Grant GoldenGate, XStream or Streams user database privileges to access the queue. / 26857, 00000, "LCR position cannot be null (XID=%s)." // *Cause: The position of an LCR in the specified transaction was null. // *Action: Use OCILCRHeaderSet to define the LCR position. / 26858, 00000, "LCR position must be strictly increasing (XID='%s', LCR position='%s', previous position='%s')." // *Cause: The position of an LCR in the specified transaction was less than or // equal to the previous LCR in transaction. // *Action: Use OCILCRHeaderSet to correct the LCR position. / 26859, 00000, "Server \"%s\" is not an XStream outbound server" // *Cause: An attempt was made to execute a procedure not appropriate on // an XStream outbound server. // *Action: Replace with a procedure appropriate for an XStream outbound server // and resubmit. / 26860, 00000, "Different transactions must have different transaction IDs (XID='%s', LCR position='%s', previous commit position='%s')." // *Cause: The position of an LCR in the specified transaction was greater than the position // of the previous commit LCR in transaction with same transaction ID. // *Action: Use different transaction IDs for different transactions. / 26861, 00000, "XStream testing" // *Document: NO // *Cause: // *Action: 26862, 00000, "LCR position must be greater than the processed low position of the XStream inbound server (XID='%s', LCR position='%s')." // *Cause: The position of an LCR in the specified transaction // was less than or equal to the processed low postion of the // XStream inbound server. // *Action: Use OCILCRHeaderSet to correct the LCR position. / 26863, 00000, "Job \"%s\" showing as an active job in DBA_STREAMS_SPLIT_MERGE does not exist in DBA_SCHEDULER_JOBS." // *Cause: An active job showing in DBA_STREAMS_SPLIT_MERGE did not exist. // It may have been dropped accidently or something was wrong with it. // *Action: Check trace to identify the problem and call // DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery. / 26864, 00000, "Error occurred in %s automatic job: \"%s\"" // *Cause: An error has happened inside GoldenGate, XStream or Streams automatic job. // *Action: Check trace for more detail. / 26865, 00000, "must send a COMMIT LCR to end transaction '%s' before sending another transaction" // *Cause: An attempt was made by a client application to send LCRs for a // new transaction before sending a COMMIT LCR for the specified // transaction. // *Action: Modify the client application to send a COMMIT LCR at the end // of the specified transaction. / 26866, 00000, "The Queue of %s Apply process \"%s\" is not changeable." // *Cause: Not all of the conditions for the Queue of a GoldenGate, XStream or Streams Apply process // to be changeable were met. Conditions are: -The Apply process is not // running. -The Apply process has no error. -The Apply process has no // spilling. -The Apply process is not used for XStream Outbound or // Inbound Servers. -The Apply process is a local Apply process. -The // corresponding GoldenGate, XStream or Streams Capture process should be stopped. // *Action: Make sure all of the conditions are met. / 26867, 00000, "%s must be called during OCIXStreamOutLCRReceive execution" // *Cause: An attempt was made to execute the specified function while // OCIXStreamOutLCRReceive call was not in progress. // *Action: Check your program and make sure the specified call is invoked // during OCIXStreamOutLCRReceive callback function. / 26868, 00000, "%s must be called during OCIXStreamInLCRSend execution" // *Cause: An attempt was made to execute the specified function while // OCIXStreamInLCRSend call was not in progress. // *Action: Check your program and make sure the specified call is invoked // during OCIXStreamInLCRSend callback function. / 26869, 00000, "must attach to an XStream inbound server before executing %s function" // *Cause: An attempt was made to invoke the specified function // before executing OCIXStreamInAttach call. // *Action: Add OCIXStreamInAttach call before the specified function. / 26870, 00000, "cannot call %s while OCIXStreamInLCRCallbackSend call is still executing." // *Cause: An attempt was made to invoke the specified call while // OCIXStreamInLCRCallbackSend call was executing. // *Action: Check your program and remove the specified call when there is an // OCIXStreamInLCRCallbackSend call in progress. / 26871, 00000, "unexpected %s call (expecting %s)" // *Cause: Could be one of the following reasons: // 1) An attempt was made to invoke OCIXStreamInChunkSend when // the most recent LCR or chunk sent did not have the // OCI_XSTREAM_MORE_ROW_DATA flag set; // 2) An attempt was made to invoke OCIXStreamInLCRSend when // the most recent LCR or chunk sent had OCI_XSTREAM_MORE_ROW_DATA // flag set. 26872, 00000, "must attach to an XStream outbound server before executing %s function" // *Cause: An attempt was made to invoke the specified function // before executing OCIXStreamOutAttach call. // *Action: Add OCIXStreamOutAttach call before the specified function. / 26873, 00000, "cannot call %s while OCIXStreamOutLCRCallbackReceive call is still executing." // *Cause: An attempt was made to invoke the specified call while // OCIXStreamOutLCRCallbackReceive call was executing. // *Action: Check your program and remove the specified call when there is an // OCIXStreamOutLCRCallbackReceive call in progress. / 26874, 00000, "%s Capture process \"%s\" cannot be split." // *Cause: An attempt was made to split a GoldenGate, XStream or Streams Capture process that could not be split. // That is, the Capture process either had less than two subscribers, // or it was not the only Capture process of its queue. // *Action: Wait until the GoldenGate, XStream or Streams Capture process can be split. / 26875, 00000, "Timeout while %s automatic split job \"%s\" waits for the subscriber \"%s\" of Capture process \"%s\" to acknowledge split" // *Cause: To split a subscriber of a GoldenGate, XStream or Streams Capture process, an automatic // split job needs to wait until the subscriber acknowledges the split. // The wait timed out. // *Action: / 26876, 00000, "invalid processed low-watermark (current position=%s; new position=%s)" // *Cause: An attempt was made to set the processed low-watermark to a value // that was less than the current processed low-watermark. // *Action: Correct the processed low-watermark in OCIXStreamOutProcessedLWMSet // call. / 26877, 00000, "must reattach after an OCIXStreamOut call was interrupted" // *Cause: An attempt was made to execute another OCIXStreamOut API when // an earlier call was interrupted because the XStream outbound // server was disabled or the client requested cancellation of // the operation. // *Action: Execute OCIXStreamOutAttach call to reattach to the same XStream // outbound server. / 26878, 00000, "inconsistent input LCR (LCR is '%s' type, expecting '%s')" // *Cause: An attempt was made to send an LCR that was not consistent with // the specified LCR type. // *Action: Correct your application to specify an LCR type that agrees with // the LCR to be sent. / 26879, 00000, "\"SET_ENQUEUE_DESTINATION\" directive is not permitted on rules used by XStream outbound server \"%s\"" // *Cause: One or more rules, used by the specified XStream outbound server, // had SET_ENQUEUE_DESTINATION directive defined. // *Action: Execute the following: // 1) Execute query // SELECT xr.rule_owner, xr.rule_name, xr.rule_set_owner, // xr.rule_set_name // FROM dba_apply_enqueue e, dba_xstream_rules xr // WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name // AND xr.streams_name = ; // 2) For each rule returned, execute DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION // procedure to set the destination queue to null, or execute // DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its associated // rule set. / 26880, 00000, "\"SET_EXECUTE\" directive is not permitted on rules used by XStream outbound server \"%s\"" // *Cause: One or more rules, used by the specified XStream outbound server, // had SET_EXECUTE directive defined. // *Action: Execute the following: // 1) Execute query // SELECT xr.rule_owner, xr.rule_name, xr.rule_set_owner, // xr.rule_set_name // FROM dba_apply_execute e, dba_xstream_rules xr // WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name // AND xr.streams_name = ; // 2) For each rule returned, use DBMS_APPLY_ADM.SET_EXECUTE // procedure to set the EXECUTE parameter to TRUE, or use // DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its associated // rule set. / 26881, 00000, "ORA-%s: %s raised in %s automatic %s job:\"%s\".\"%s\" for Capture process \"%s\" and cloned Capture process \"%s\"." // *Cause: An error was raised in a GoldenGate, XStream or Streams automatic split/merge job for the given original and cloned Capture processes. // *Action: Check the corresponding split/merge row in DBA_STREAMS_SPLIT_MERGE view, alert log and trace file for details. / 26882, 00000, "Timeout while %s automatic split/merge job:\"%s\".\"%s\" tried to lock Capture process \"%s\"." // *Cause: The GoldenGate, XStream or Streams Capture process could be locked by other automatic split/merge jobs. // *Action: No action required. The GoldenGate, XStream or Streams automatic split/merge job will retry automatically. / 26883, 00000, "Timeout due to %s Apply process \"%s\" while merge original Capture process \"%s\" and cloned Capture process \"%s\"." // *Cause: When merging two GoldenGate, XStream or Streams Capture processes, the merge needs to wait untill the // Apply process of the cloned Capture process goes // ahead of the slowest subscriber of the original Capture // process. This wait timed out. // *Action: Make sure the GoldenGate, XStream or Streams Apply process still works properly. / 26884, 00000, "Not allowed to specify OCI_LCR_ROW_COLVAL_OLD with OCILCR_NEW_ONLY_MODE." // *Cause: An attempt was made to call OCILCRRowColumnInfoGet function with // OCI_LCR_ROW_COLVAL_OLD and OCILCR_NEW_ONLY_MODE. // *Action: Change OCI_LCR_ROW_COLVAL_OLD to OCI_LCR_ROW_COLVAL_NEW or // remove OCILCR_NEW_ONLY_MODE argument. / 26885, 00000, "OCIXStreamInCommit called before OCIXStreamInFlush" // *Cause: An attempt was made to call OCIXStreamInCommit before calling OCIXStreamInFlush. // *Action: Call OCIXStreamInFlush prior to calling OCIXStreamInCommit. / 26886, 00000, "LCR commit position ('%s') must be greater than the applied high position of the XStream inbound server (position='%s')." // *Cause: The position of the commit LCR was less than or equal to the applied // high postion of the XStream inbound server. // *Action: Set the commit position higher than the applied high position. / 26887, 00000, "Insufficient privileges to attach to XStream inbound server \"%s\"." // *Cause: Sufficient privileges were not granted to attach to the specified // XStream inbound server. // *Action: Query DBA_XSTREAM_INBOUND view to get the apply_user value for // the specified XStream outbound server. Then, modify the application // to connect to the inbound server's database using this value. / 26888, 00000, "Redo compatibilty must be 10.2 or greater" // *Cause: XStream Out requires redo comptibility to be 10.2 or greater. // *Action: Drop the outbound server. / 26889, 00000, "LOB assembly not supported for PDML parent transaction %s, child transaction %s." // *Cause: LOB assembly is not supported for PDML transactions. // *Action: Disable LOB assembly, or filter out the PDML transaction. / 26890, 00000, "Invalid update LCR on Oracle Sequence \"%s\".\"%s\"" // *Cause: The new value column list of an update LCR on an Oracle Sequence // did not have non-null columns \"CYCLE#\", \"INCREMENT$\", \"CACHE\" // and \"HIGHWATER". // *Action: Make sure the new value column list has all the required columns. // This might be a user error if the LCR is from an XStream In client. / 26891, 00000, "Target Oracle Sequence \"%s\".\"%s\" has inconsistent parameters with the source." // *Cause: The source and target Oracle Sequences did not have the identical // cache size, increment value, and cycle flag needed for replication // purposes. // *Action: Make sure the source and target Oracle Sequences have identical // parameters. This might be a user error if the LCR is from an // XStream In client. / 26892, 00000, "XStream feature not supported" // *Cause: The XStream feature was not supported. // *Action: No action necessary. / 26893, 00000, "Input LCR must be a commit LCR" // *Cause: The input LCR was not a commit LCR. // *Action: Make sure the input LCR is a commit LCR. / 26894, 00000, "Invalid \"%s\" in Apply Progress redo" // *Cause: The value of the field reported was possibly corrupted. // *Action: Contact Oracle Support Services. / 26895, 00000, "Setting parameter \"%s\" of Streams process \"%s\" is only permitted for Oracle GoldenGate or XStream." // *Cause: An attempt was made to set a parameter that is only allowed // for XStream. // *Action: Oracle GoldenGate license is needed to use this parameter. / 26896, 00000, "Attempted to connect multiple Oracle GoldenGate Capture processes, including \"%s\", with XStream outbound server \"%s\" through queue \"%s\".\"%s\"" // *Cause: An attempt was made to connect multiple Oracle GoldenGate Capture // processes through a queue with the XStream outbound server. // *Action: Each XStream outbound server can only connect with one co-located // Capture process. Remove extra Capture processes. / 26898, 00000, "Unable to create \"%s\" because there is an Oracle Capture process using the same queue \"%s\".\"%s\"." // *Cause: An attempt was made to create an inbound server using the same // queue that was used by an Oracle Capture process. // *Action: Resubmit the statement using another queue name. / 26899, 00000, "internal %s error" // *Cause: An internal Streams, XStream or GoldenGate error has occurred. // *Action: Please contact Oracle customer support. / 26900, 00000, "Streams failed to update data dictionary table for propagation \"%s\" from capture \"%s\" to apply \"%s\"." // *Cause: The data dictionary table was corrupted. // *Action: Validate the data dictionary table to restart GoldenGate, XStream or Streams capture process. / 26901, 00000, "%s propagation sender in the combined capture and apply mode is to be suspended while apply is disabled." // *Cause: The corresponding subscriber was dropped or split. // *Action: No action necessary. / 26902, 00000, "%s propagation sender in the combined capture and apply mode is to be suspended while apply is enabled." // *Cause: The corresponding subscriber was dropped or split. // *Action: No action necessary. / 26903, 00000, "Invalid edition name \"%s\"" // *Cause: The edition associated with the LCR did not exist in the // destination database. // *Action: Check if the edition needs to be created manually on the destination // database or if the CREATE EDITION statement for this edition // has been applied properly on the destination database. / 26904, 00000, "Invalid bind variable \"%s\" in LCR field expression." // *Cause: In the statement handler, the bind variables listed in // the SQL expression did not match the allowed Logical Change Record field names. // *Action: Verify that all the bind variables listed in the expression are // legal Logical Change Record fields. / 26905, 00000, "Invalid LCR method expression \"%s\" in statement handler." // *Cause: The Logical Change Record method listed was not allowed in the statement handler. // *Action: Verify that the Logical Change Record method listed in the expression is a legal // DBMS_LCR method. 26906, 00000, "No change handler exists." // *Cause: There was no change handler for the specified apply, operation, // source table, change table, and capture values. // *Action: Query DBA_APPLY_CHANGE_HANDLERS view to find the correct change // handler. 26907, 00000, "Insufficient privileges to set converge tag" // *Cause: Privileges were insufficient to set converge tag. // *Action: The invoker needs EXECUTE_CATALOG_ROLE or execute privilege on // DBMS_STREAMS_ADM to set converge tag. Grant appropriate privileges // to the invoker. / 26908, 00000, "XStream API must be executed using a dedicated server process." // *Cause: An attempt was made to execute XStream API using a shared server // process. // *Action: Replace the connect string in the client application to use a // dedicated server process. / 26909, 00000, "cannot reexecute an eager error" // *Cause: An attempt was made to reexecute an eager error transaction. // An eager transaction is applied before the apply process sees // the commit or rollback for the transaction. // *Action: Fix the cause of the eager error and restart the apply process. // When apply is restarted, capture will automatically resend // the transaction, and the transaction will be applied by the // apply process. / 26910, 00000, "user error %s encountered in eager mode" // *Cause: An error was encountered during eager apply. An eager // transaction is applied before the apply process sees the commit // or rollback for the transaction. If an error occurs during // an eager transaction, the transaction will be rolled back. // *Action: Query the DBA_APPLY_ERROR view to determine the error and // take the appropriate action. The apply process will need to be // restarted to apply the transaction that had the error. When // apply is restarted, capture will automatically resend the // transaction, and the transaction will be applied by the apply // process. / 26911, 00000, "invalid oldest position (current position=%s; new position=%s)" // *Cause: An attempt was made to set the oldest position to a value // that was less than the current value. // *Action: Correct the oldest_position argument in // OCIXStreamOutProcessedLWMSet2 call. / 26912, 00000, "not allowed to invoke '%s' while in committed data-only mode" // *Cause: An attempt was made to call the specified API while the attached // XStream server was in committed data-only mode. // *Action: Perform one of the following: // 1) If the invalid call is OCIXStreamOutProcessedLWMSet2, then change it // to OCIXStreamOutProcessedLWMSet or pass a null oldest_position to // OCIXStreamOutProcessedLWMSet2 call. // 2) If the invalid call is OCIXStreamInProcessedLWMGet2, then change it // to OCIXStreamInProcessedLWMGet or pass a null oldest_position to // OCIXStreamInProcessedLWMGet2 call. / 26913, 00000, "must connect to instance %s where %s %s server \"%s\" is running" // *Cause: The client application was not connected to the same Oracle RAC // instance as the specified Oracle GoldenGate or XStream server. // *Action: Connect to the specified instance using the network service name // obtained from the following query: // SELECT network_name FROM all_queues q, all_xstream_outbound ob // WHERE q.owner = ob.queue_owner AND q.name = ob.queue_name // AND server_name = ''; / 26914, 00000, "Unable to communicate with %s capture process \"%s\" from outbound server \"%s\"." // *Cause: Capture process might not haven been started properly or was aborted. // *Action: If Oracle GoldenGate, XStream or Oracle Streams capture process // was stopped, then restart the capture process. Otherwise, query the // DBA_CAPTURE view to determine the reason and take the appropriate // action. // If the error is ORA-4031, either increase the initialization // parameter STREAMS_POOL_SIZE or increase the capture parameter // MAX_SGA_SIZE or increase both. // Refer to the XStream documentation for additional information on // these parameters. / 26915, 00000, "Unable to return Logical Change Record (LCR) information due to missing data dictionary." // *Cause: The current session was unable to return the requested information on // the given LCR due to missing dictionary data on that LCR. // *Action: Detach and reattach the XStream outbound server. Then retry the // current call. / 26916, 00000, "Must call OCIPOGGRedoLogOpen function before OCIPOGGRedoLogRead" // *Cause: An attempt was made to call OCIPOGGRedoLogRead before calling // OCIPOGGRedoLogOpen. // *Action: Add OCIPOGGRedoLogOpen call before OCIPOGGRedoLogRead. / 26917, 00000, "OCIPOGG API must be executed using a dedicated server process." // *Cause: An attempt was made to execute OCIPOGG API using a shared server // process. // *Action: Replace the connect string in the client application to use a // dedicated server process. / 26918, 00000, "Must use '%s' procedure for outbound server \"%s\"." // *Cause: An attempt was made to execute START_APPLY on an outbound server // that uses uncommitted data mode. // *Action: Use the specified procedure instead. / 26919, 00000, "Capture \"%s\" is not associated with queue \"%s\".\"%s\". " // *Cause: The capture specified in the ADD_OUTBOUND procedure was not // associated with the specified queue. // *Action: Resubmit the ADD_OUTBOUND procedure after removing either the // capture_name or the queue_name argument. / 26920, 00000, "%s outbound server \"%s\" has been stopped." // *Cause: The specified outbound server was stopped. // *Action: Execute START_OUTBOUND procedure to restart the outbound server or // execute OCIXStreamOutAttach function to reattach to the outbound // server. / 26921, 00000, "Cannot alter the start SCN or time of %s Capture \"%s\"." // *Cause: An attempt was made to alter the start SCN or time for a capture // while other outbound servers were still attached to it. // *Action: Execute the following: // 1) Get the names of other outbound servers currently attached to the // specified Capture using the query: // SELECT server_name // FROM dba_xstream_outbound // WHERE (status = 'ATTACHED') AND // (server_name <> '') AND // (capture_name = ''); // 2) Detach the client application from each server_name returned. // 3) Retry the operation. / 26922, 00000, "user %s does not have SELECT ANY TRANSACTION privilege" // *Cause: An attempt was made to start the capture process or attach to // an outbound server when the specified user did not have // SELECT ANY TRANSACTION privilege. // *Action: Grant SELECT ANY TRANSACTION privilege to the specified user and // resubmit the failed operation. / 26923, 00000, "cannot configure %s outbound server \"%s\" with %s capture \"%s\" due to different purpose" // *Cause: An attempt was made to configure an outbound server with a // capture used for different purpose. // *Action: Execute the following: // 1) Get the purpose of each capture and its associated queue: // SELECT capture_name, queue_owner, queue_name, purpose // FROM dba_capture; // 2) Resubmit the statement using a queue or capture with the same purpose. / 26924, 00000, "cannot configure %s using \"%s\".\"%s\" queue because it is used by \"%s\" for %s purpose" // *Cause: An attempt was made to configure the specified process using a // queue already used by another process for different purpose. // *Action: Resubmit the statement using another queue of the same purpose. / 26925, 00000, "cannot configure outbound server \"%s\" with capture \"%s\" because it is not using apply-state checkpoint" // *Cause: An attempt was made to configure an outbound server with a // capture not using apply-state checkpoint. // *Action: Specify a different capture in the ADD_OUTBOUND procedure // or re-create the capture and resubmit the statement. / 26926, 00000, "Unable to attach because capture \"%s\" is missing dictionary redo logs" // *Cause: The specified capture was unable to locate the dictionary redo log. // *Action: Check the state of the specified capture from GV$STREAMS_CAPTURE // to determine the SCN or file name of the missing log file. Confirm // that the file name exists and is accessible online and also in the // DBA_REGISTERED_ARCHIVED_LOG view. In addition, for local capture, // confirm that an entry exists for the file in the V$ARCHIVED_LOG view. // If an entry is missing, it can be added using the ALTER DATABASE // REGISTER .... LOGFILE command, specifying the keyword LOGICAL // LOGFILE or PHYSICAL LOGFILE as appropriate. / 26927, 00000, "altering an outbound server with a remote capture is not allowed" // *Cause: An attempt was made to alter an outbound server with a remote // capture. // *Action: None 26928, 00000, "Unable to communicate with %s apply coordinator process \"%s\" from outbound server \"%s\"." // *Cause: A timeout occurred while waiting for apply coordinator to respond. // *Action: Check the state of the specified apply coordinator from // GV$STREAMS_APPLY_COORDINATOR view. // Determine the reason for apply coordinator's unresponsiveness. // If streams_pool_size is not set or set with an inadequate value, consider // setting or increasing the value of this parameter. / 26929, 00000, "altering an outbound server with a remote capture is not allowed" // *Cause: An attempt was made to alter an outbound server with a remote // capture. // *Action: None / 26930, 00000, "User \"%s\" does not have privileges to perform this operation" // *Cause: An attempt was made to create, alter, or drop a process that has // a different user (such as capture user or apply user) than the // invoking user. // *Action: Use the DBMS_XSTREAM_AUTH.GRANT_ADMIN_PRIVILEGE or // DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE procedures to grant the // invoking user proper privileges. / / 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, "failed to obtain file size limit" // *Cause: getrlimit system call returned an error // *Action: check errno 27033, 00000, "failed to obtain file size limit" // *Cause: ulimit system call returned an error // *Action: check errno 27034, 00000, "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, "created file already 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, "file 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, "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, 00000, "NFS file system where the file is created or resides is not mounted with correct options" // *Cause: The file was on an NFS partition and either reading the mount tab // file failed or the partition wass not mounted with the correct // mount option. // *Action: Make sure mount tab file has read access for Oracle user and // the NFS partition where the file resides is mounted correctly. // For the list of mount options to use refer to your platform // specific documentation. /27055 27056, 00000, "could not delete file" // *Cause: unlink system call returned error // *Action: check errno 27057, 00000, "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, "file I/O question parameter is invalid" // *Cause: internal error, invalid query is being asked // *Action: check for trace file and contact Oracle Support 27059, 00000, "could not reduce file size" // *Cause: ftruncate system call returned error // *Action: check errno 27060, 00000, "could not set close-on-exec bit on file" // *Cause: fcntl system call returned error // *Action: check errno 27061, 00000, "waiting for async I/Os failed" // *Cause: aiowait function returned error // *Action: check errno 27062, 00000, "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, "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, "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, "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, "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, "size of I/O 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, "I/O 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, "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, "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, "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, "File 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, "Trying to close a file which has async I/Os pending to be dequeued" // *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, "unable to determine limit for open files" // *Cause: The getrlimit() system call returned an error. // *Action: Check errno. 27075, 00000, "SSTMOFRC constant too large" // *Cause: internal error // *Action: check for trace file and contact Oracle Support 27076, 00000, "unable to set limit for open files" // *Cause: The setrlimit() system call returned an error. // *Action: Check errno. 27077, 00000, "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. 27078, 00000, "unable to determine limit for open files" // *Cause: The getrlimit() system call returned an error. // *Action: Check errno. 27079, 00000, "unable to set async IO limit" // *Cause: The setting of the limit for async I/O has failed. // *Action: Check errno. 27080, 00000, "too many files open" // *Cause: The number of files opened has reached the system limit. // *Action: Check the error, and set system configuration values. 27081, 00000, "unable to close the file" // *Cause: The close() system call failed. // *Action: Check errno. 27083, 00000, "waiting for async I/Os failed" // *Cause: The aio_waitn() library call returned an error. // *Action: Check errno. 27084, 00000, "unable to get/set file status flags " // *Cause: The fcntl() system call with F_GETFL/F_SETFL flag returned an error. // *Action: Check errno. 27086, 00000, "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, "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, "unable to get file status" // *Cause: file not open or file descriptor is invalid. 27089, 00000, "unable to release advisory lock" // *Cause: release of file lock failed // *Action: see errno 27090, 00000, "Unable to reserve kernel resources for asynchronous disk I/O" // *Cause: The system call to reserve kernel resources for asynchronous I/O // has failed. // *Action: Check errno 27091, 00000, "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, "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 27093, 00000, "could not delete directory" // *Cause: rmdir system call returned error // *Action: check errno 27094, 00000, "raw volume used can damage partition table" // *Cause: A raw device with VTOC information was provided as a database file. // *Action: Make sure the disk partition that is provided to Oracle // does not start at sector 0 27095, 00000, "fail to get the disk sector size" // *Cause: The system call to get the sector size failed. Additional information // indicates which function encountered the error. // *Action: Check error number. 27096, 00000, "fail to get file size" // *Cause: The system call to get file size failed. Additional information // indicates which function encountered the error. // *Action: Check error number. / / 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 remove 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 27129, 00000, "VLM Map operation failed" // *Document: NO // *Cause: Internal error // *Action: Contact Oracle Support Services. 27130, 00000, "VLM Unmap operation failed" // *Document: NO // *Cause: Internal error // *Action: Contact Oracle Support Services. 27131, 00000, "VLM Add operation failed" // *Document: NO // *Cause: Internal error // *Action: Contact Oracle Support Services. 27132, 0000, "VLM Remove operation failed" // *Document: NO // *Cause: Internal error // *Action: Contact Oracle Support Services. 27133, 00000, "unable to determine stacksize" // *Cause: getrlimit() call failed // *Action: Contact Oracle Support Services. 27134, 00000, "unable to set stacksize" // *Cause: setrlimit() call failed // *Action: Contact Oracle Support Services. 27135, 00000, "Operating System hard stack limit is set too low" // *Cause: Operating System hard stack limit was set too low. // *Action: Check additional information for current and minimum limit. // Increase the Operating System hard stack limit and retry. 27136, 00000, "MPMT and VLM are both enabled" // *Cause: When the _mpmt_enabled parameter is set to TRUE, none of the // following parameters should be set to TRUE: // * use_indirect_buffers // * _db_block_cache_protect // * _db_block_cache_clone // // *Action: Either turn off Multi Process Multi Threads (MPMT) or // turn off all the other parameters. 27137, 00000, "unable to allocate large pages to create a shared memory segment" // *Cause: Parameter USE_LARGE_PAGES set to only, but large pages were not // configured properly // *Action: Check alert file for more information / / 27140-27189 RESERVED FOR SKGP / 27140, 0000, "attach to post/wait facility failed" // *Cause: The program attempted to initialize the post/wait facility, // but the facility could not be attached. // *Action: Check for additional errors and contact Oracle Support. 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 27158, 0000, "process control failure" // *Cause: Oracle was unable to set the specified process control. // *Action: Consult the Oracle Administrator's Guide. 27159, 0000, "failure setting process scheduling priority" // *Cause: Oracle was unable to set the scheduling priority desired. // *Action: Consult the Oracle Administrator's Guide. 27160, 0000, "process requested to perform operation" // *Cause: The current process was requested to perform an operation by // another process. // *Action: This is used internally; no action is required. 27161, 0000, "request for Oracle binary information failed" // *Cause: The program was unable to get information about the Oracle binary. // *Action: Check for additional errors and contact Oracle support. 27162, 0000, "thread creation failed" // *Cause: The program was unable to create a thread. // *Action: Check errno and contact Oracle support. 27163, 0000, "out of memory" // *Cause: The program ran out of memory when allocating a temporary // data structure. // *Action: Increase the amount of memory on the system. 27164, 0000, "tried to join detached thread" // *Cause: The program tried to join a detached thread. // *Action: This is an internal error; contact Oracle support. 27165, 0000, "tried to join thread that does not exist" // *Cause: The program tried to join a thread that does not exist. // *Action: This is an internal error; contact Oracle support. 27166, 0000, "tried to join current thread" // *Cause: A thread in the program tried to join itself. // *Action: This is an internal error; contact Oracle support. 27167, 0000, "Attempt to determine if Oracle binary image is stored on remote server failed" // *Cause: OS dependent operation failed // *Document: NO // *Action: This is an internal error; contact Oracle support. 27168, 0000, "Translation from hostname to network address failed" // *Cause: Internal error // *Action: Contact Oracle Support Services. / / 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. 27214, 00000, "skgfrsfe: file search failed" // *Cause: The FindNextFile function returned unxpected error. // *Action: Check errors on the error stack for an explanation // why the search for files could not be successfully executed. 27215, 00000, "skgfgsmcs: sbtinfo2 returned unknown file" // *Cause: During an sbtinfo2() call, the media management software // returned information about an unknown backup file. // *Action: Contact the media management vendor. 27216, 00000, "skgfgsmcs: sbtinfo2 returned a malformed response" // *Cause: The media management software returned a malformed // response during an sbtinfo2() call. // *Action: Contact the media management vendor. 27217, 00000, "failed to load Media Management Library from secure location" // *Cause: SBT libraries were not installed in a secure location. // *Action: Remove SBT_SECURE parameter or Request third party vendors // to provide patch that installs SBT libraries in secured // locations as mandated by Oracle. 27230, 00000, "OS system call failure" // *Cause: OS system call failed // *Action: check errno and contact Oracle support / / 27231 - 27249 reserved for sskgof / 27231, 00000, "unable to close file" // *Cause: A file could not be closed. // *Action: See accompanying errors. 27232, 00000, "unable to get file information" // *Cause: Information about the file could not be obtained. // *Action: See accompanying errors. 27233, 00000, "file is not an ELF file" // *Cause: A file was not an ELF file. // *Action: Check for file corruption and contact Oracle Support Services. 27234, 00000, "unable to read file" // *Cause: A file could not be read. // *Action: See accompanying errors. 27235, 00000, "unable to map file region into memory" // *Cause: A file region could not be mapped into memory. // *Action: See accompanying errors. 27236, 00000, "unable to unmap file from memory" // *Cause: A file region could not be unmapped from memory. // *Action: See accompanying errors. 27237, 00000, "ELF file is not a relocatable object file" // *Cause: An ELF file was not the expected type. // *Action: Supply the expected type of file. 27238, 00000, "ELF file is not an executable" // *Cause: An ELF file was not the expected type. // *Action: Supply the expected type of file. 27239, 00000, "ELF file is not a shared object file" // *Cause: An ELF file was not the expected type. // *Action: Supply the expected type of file. 27240, 00000, "ELF file does not have a required section" // *Cause: An ELF file did not have a required section. // *Action: Contact Oracle Support Services. 27241, 00000, "ELF-shared library has multiple sections of the same type" // *Cause: An ELF-shared library had multiple sections of the same type. // *Action: Contact Oracle Support Services. 27242, 00000, "ELF file has invalid hash table entry size" // *Cause: An ELF file had an invalid hash table entry size. // *Action: Contact Oracle Support Services. 27243, 00000, "ELF file has too many relocation sections" // *Cause: An ELF file had too many relocation sections. // *Action: Contact Oracle Support Services. 27244, 00000, "unable to determine base value for data relocation from ELF file" // *Cause: An ELF file was missing important information. // *Action: Contact Oracle Support Services. 27245, 00000, "unable to dlopen() binary image" // *Cause: A file could not be accessed via dlopen(). // *Action: See accompanying errors and make file available. 27246, 00000, "unable to open file" // *Cause: A file could not be opened. // *Action: See accompanying errors and make file available. / / 27250 - 27269 reserved for sm / 27250, 00000, "OS system call failure" // *Cause: OS system call failed // *Action: check errno and 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 / / 27351 - 27499 RESERVED FOR NEW DATABASE SCHEDULER / 27351, 00000, "conflicting values of job attributes %s and %s" // *Cause: The values of two attributes passed in to the CREATE_JOBS call // or the JOB object constructor conflicted with each other. This is // usually because both attributes cannot be non-NULL at the same // time. // *Action: Resolve the conflict by changing the value of one of the // attributes and issue the call again. 27352, 00000, "unable to get lock on queue" // *Document: NO // *Cause: An internal scheduler synchronization error // *Action: Contact Oracle Customer Support. 27353, 00000, "job attribute %s is missing" // *Cause: An attribute needed to fully specify a job was not passed in // to a call to CREATE_JOBS or the JOB object constructor. // *Action: Issue the call again with the required attribute set. 27354, 00000, "attribute %s cannot be set for lightweight jobs" // *Cause: The CREATE_JOBS call or the JOB object constructor was called // with an argument that is illegal in the case of lightweight jobs. // *Action: Set the argument to the default value and issue the call again. 27355, 00000, "unable to lock row cache entry" // *Document: NO // *Cause: Failure in scheduler concurrency control // *Action: Contact Oracle Customer Support. 27356, 00000, "invalid job argument" // *Cause: An invalid job argument was passed into either the CREATE_JOBS // call or the JOB object constructor. // *Action: Correct the argument value and issue the call again. 27357, 00000, "duplicate reference to job object %s" // *Cause: The scheduler CREATE_JOBS call had two or more references // to the same job. // *Action: Eliminate the duplicate references and issue the call again. 27358, 00000, "unknown allocation type" // *Document: NO // *Cause: Failure in scheduler memory allocation routines // *Action: Contact Oracle Customer Support. 27359, 00000, "duplicate reference to attribute %s of job %s" // *Cause: The scheduler SET_JOB_ATTRIBUTES call had two or more // references to a specific atrribute of a job. // *Action: Eliminate the duplicate references and issue the call again. 27360, 00000, "unknown operation type" // *Document: NO // *Cause: Failure in scheduler linked list routines // *Action: Contact Oracle Customer Support. 27361, 00000, "scheduler API invoked with illegal or inconsistent arguments" // *Cause: A DBMS_SCHEDULER API call was invoked with either illegal or // inconsistent arguments. // *Action: Refer to scheduler documentation for the call, make the necessary // changes and issue the call again. 27362, 00000, "batch API call completed with errors" // *Cause: Some of the commands submitted to a scheduler batch API call // could not be successfully carried out because of errors. Other // commands in the batch may have completed successfully. // *Action: Check the view SCHEDULER_JOB_ERRORS to see which commands failed // and why. Make the appropriate corrections and submit the failed // commands again. 27363, 00000, "invalid program for lightweight job" // *Cause: You tried to create a lightweight job using an invalid // program. A program used in a lightweight job has to be enabled, // has to be in the same schema as the job, and the program action // has to be either a PL/SQL block or a stored procedure. // *Action: Use a valid program for the lightweight job. 27364, 00000, "remote database %s already registered as %s" // *Cause: The user attempted to register a remote database that was // already registered. // *Action: To update the registration information, the REPLACE argument // of the REGISTER_REMOTE_DATABASE procedure should be set to // TRUE. If the registration information is already current, no // further action is needed. 27365, 00000, "job has been notified to stop, but failed to do so immediately" // *Cause: The job specified in the stop_job command // cannot be stopped immediately(because it is rolling back or blocked // on a network operation), but it has been notified to stop. This // means it will be stopped as soon as possible after its current // uninterruptable operation is done. // *Action: No action is required for the job to be stopped, but calling // stop_job with force (if you have the privilege) // may cause the job to be stopped sooner. 27366, 00000, "job \"%s.%s\" is not running" // *Cause: An attempt was made to stop a job that was not running. // *Action: Verify the status of the job. If the job is running but this // message is still being returned, contact Oracle support. 27367, 00000, "program \"%s.%s\" associated with this job is disabled" // *Cause: An attempt was made to run a job whose program has been disabled. // *Action: Reenable the program before running the job. 27368, 00000, "job execution abandoned" // *Document: NO // *Cause: A slave had picked up a job for execution that was either currently // being run or had just finished running on another RAC instance, so // the slave abandoned the job without executing it. // *Action: This error is used as part of communication between various // scheduler modules. It should not be seen by an end-user. If // this message is seen, contact Oracle Customer Support. 27369, 00000, "job of type EXECUTABLE failed with exit code: %s" // *Cause: A problem was encountered while running a job of type EXECUTABLE. // The cause of the actual problem is identified by the exit code. // *Action: Correct the cause of the exit code and reschedule the job. 27370, 00000, "job slave failed to launch a job of type EXECUTABLE" // *Cause: The scheduler ran into an error when the job slave tried to start // a job of type EXECUTABLE. The rest of the error stack will provide // more detailed information on what the exact problem was. // *Action: Correct the problem specified in the error stack and reschedule // the job. 27371, 00000, "jobs of type EXECUTABLE are not supported on this platform" // *Cause: The user tried to create a job or program of type EXECUTABLE on a // platform where such jobs are not supported. // *Action: Switch to a different platform or create a different type of job // or program. 27372, 00000, "length of action and arguments exceeds platform limit %s" // *Cause: The total length of the job or program action and the arguments // exceeds the platform limit specified. // *Action: Reduce the total length by specifying fewer and/or shorter // arguments 27373, 00000, "unknown or illegal event source queue" // *Cause: The source queue specified for the event based job or event // based schedule was either not found or was of the wrong type. // *Action: Check if the queue exists. If it does make sure it is a // multiple consumer queue and it is a post 8.1 compatible queue. // Single consumer queues and old-style queues cannot be used // as event source queues. 27374, 00000, "insufficient privileges on event source queue" // *Cause: The job owner had insufficient privileges on the event source // queue that was specified for the job. // *Action: The job owner has to have dequeue privileges on event source // queue or he has to have manage queue or dequeue any queue // system privileges. Make sure one of these privileges is // granted. 27375, 00000, "valid agent name must be specified for secure queues" // *Cause: The queue specified for the event based job or schedule was // a secure queue and either no agent name was specified or // an invalid agent name was specified. // *Action: If no agent name was specified, retry the call with a valid // agent name. If the agent name was valid, check if the agent // is currently subscribed to the queue and, in the case of jobs, // check is the agent has been authorized to act as the job // owner. 27376, 00000, "event condition cannot be NULL" // *Cause: A null event condition was passed in for an event based job // or schedule. This is not allowed. // *Action: Pass in a legal event condition. 27377, 00000, "windows cannot have event based schedules" // *Cause: Event based schedules for windows are currently not supported. // *Action: Use a time-based schedule instead. 27378, 00000, "cannot stop jobs of type EXECUTABLE on this platform" // *Cause: An attempt was made to stop a job of type EXECUTABLE on a platform // where the stop operation was not supported. // *Action: If the attempt to stop the job was made with the FORCE option // set to FALSE, try again but change the FORCE option to TRUE. 27379, 00000, "INSTANCE_ID attribute conflicts with job class settings" // *Cause: The value of the INSTANCE_ID attribute of the job conflicted with the // value of the SERVICE attribute of its job class. // *Action: Change the value of the INSTANCE_ID attribute or place the job // in a job class whose settings do not conflict with the // INSTANCE_ID attribute. Then re-enable the job. 27399, 00000, "job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege" // *Cause: The owner of a job of type EXECUTABLE does not have the // CREATE EXTERNAL JOB system privilege. // *Action: Grant the CREATE EXTERNAL JOB system privilege to the job owner or // create another job in a schema which does have the CREATE EXTERNAL // JOB system privilege. / / 27401 - 27410 Reserved for scheduler events / 27401, 00000, "Scheduler debug event" // *Document: NO // *Cause: // *Action: 27402, 00000, "Scheduler tracing event" // *Document: NO // *Cause: // *Action: / 27403, 00000, "scheduler stop job event" // *Document: NO // *Cause: // *Action: / / 27411 - 27420 Reserved for scheduler repeat interval errors / 27411, 0000, "empty string is not a valid repeat interval." // *Cause: An empty string '' was provided as a repeat interval for a window // or a schedule. // *Action: Specify a valid repeat interval, e.g., // 'FREQ=DAILY;BYHOUR=8;BYMINUTE=0;BYSECOND=0' for a job that executes // daily at 8am. / 27412, 00000, "repeat interval or calendar contains invalid identifier: %s" // *Cause: The calendar string or calendar definition for the repeat interval // of a job, schedule or window contained an unsupported keyword or // reference to an undefined calendar. // *Action: Correct the repeat interval such that it no longer contains the // invalid keyword. / 27413, 00000, "repeat interval is too long" // *Cause: The repeat interval consisted of a calendar string larger than the // maximum size allowed. // *Action: Use a shorter calendar string for the repeat interval. / 27414, 00000, "Invalid %s clause value" // *Cause: The BY clause value was not recognized or was out-of-range for the // frequency specified. // *Action: Specify a valid BY clause value. / / 27415, 00000, "repeat interval or calendar must start with a frequency clause" // *Cause: The specified calendar string for the repeat interval did not start // with a frequency clause. // *Action: Create a repeat interval that starts with a frequency clause,for example // 'FREQ=YEARLY;BYMONTH=FEB' / 27416, 00000, "BYDAY clause in repeat interval or calendar contains an invalid weekday" // *Cause: The BYDAY clause of the repeat interval contained a value that // did not represent a weekday. // *Action: Use the correct three letter abbreviations for weekdays, for example // MON for Monday and FRI for Friday. / 27417, 00000, "BYWEEKNO clause requires YEARLY clause" // *Cause: A repeat interval or calendar contained a BYWEEKNO clause // with a frequency other than yearly. // *Action: Remove the BYWEEKNO clause or change the frequency to YEARLY. / 27418, 00000, "syntax error in repeat interval or calendar" // *Cause: The repeat interval or calendar definition was not // recognized as valid syntax. // *Action: Specify a valid repeat interval. / 27419, 00000, "unable to determine valid execution date from repeat interval" // *Cause: The specified repeat interval contained conflicting clauses that // made it impossible to ever find a matching date, e.g., // 'FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31'. Alternatively, // the scheduler reached its maximum number of attempts to try to // find a valid execution date. This occurs when theoretically // there is a valid execution date far in the future, but the // scheduler took too many attempts to determine this date. // *Action: Remove the conflicting clauses, or simplify the repeat interval // so that it is easier to determine the next execution date. / 27420,00000, "Following message from %s interval interpreter" // *Cause: The repeat interval or calendar definition was not // recognized as valid syntax. // *Action: Specify a valid repeat interval. 27421, 00000, "calendar expression restriction %s encountered" // *Cause: The calendar expression was not valid because a limit test failed. // For example, the maximum value of the interval that can be specified // in the INTERVAL clause is limited to a value derived from the frequency clause. // *Action: Specify a valid calendar definition. / 27422, 00000, "usage of %s not supported in embedded calendar application \"%s\".\"%s\"" // *Cause: The main calendar definition used an embedded calendar in an INCLUDE, // EXCLUDE, INTERSECT, or FREQ clause for which extra limitations // apply. // *Action: Remove the specific clause from the calendar definition. / 27423,00000, "calendar clause %s specified more than once" // *Cause: The calendar definition contained a clause that was specified // twice or more times. // *Action: Append the values in the second clause to the first clause // and remove the second clause. 27424,00000, "calendar clauses %s and %s are incompatible" // *Cause: The calendar definition contained clauses that were incompatible. // *Action: Change or remove either clause. / / / 27431 - 27500 Scheduler API errors continuation / 27431, 00000, "chain %s.%s has a user-managed rule set" // *Cause: An attempt was made to modify a rule set that is not managed by the // Scheduler. // *Action: Modify the rule set directly using the dbms_rule_adm package or // create another chain without specifying a rule set. 27432, 00000, "step %s does not exist for chain %s.%s" // *Cause: The step specified does not exist for the given chain. // *Action: Reissue the command using a step that exists for this chain. 27433, 00000, "cannot alter state of step %s for job %s.%s to %s" // *Cause: The step cannot be changed to the requested state. The state of a // running step cannot be changed. A step which is running or has // already run cannot be run again. // *Action: Wait until the step has finished running. 27434, 00000, "cannot alter chain step job %s.%s.%s" // *Cause: A step job of a running chain cannot be altered, only stopped or // dropped. // *Action: Stop or drop the chain step job or alter the running chain step // instead. 27435, 00000, "chain job terminated abnormally" // *Cause: A chain job has ended abnormally. The error code for the running // chain could not be retrieved. // *Action: No action necessary. The job will run again when it is scheduled // to. 27451, 00000, "%s cannot be NULL" // *Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL. // *Action: Reissue the command using a non-NULL value for the specified // attribute. 27452, 00000, "%s is an invalid name for a database object." // *Cause: An invalid name was used to identify a database object. // *Action: Reissue the command using a valid name. 27453, 00000, "%s is an invalid job or program argument name." // *Cause: An invalid job or program argument name was specified. // *Action: Reissue the command using a valid name for this argument. 27454, 00000, "argument name and position cannot be NULL" // *Cause: The name or position of a program or job argument was defined as // NULL. // *Action: Reissue the command providing either a valid argument name or // valid argument position. 27455, 00000, "Only \"SYS\" is a valid schema for a %s." // *Cause: A non-SYS schema was specified for an object that must be in the // SYS schema. // *Action: Reissue the command, leaving out the schema name or using the // schema name of SYS. 27456, 00000, "not all arguments of program \"%s.%s\" have been defined" // *Cause: The number_of_arguments attribute of the named program did not // match the actual number of arguments that have been defined. // *Action: Define as many arguments as the number of arguments, or change // the number of arguments. 27457, 00000, "argument %s of job \"%s.%s\" has no value" // *Cause: No value was provided for the job argument with the specified // position. // *Action: Provide a value for the job argument using any of the // set_job_xxxx_value() routines. Or, when using a named program, // specify a default value for the corresponding argument of the // program. 27458, 00000, "A program of type PLSQL_BLOCK cannot have any arguments." // *Cause: An attempt was made to create or enable a program of type // PLSQL_BLOCK with arguments. This is not allowed. // *Action: Change the number of arguments to zero, or change the type // of the program. 27459, 00000, "A program of type EXECUTABLE must have character-only arguments." // *Cause: A program of type EXECUTABLE was created or enabled with one or // more arguments of non-character datatypes. // *Action: Change the arguments to be of character-only datatypes. 27460, 00000, "cannot execute disabled job \"%s.%s\"" // *Cause: An attempt was made to run a job that is disabled. // *Action: Enable the job and then reschedule the job. 27461, 00000, "The value for attribute %s is too large." // *Cause: The value that was provided for the specified attribute was too // large. // *Action: Reissue the command using a smaller or shorter value. 27463, 00000, "invalid program type %s" // *Cause: An invalid program type was specified. // *Action: Reissue the command using a valid program type. 27464, 00000, "invalid schedule type %s" // *Cause: An invalid schedule type was specified. // *Action: Reissue the command using a valid schedule type. 27465, 00000, "invalid value %s for attribute %s" // *Cause: An invalid value was provided for the specified attribute. // *Action: Reissue the command using a valid value for this attribute. 27466, 00000, "internal scheduler error: %s" // *Document: NO // *Cause: The scheduler ran into an internal error. // *Action: Contact Oracle Customer Support. 27467, 00000, "invalid datatype for %s value" // *Cause: The value provided for the named scheduler attribute was of an // invalid datatype. // *Action: Reissue the command using a value of the correct datatype. 27468, 00000, "\"%s.%s\" is locked by another process" // *Cause: An attempt was made to read or modify the state of the named // scheduler object when another process was also updating the same // object and held the lock. // *Action: Retry the operation. Scheduler locks are held for a very // short duration. If the error persists, contact Oracle Support. 27469, 00000, "%s is not a valid %s attribute" // *Cause: A non-existant attribute was specified. // *Action: Reissue the command using a valid attribute for that specific // scheduler object. 27470, 00000, "failed to re-enable \"%s.%s\" after making requested change" // *Cause: A change was made to an enabled scheduler object that caused it // to become disabled. // *Action: Alter the object so that it becomes valid and then enable it. 27471, 00000, "window \"%s.%s\" is already closed" // *Cause: An attempt was made to close a window that was not open. // *Action: No action required. 27472, 00000, "invalid metadata attribute %s" // *Cause: An invalid metadata attribute was specified. // *Action: Reissue the command using a valid metadata attribute. 27473, 00000, "argument %s does not exist" // *Cause: An argument which was specified does not exist. // *Action: Reissue the command using an argument name defined by the program // or using a valid argument position. 27474, 00000, "cannot give both an argument name and an argument position" // *Cause: An argument was specified using both a name and a position. // *Action: Reissue the command using either the argument name or the argument // position but not both. 27475, 00000, "\"%s.%s\" must be a %s" // *Cause: An object of the wrong type was specified. For example, a table // could have been passed to the drop_job() procedure. // *Action: Reissue a different command applicable to this object type or // reissue the same command using an object of the valid type. 27476, 00000, "\"%s.%s\" does not exist" // *Cause: A database object was specified that does not exist. // *Action: Reissue the command using an object that exists or create a new // object and then reissue this command. 27477, 00000, "\"%s.%s\" already exists" // *Cause: An attempt was made to create an object with a name that has // already been used by another object in the same schema. // *Action: Reissue the command using a different name or schema. 27478, 00000, "job \"%s.%s\" is running" // *Cause: An attempt was made to drop a job that is currently running. // *Action: Stop the job and then reissue the command, or reissue the command // specifying the force option to stop the job first. 27479, 00000, "Cannot %s \"%s.%s\" because other objects depend on it" // *Cause: An attempt was made to drop or disable a scheduler object that has // jobs associated with it without specifying the force option. // *Action: Alter the associated jobs so they do not point to the scheduler // object being dropped or disabled and then reissue the // command. Alternatively reissue the command specifying the force // option. If // the force option is specified and a scheduler object is being // dropped, all associated jobs will be disabled. 27480, 00000, "window \"%s\" is currently open" // *Cause: An attempt was made to drop a window that is currently open, or // to manually open a window while another window is already open. // *Action: Close the window that is open and then reissue the command, or // reissue the command while setting the force option to TRUE. 27481, 00000, "\"%s.%s\" has an invalid schedule" // *Cause: An attempt was made to enable a job or window that has an invalid // schedule. // *Action: Alter the schedule of the job or window so that it is valid and // then reissue the enable command. 27483, 00000, "\"%s.%s\" has an invalid END_DATE" // *Cause: An attempt was made to enable a job or window that has an invalid // end_date. Either the end_date is before the start_date or the // end_date is in the past. // *Action: Alter the job or window so that the end date becomes valid // (possibly null) and then reissue the command. 27484, 00000, "Argument names are not supported for jobs without a program." // *Cause: An attempt was made to set or reset a job argument by using the // name of the argument. Identifying job arguments by their name is // only supported in combination with jobs that are based on programs. // Jobs that are not using a program cannot have named arguments. // *Action: Use argument position instead of name and then issue the command // again. 27485, 00000, "argument %s already exists at a different position" // *Cause: An attempt was made to create or replace an argument with a name // that is already used by an argument at a different position. // *Action: Use a different name for the argument or drop or alter the // argument which already exists with this name and then reissue the // command. 27486, 00000, "insufficient privileges" // *Cause: An attempt was made to perform a scheduler operation without the // required privileges. // *Action: Ask a sufficiently privileged user to perform the requested // operation, or grant the required privileges to the proper user(s). 27487, 00000, "invalid object privilege for a %s" // *Cause: The granted object privilege is not valid for the specified // scheduler object. // *Action: Check the scheduler documentation to verify which object privileges // can be granted on which scheduler objects. 27488, 00000, "unable to set %s because %s was/were already set" // *Cause: An attempt was made to set an object's attribute even though one // or more conflicting attributes of the same object had already been // set. // *Action: Set the other conflicting attributes to NULL and then reissue // the command. 27489, 00000, "unable to process job \"%s.%s\" from job class \"%s\"" // *Cause: An error was encountered while processing the named job from // the specified job class. // *Action: Resolve the error for this job and then reissue the command. // See the next error message on the stack to find out what the error // for the job is. 27490,0000, "cannot open disabled window \"%s.%s\"" // *Cause: The user tried to open a disabled window. // *Action: Enable the window and then try to open it again. 27491,0000, "repeat_interval and start_date cannot both be NULL" // *Cause: An attempt was made to set both repeat_interval and start_date // to equal NULL for a Scheduler window or schedule. // *Action: If either repeat_interval or start_date is set to equal NULL, // the other should be set to a non-NULL value. 27492,0000, "unable to run job \"%s.%s\": scheduler unavailable" // *Cause: A job run with current session set to false can not be issued // if the scheduler is not active. Check value of job_queue_processes // parameter, issue dbms_ijob.set_enabled(true), // database is in upgrade/migrade mode, database is in data guard // mode, or scheduler attribute SCHEDULER_DISABLED is set to TRUE // *Action: Run the job in the current session or activate the scheduler / / 27500-27599 RESERVED FOR IPC ERRORS / 27500, 00000, "inter-instance IPC error" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the extra information and contact Oracle Support Services. 27501, 00000, "IPC error creating a port" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27502, 00000, "IPC error deleting OSD context" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27503, 00000, "IPC error attempting to cancel request" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27504, 00000, "IPC error creating OSD context" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27505, 00000, "IPC error destroying a port" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27506, 00000, "IPC error connecting to a port" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27507, 00000, "IPC error disconnecting from a port" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27508, 00000, "IPC error sending a message" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27509, 00000, "IPC error receiving a message" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27510, 00000, "IPC error waiting for a request to complete" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27512, 00000, "IPC error posting a process" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27513, 00000, "parameter %s contains invalid value %s" // *Cause: The program could not identify the value as an IP address. // *Action: Change the value to be a valid IP address. 27514, 00000, "IPC error copying memory to remote process" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. // 27528, 00000, "<>" // *Cause: // *Action: // 27529, 00000, "<>" // *Cause: // *Action: // 27530, 00000, "<>" // *Cause: // *Action: // 27531, 00000, "<>" // *Cause: // *Action: 27532, 00000, "IPC global name service error" // *Cause: The global name space service used by KSXP reported an error // *Action: Check additional error messages in the process trace file and // contact Oracle Support Services. // 27533, 00000, "<>" // *Cause: // *Action: // 27534, 00000, "<>" // *Cause: // *Action: // 27535, 00000, "<>" // *Cause: // *Action: // 27536, 00000, "<>" // *Cause: // *Action: // 27537, 00000, "<>" // *Cause: // *Action: // 27538, 00000, "<>" // *Cause: // *Action: // 27539, 00000, "<>" // *Cause: // *Action: // 27540, 00000, "<>" // *Cause: // *Action: // 27541, 00000, "<>" // *Cause: // *Action: 27542, 00000, "Failed to unprepare a buffer prepared for remote update" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27543, 00000, "Failed to cancel outstanding IPC request" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27544, 00000, "Failed to map memory region for export" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27545, 00000, "Fail to prepare buffer for remote update" // *Cause: This is an operating system/cluster interconnect error. // *Action: Check the value of errno and contact Oracle Support Services. 27546, 00000, "Oracle compiled against IPC interface version %s.%s found version %s.%s" // *Cause: A misconfiguration or installation error occurred. // *Action: Install the IPC library for this release of Oracle. // 27547, 00000, "Unable to query IPC OSD attribute %s" // *Cause: This is an operating system-dependent IPC error. // *Action: Contact Oracle support Services. 27548, 00000, "Unable to unprepare IPC buffer" // *Cause: This is an operating system-dependent IPC error. // *Action: Contact Oracle support Services. // 27550, 00000, "Target ID protocol check failed. tid vers=%s, type=%s, remote instance number=%s, local instance number=%s" // *Cause: The local Oracle Real Application Cluster instance and remote // instance are running with incompatible implementation of the // inter-instance IPC protocol library. A misconfiguration or // installation error occurred. // *Action: Check additional error messages in the alert log and the process // trace file. 27551, 00000, "Number of IPC ports exceeds OSD limit %s" // *Document: NO // *Cause: Attempted to create more IPC ports than is supported by OSD // *Action: Contact Oracle Support Services. // / / 27600-27799 RESERVED FOR EXADATA (SAGE) and HOST/CELL ERRORS / / 27601, 00000, "Cell storage initialization failed, cell library error code [%s]" // *Cause: Cell storage client did not succeed in initializing. // *Action: Check the value of errno and contact Oracle Support Services. 27602, 00000, "Failure to publish network status information, cell library error code [%s]" // *Cause: Network status information publishing failed. // *Action: Check the value of errno and contact Oracle Support Services. 27603, 00000, "Cell storage I/O error, I/O failed on disk %s at offset %s for data length %s" // *Cause: Cell storage I/O read or write failed, possibly due to a configuration problem or a hardware failure. // *Action: Check the value of errno and contact Oracle Support Services. 27604, 00000, "Cell storage ioctl error, ioctl failed on disk %s" // *Cause: Ioctl operation on a cell storage disk failed. // *Action: Check the value of errno and contact Oracle Support Services. 27605, 00000, "Smart I/O failed as a handle could not be obtained to the cell \"%s\" as the cell is not accessible." // *Cause: The cell could have been unavailable. // *Action: Ensure the cell is available. Check the network connectivity. 27606, 00000, "Smart I/O failed because the diskgroup was found to be unmounted. tablespace number: \"%s\", file number: \"%s\"" // *Cause: The diskgroup to which the specified file belongs was found // to be unmounted. // *Action: Ensure that the diskgroup to which the specified file belongs // is mounted. 27607, 00000, "Smart I/O failed because there were no online disks. tablespace number: \"%s\", file number: \"%s\"" // *Cause: There were no online disks found for the specified file. // *Action: Ensure the diskgroup to which the specified file belongs to is mounted. // Ensure that the disks are online. Check the availability of // cells and check the network. 27608, 00000, "Smart I/O failed because the disk \"%s\" on the cell \"%s\" was not open. error code: \"%s\", \"%s\"" // *Cause: The specified disk on the specified cell could not be opened. // *Action: Ensure the cell is available. Check the network. 27609, 00000, "Smart I/O failed due to a network error to the cell \"%s\". error code \"%s\", \"%s\"" // *Cause: The specified cell could not be connected to. // *Action: Ensure that the cell is available. Check the network. 27610, 00000, "Smart I/O failed due to shortage of memory on the cell \"%s\"" // *Cause: The specified cell had a shortage of memory to perform smart I/O. // *Action: Reduce the parallel degree or number of Oracle sessions executing // smart I/O. 27611, 00000, "Smart I/O failed due to a block corruption detected on the host. The block was received from cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\"" // *Cause: The data block indicated was corrupted on the host, but // a corruption was not found on the cell. // *Action: This may be due to a transient network error or a real block // corruption. Check your network for any errors. Analyze the // segment to which the file belongs. If there is indeed a // corruption, try to restore the block using RMAN block recovery. // If there is a trace file, report the errors in it to Oracle // Support Services. If analyze did not report an error and network // did not have any error, report the problem to Oracle Support // Services as this appears to be a software error. 27612, 00000, "Smart I/O failed due to a block corruption detected on the cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\"" // *Cause: The data block indicated was found to be corrupted on the cell. // *Action: This may be due to a software error or a real data corruption. // Analyze the segment. If there is indeed a block corruption, try to // restore the block using RMAN block level recovery. If there // is a trace file, report the errors in it to Oracle Support // Services. If analyze did not report an error, report // the problem to Oracle Support Services as this appears to // be a software error. 27613, 00000, "Smart I/O failed due to an I/O error on the cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\" I/O size: \"%s\"" // *Cause: An I/O request failed on the specified cell and disk. // *Action: Check the specified disk on the cell. 27614, 00000, "Smart I/O failed due to an error \"%s, %s\" from the cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\" I/O size: \"%s\"" // *Cause: An I/O request failed, due to an internal error on the specified // cell and disk. // *Action: Report the problem to Oracle Support Services along with // the process trace file and alert log. 27615, 00000, "Smart I/O file to ASM disk translation failed with error: %s." // *Cause: An internal error caused a smart I/O operation to fail. // *Action: Report the problem to Oracle Support Services along with // the process trace file and alert log. 27616, 00000, "ASM Allocation Unit: %s" // *Cause: This error message is usually accompanied by another message, // indicating the real problem. This message exists to provide // additional information to Oracle Support Services. // *Action: Check the next error message. 27617, 00000, "Smart I/O failed because of an internal error. Cell \"%s\", disk \"%s\", cell library error code \"%s, %s\", error information \"%s\"" // *Cause: An internal error caused a smart I/O operation to fail. // *Action: Report the problem to Oracle Support Services along with // the process trace file and alert log. 27618, 00000, "Smart I/O failed because of an internal error. Cell \"%s\", cell library error code \"%s, %s\", error information \"%s\"" // *Cause: An internal error caused a smart I/O operation to fail. // *Action: Report the problem to Oracle Support Services along with // the process trace file and alert log. 27619, 00000, "Smart I/O failed because of an internal error when determining the time zone file version. Error code \"%s\"" // *Cause: An internal error caused a smart I/O operation to fail. // *Action: Report the problem to Oracle Support Services along with // the process trace file and alert log. 27621, 00000, "The value of %s is not valid for parameter %s" // *Cause: Incorrect value is specified for an internal parameter. // *Action: This parameter should only be set by Oracle Support Services. // Check the additional diagnostic information in the trace file and // contact Oracle Support Services for recommendations // on setting this parameter. 27622, 00000, "Cell automation worker action interrupted" // *Document: NO // *Cause: Cell automation worker action was interrupted. // *Action: This is used internally; no action is required. 27623, 00000, "Cell automation SQL action failed" // *Cause: Cell automation manager or worker process failed to execute // SQL action through OCI recursive call. // *Action: Check the alert log and process trace file for additional // information. Contact Oracle Support Services if the errors // specified in the trace file cannot be corrected. 27624, 00000, "Smart I/O failed because the number of reconnects to the cell \"%s\" exceeded the maximum allowed \"%s\"." // *Cause: The number of reconnects to a cell exceeded the maximum allowed. // This problem indicates a possible network problem or a software problem // on the cell. // *Action: If the cellsrv is being restarted repeatedly, in a short interval, // check the system load. The problem may be corrected by rebooting // the cell. If the system is not overloaded, the repeated restarts // are likely due to software problem. Report the problem to Oracle // Support Services along with alert log and trace files. If the cellsrv // is not restarting, the problem may be in the IB network. Check the // network between the host and all the cells. 27625, 00000, "Exadata configuration failed." // *Cause: One or both of the files, cellinit.ora and cellip.ora, were either invalid or missing. // *Action: Check if the files, cellinit.ora and cellip.ora, are both present. // They can be found in the $OSSCONF directory. If both are present, // check if their contents are valid and correct. // If the files are invalid or missing, produce files with // valid information in the $OSSCONF directory. For information on // how to set up these files, see the Exadata Users Guide. 27626, 00000, "Exadata error: %s (%s)" // *Cause: The cause of this error is dependent on the context in which this error // is reported. // *Action: See the primary error reported with this error. / / 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 as 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 expiry; the expiry period // is unlimited. // *Action: Change the password or contact the DBA. / 28013, 00000, "the password has expired" // *Cause: The password of the proxy user expired. // // *Action: Connect directly as proxy user to change the password // or contact the DBA. / 28015, 00000, "Account unlocked, but the database is open for read-only access" // *Cause: The database or pluggable database was open for read-only access. // Although the account was successfully unlocked, this account // status change only affected the current database instance. // *Action: If this database is part of a Data Guard configuration, // perform the account unlock action on the primary database. // // 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 28031, 00000, "maximum of %s enabled roles exceeded" // *Cause: The user attempted to enable too many roles. // *Action: Enable fewer roles. 28032, 00000, "Your password has expired and the database is set to read-only" // *Cause: Your password expired and needs to be changed before // your login request can be processed. // Because the database is currently open in read-only mode, the // password change operation cannot be performed on this database. // *Action: Log in to the primary database to change your password, then // retry your login request at the standby database. 28033, 0000, "LDAP problem" // *Document: NO // *Cause: // *Action: 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 28038, 0000, "disallow O2LOGON" // *Cause: turn off O2LOGON // *Action: 28039, 0000, "cannot validate Kerberos service ticket" // *Cause: The Kerberos service ticket provided was invalid or expired // *Action: Provide a valid, unexpired service ticket. 28040, 0000, "No matching authentication protocol" // *Cause: No acceptible authentication protocol for both client and server // *Action: Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter // on both client and servers to values that matches the minimum // version supported in the system. 28041, 0000, "Authentication protocol internal error" // *Cause: Authentication protocol failed with an internal error // *Action: 28042, 0000, "Server authentication failed" // *Cause: Server failed to authenticate itself to the client // *Action: Confirm that the server is a valid database server. 28043, 000, "invalid bind credentials for DB-OID connection" // *Cause: The Database password stored in the wallet did not match // the one in OID . // *Action: Use DBCA to reset the database password so that it // is the same in database wallet and in OID. 28044, 000, "unsupported directory type" // *Cause: The database tried to work with a directory which is not OID. // *Action: Enterprise User Security works only with Oracle Internet Directory. // Update the ldap.ora file to reflect an appropriate OID. 28045, 000, "SSL authentication between database and OID failed" // *Cause: Server failed to authenticate itself to the Directory. // *Action: Make sure the sqlnet.ora used is pointing to the wallet // with the right certificate. 28046, 0000, "Password change for SYS disallowed" // *Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS // password changes. // *Action: Change setting of REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or NONE. 28047, 0000, "database is not a member of any enterprise domain in OID" // *Cause: An enterprise user login was attempted on a database that is // not a member of any enterprise domain in OID. // *Action: An administrator should put the database into an enterprise // domain in OID, and then the user should reconnect. 28048, 0000, "database is a member of multiple enterprise domains in OID" // *Cause: An enterprise user login was attempted on a database that is // a member of multiple enterprise domains in OID. // *Action: An administrator should put the database into only one // enterprise domain in OID, and then the user should reconnect. 28049, 00000, "the password has expired" // *Cause: The enterprise user's password has expired and the password // needs to be changed. // *Action: change the password in the directory or contact the directory // administrator. 28051, 00000, "the account is locked" // *Cause: The enterprise user has consecutively entered the wrong password // for maximum number of times specified in the realm's // password policy profile. // *Action: Contact the directory administrator. 28052, 00000, "the account is disabled" // *Cause: The enterprise user's account in the directory has been disabled. // *Action: Contact the directory administrator. 28053, 00000, "the account is inactive" // *Cause: The enterprise user's account in the directory is currently not // active. // *Action: Contact the directory administrator. 28054, 00000, "the password has expired. %s Grace logins are left" // *Cause: The enterprise user's password has expired. The user is // able to login because he has gracelogins left. // *Action: change the password in the directory or contact the directory // administrator. 28055, 00000, "the password will expire within %s days" // *Cause: The enterprise user's password is about to expire. // *Action: Change the password in the directory or contact the directory // administrator. 28056, 00000, "Writing audit records to Windows Event Log failed" // *Cause: Unable to write an audit entry to the Windows event log // used as the audit trail. // *Action: Check the error number for a possible operating system error. // If there is no error, contact Oracle Support Services. 28057, 00000, "name of the password file could not be constructed" // *Cause: Possibly environment variable ORACLE_SID was not set. // *Action: Set value for the ORACLE_SID environment variable. / / 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, "input value for %s is not valid" // *Cause: Input value for the argument is not valid // *Action: specify a valid argument value. 28105, 00000, "cannot create security relevant column policy in an object view" // *Cause: Security relevant column argument is not null in policy creation // for an object view // *Action: 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: An attempt was made to execute either DBMS_RLS.CREATE_POLICY_GROUP // or DBMS_RLS.DELETE_POLICY_GROUP using SYS_DEFAULT as the policy // group name. // *Action: Do not attempt to CREATE or DELETE the SYS_DEFAULT policy // group. This action is not permitted. 28123, 00000, "Driving context '%s,%s' contains invalid group '%s'" // *Cause: A previous call to DBMS_SESSION.SET_CONTEXT specified an invalid // policy group. // *Action: Ensure that a valid policy group is passed to // DBMS_SESSION.SET_CONTEXT when initializing a policy driving context. 28124, 00000, "Column %s in sec_relevant_cols cannot be of an object data type" // *Cause: A column specified in sec_relevant_cols was of an object data type. // *Action: Ensure that none of the columns specified in sec_relevant_cols // is of an object data type or XMLType. 28130, 00000, "Fine Grained Access Control at table level" // *Document: NO // *Cause: // *Action: 28131, 00000, "Fine Grained Access Control enforced" // *Document: NO // *Cause: // *Action: 28132, 00000, "The MERGE INTO syntax does not support the security policy." // *Cause: The MERGE INTO syntax did not support a security policy on the // destination table, because the policy's statement_types did // not include each of INSERT, UPDATE and DELETE. // *Action: If you do not have the privilege to modify the security policy, // then instead of MERGE INTO, use the INSERT, UPDATE and DELETE DML // statements on the table that has a security policy defined on it. // If you have the privilege to modify the security policy, then // redefine it in such a way that statement_types includes all of // the DML statement types (INSERT, UPDATE and DELETE). // 28133, 00000, "full table access is restricted by fine-grained security" // *Document: NO // *Cause: The command requires full table access but the user is not SYS // and does not have permission to by pass security policies. // *Action: Grant appropriate privileges, or change the policy function so // that it returns a NULL predicate under certain session // environments. / 28134, 00000, "object cannot have fine-grained access control policy" // *Cause: Only tables, views, or synonyms of tables or views // may have VPD policies // *Action: 28135, 00000, "VPD check option silent error event" // *Cause: // *Action: 28136, 00000, "Ignore check option error" // *Cause: // *Action: / 28137, 00000, "Invalid FGA audit Handler" // *Cause: An invalid audit handler was specified. // *Action: Specify a valid audit handler. / 28138, 00000, "Error in Policy Predicate" // *Cause: An invalid policy predicate was specified. // *Action:Please specify a valide policy Predicate for the FGA policy / 28139, 00000, "Maximum allowed Fine Grain Audit Policies Exceeded" // *Cause: A maximum of 256 policies can be enabled on an object // *Action: Drop or disable an existing policy before creating more / 28140, 00000, "Invalid column specified " // *Cause: Column name specified during policy creation is invalid // *Action: Please specify a valid column name. Object columns are not // supported / 28141, 00000, "error in creating audit index file" // *Cause: ORACLE was not able to create the file being used to hold // audit file names. // *Action: Examine the directory pointed to by the initialization // parameter "audit_file_dest." Make sure that all of the // following is true: // 1. The directory exists. // 2. The name indeed points to a directory and not a file. // 3. The directory is accessible and writable to the ORACLE user. / 28142, 00000, "error in accessing audit index file" // *Cause: ORACLE was not able to access the file being used to hold // audit file names. // *Action: Make sure the file exists in the directory pointed to by the // initialization parameter "audit_file_dest" and is readable // by the ORACLE user. / 28143, 00000, "Invalid argument passed to FGA ADD_POLICY procedure" // *Cause: Invalid input argument was specified for FGA ADD_POLICY procedure. // *Action: Specify correct type and number of arguments to FGA // ADD_POLICY procedure. / 28144, 00000, "Failed to execute fine-grained audit handler" // *Cause: An error was encountered while executing fine-grained audit handler. // *Action: Refer to the trace file for details. / / 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. / 28181, 00000, "proxy '%s' failed to enable one or more of the specified initial roles for client '%s'" // *Cause: Attempt to enable specified initial roles after logon resulted in // failure. // *Action: Check that the initial roles are valid, granted to client, and // not password protected. / 28182, 00000, "cannot acquire Kerberos service ticket for client" // *Cause: An attempt to use a Kerberos forwardable ticket granting ticket // to obtain a Kerberos service ticket failed. // *Action: Check that the Kerberos forwardable ticket granting ticket // belongs to the client, is valid, and that the key distribution // center is available. / 28183, 00000, "proper authentication not provided by proxy" // *Cause: A client user must be authenticated but // no authentication credentials were provided by the proxy user. // *Action: Provide some form of authentication credentials. / 28184, 00000, "global user cannot have proxy permissions managed in the directory" // *Cause: The client name specified was a global user. // *Action: Use ALTER USER to change the type of user (from IDENTIFIED // GLOBALLY to something else, such as IDENTIFIED BY password // or IDENTIFIED EXTERNALLY). / / 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 // // / // // / / 28221-28230 RESERVED FOR PASSWORD ENHANCEMENT / // 28221, 00000, "REPLACE not specified" // *Cause: User is changing password but password verification function is // turned on and the original password is not specified and the // user does not have the alter user system privilege. // *Action: Supply the original password. // // / / 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 an 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" // *Document: NO // *Cause: N/A // *Action: Debugging event for KZCTX layer. / 28267, 0000, "Invalid NameSpace Value" // *Cause: Context NameSpace conflicts with reserved key words or // a secure Namespace is not allowed for this // type of Application Context. // *Action: Use a valid namespace. // / 28268, 0000, "Exceeded the maximum allowed size for Context information in a session" // *Cause: The maximum size specified by the _session_context_size // init.ora parameter was exceeded. // *Action: Please change the value for _session_context_size in the // init.ora file. // / 28269, 0000, "Event to enable overwrite of client_identifier when client_info is set" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to propagate client_info session // context attribute to client_identifier. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. // / / 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 ldap_directory_access init parameter." // *Cause: ldap_directory_access parameter is not specified corrrectly. // // *Action: Make sure spfile.ora has ldap_directory_access set correctly. // Possible correct values are PASSWORD, SSL and NONE. / 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. / 28281, 0000, "Global application context is not updated on one or more Oracle RAC instances" // *Cause: While updating global application context across Oracle RAC instances, // the background process errored out or the timeout expired due to // some failure. // *Action: Ensure every instance in Oracle RAC is operational and retry the operation. / / 28290 - 28300 RESERVED FOR THE Kerberos Enterprise User Security / 28290, 00000, "Multiple entries found for the same Kerberos Principal Name" // *Cause: Multiple user entries has been configured with the same krbPrincipalName // *Action: Modify enterprise user's entry to assign its Kerberos principal name // Make sure the user entries in LDAP are provisioned correctly. / 28291, 00000, "No Kerberos Principal Value found." // *Cause: Oracle server fails to get value of krbPrincipalName attribute // *Action: Make sure user entries are correctly provisioned with correct // Kerberos principal value / 28292, 00000, "No Domain Policy registered for Kerberos based authentication" // *Cause: The enterprise domain entry is not configured for Kerberos based // global authentication. // *Action: Modify orclDBAuthType of the database server's enterprise // domain entry and assign it "ALL" or "KRB5" / 28293, 00000, "No matched Kerberos Principal found in any user entry" // *Cause: Oracle server fails to find the principal in the user search base // *Action: Make sure the user search base is correct. // Use ESM to configure the enterprise user its Kerberos principal name / / / 28300 - 28329 RESERVED FOR THE ENTERPRISE USER SECURITY / 28300, 00000, "No permission to read user entry in LDAP directory service." // *Cause: ORACLE server does not have read permission on user entries. // *Action: Make sure ORACLE server is using right credentials to connect // to LDAP directory services. // Make sure permissions for LDAP user entries are configured correctly. / 28301, 00000, "Domain Policy hasn't been registered for SSL authentication." // *Cause: An attempt was made to authenticate with SSL, but the database // enterprise domain was not configured for SSL authentication. // *Action: Modify orclDBAuthType of the server's enterprise domain entry // and assign it "ALL" or "SSL". / 28302, 00000, "User does not exist in the LDAP directory service." // *Cause: An attempt was made to authenticate with SSL using the user's // certificate, but there was no user entry in the LDAP server that // matched the user's Distinguished Name. // *Action: Add an user entry whose DN matches the user's PKI DN in // the LDAP directory. 28303, 00000, "Distinguished name for user exceeds maximum supported length" // *Cause: The user's distinguished name (DN) exceeded the maximum supported // length. // *Action: Shorten the user's distinguished name (DN) and retry. / / / 28330-28499 RESERVED FOR TRANSPARENT DATA ENCRYPTION / 28330, 0000, "encryption is not allowed for this data type" // *Cause: Data type was not supported for column encryption. // // *Action: // / 28331, 0000, "encrypted column size too long for its data type" // *Cause: column was encrypted and // for VARCHAR2, the length specified was > 3932; // for CHAR, the length specified was > 1932; // for NVARCHAR2, the length specified was > 1966; // for NCHAR, the length specified was > 966; // *Action: Reduce the column size. // / 28332, 0000, "cannot have more than one password for the encryption key" // *Cause: More than one password was specified in the user command. // // *Action: // / 28333, 0000, "column is not encrypted" // *Cause: An attempt was made to rekey or decrypt an unencrypted column. // // *Action: // / 28334, 0000, "column is already encrypted" // *Cause: An attempt was made to encrypt an encrypted column. // // *Action: // / 28335, 0000, "referenced or referencing FK constraint column cannot be encrypted" // *Cause: encrypted columns were involved in the referential constraint // // *Action: // / 28336, 0000, "cannot encrypt SYS owned objects" // *Cause: An attempt was made to encrypt columns in a table owned by SYS. // // *Action: // / 28337, 0000, "the specified index may not be defined on an encrypted column" // *Cause: Index column was either a functional, domain, or join index. // // *Action: // / 28338, 0000, "Column(s) cannot be both indexed and encrypted with salt" // *Cause: An attempt was made to encrypt index column with salt or // an attempt was made to create an index on encrypted column with salt. // // *Action: Alter the table and specify column encrypting without salt. // / 28339, 0000, "missing or invalid encryption algorithm" // *Cause: Encryption algorithm was missing or invalid in the user command. // // *Action: Must specify a valid algorithm. // / 28340, 0000, "a different encryption algorithm has been chosen for the table" // *Cause: Existing encrypted columns were associated with a different algorithm. // // *Action: No need to specify an algorithm, or specify the same one for the // existing encrypted columns. / 28341, 0000, "cannot encrypt constraint column(s) with salt" // *Cause: An attempt was made to encrypt constraint columns with salt. // // *Action: Encrypt the constraint columns without salt. // / 28342, 0000, "integrity check fails on column key" // *Cause: Encryption metadata may have been improperly altered. // // *Action: // / 28343, 0000, "fails to encrypt data" // *Cause: data or encryption metadata may have been improperly altered or // the security module may not have been properly setup // // *Action: // 28344, 0000, "fails to decrypt data" // *Cause: data or encryption metadata may have been improperly altered or // the security module may not have been properly setup // // *Action: // / 28345, 00000, "cannot downgrade because there exists encrypted column" // *Cause: An attempt was made to downgrade when there was an encrypted // column in the system. // *Action: Decrypt these columns before attempting to downgrade. / 28346, 00000, "an encrypted column cannot serve as a partitioning column" // *Cause: An attempt was made to encrypt a partitioning key column or // create partitioning index with encrypted columns. // *Action: The column must be decrypted. / 28347, 00000, "encryption properties mismatch" // *Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | // SUBPARTITION command, but encryption properties were mismatched. // *Action: Make sure encrytion algorithms and columns keys are identical. // The corresponding columns must be encrypted on both tables with // the same salt and non-salt flavor. / 28348, 0000, "index defined on the specified column cannot be encrypted" // *Cause: An attempt was made to encrypt a column which is in a functional // index, domain index, or join index. // // *Action: drop the index // / 28349, 0000, "cannot encrypt the specified column recorded in the materialized view log" // *Cause: An attempt was made to encrypt a column which is already recorded // in the materialized view log. // // *Action: drop the materialized view log // / 28350, 0000, "cannot encrypt the specified column recorded in CDC synchronized change table" // *Cause: An attempt was made to encrypt a column which is already recorded // in CDC synchronized change table. // *Action: drop the synchronized change table / 28351, 0000, "cannot encrypt the column of a cluster key" // *Cause: An attempt was made to encrypt a column of the cluster key. // A column of the cluster key in a clustered table cannot be // encrypted. // *Action: None / 28353, 0000, "failed to open wallet" // *Cause: The database was unable to open the security module wallet due // to an incorrect wallet path or password It is also possible // that a wallet has not been created. Type mkwallet from command // line for instructions. // *Action: Execute the command again using the correct wallet password or // verfying a wallet exists in the specified directory. If // necessary, create a new wallet and initialize it. / 28354, 0000, "Encryption wallet, auto login wallet, or HSM is already open" // *Cause: Encryption wallet, auto login wallet, or HSM was already opened. // *Action: None. // / 28355, 0000, "failed to initialize security module" // *Cause: // // *Action: // / 28356, 0000, "invalid open wallet syntax" // *Cause: The command to open the wallet contained improper spelling // or syntax. // *Action: If attempting to open the wallet, verify the spelling and // syntax and execute the command again. / 28357, 0000, "password required to open the wallet" // *Cause: A password was not provided when executing the open wallet // command. // *Action: Retry the command with a valid password. / 28358, 0000, "improper set key syntax" // *Cause: The command to set the master key contained improper spelling // or syntax. // *Action: If attempting to set the master key for Transparent Database // Encryption, verify the spelling and syntax and execute // the command again. / 28359, 0000, "invalid certificate identifier" // *Cause: The certificate specified did not exist in the wallet. // *Action: Query the V$WALLET fixed view to find the proper certificate // identifier for certificate to be used. / 28360, 0000, "security module internal error" // *Cause: // // *Action: // / 28361, 0000, "master key not yet set" // *Cause: The master key for the instance was not set. // *Action: Execute the ALTER SYSTEM SET KEY command to set a master key // for the database instance. / 28362, 0000, "master key not found" // *Cause: The required master key required could not be located. This may // be casued by the use of an invalid or incorrect wallet. // *Action: Check wallet location parameters to see if they specify the // correct wallet. Also, verify that an SSO wallet is not being used // when an encrypted wallet is intended. 28363, 0000, "buffer provided not large enough for output" // *Cause: A provided output buffer is too small to contain the output. // *Action: Check the size of the output buffer to make sure it is initialized // to the proper size. / 28364, 0000, "invalid wallet operation" // *Cause: The command to operate the wallet contained improper spelling // or syntax. // *Action: Verify the spelling and syntax and execute the command again. / 28365, 0000, "wallet is not open" // *Cause: The security module wallet has not been opened. // *Action: Open the wallet. / 28366, 0000, "invalid database encryption operation" // *Cause: The command for database encryption contained improper spelling // or syntax. // *Action: Verify the spelling and syntax and execute the command again. / 28367, 0000, "wallet does not exist" // *Cause: The Oracle wallet has not been created or the wallet location // parameters in sqlnet.ora specifies an invalid wallet path. // *Action: Verify that the WALLET_LOCATION or the ENCRYPTION_WALLET_LOCATION // parameter is correct and that a valid wallet exists in the path // specified. / 28368, 0000, "cannot auto-create wallet" // *Cause: The database failed to auto create an Oracle wallet. The Oracle // process may not have proper file permissions or a wallet may // already exist. // *Action: Confirm that proper directory permissions are granted to the Oracle // user and that neither an encrypted or obfuscated wallet exists in // the specified wallet location and try again. / 28369, 0000, "cannot add files to encryption-ready tablespace when offline" // *Cause: You attempted to add files to an encryption-ready tablespace when // all the files in the tablespace were offline. // *Action: Bring the tablespace online and try again // / 28370, 0000, "ENCRYPT storage option not allowed" // *Cause: You attempted to specify the ENCRYPT storage // option. This option may only be specified during // CREATE TABLESPACE. // *Action: Remove this option and retry the statement. // / 28371, 0000, "ENCRYPTION clause and/or ENCRYPT storage option not allowed" // *Cause: You attempted to specify the ENCRYPTION clause or // ENCRYPT storage option for creating TEMP or UNDO tablespaces. // *Action: Remove these options and retry the statement. // / 28372, 0000, "missing ENCRYPT storage option for encrypted tablespace" // *Cause: You attempted to specify ENCRYPTION property for CREATE TABLESPACE // without specifying ENCRYPT storage option to encrypt the // tablepsace. // *Action: Add ENCRYPT storage option and retry the statement. // / 28373, 0000, "missing ENCRYPTION clause for encrypted tablespace" // *Cause: You attempted to specify storage option ENCRYPT in CREATE TABLESPACE // without specifying ENCRYPTION property to encrypt the // tablepsace. // *Action: Add ENCRYPTION clause and retry the statement. // // / 28374, 0000, "typed master key not found in wallet" // *Cause: You attempted to access encrypted tablespace or redo logs with // a typed master key not existing in the wallet. // *Action: Copy the correct Oracle Wallet from the instance where the tablespace // was created. // / 28375, 0000, "cannot perform cross-endianism conversion on encrypted tablespace" // *Cause: You attempted to perform cross-endianism conversion on encrypted // tablespace. // *Action: Cross-endianism conversion on encrypted tablespace is not supported. // / 28376, 0000, "cannot find PKCS11 library" // *Cause: The HSM vendor's library cannot be found. // *Action: Place the HSM vendor's library in the following directory structure: // For Unix like system: // /opt/oracle/extapi/[32,64]/hsm/{VENDOR}/{VERSION}/lib. // For Windows systems: // %SYSTEM_DRIVE%\oracle\extapi\[32,64]\hsm\{VENDOR}\{VERSION}\lib. // [32, 64] - refers to 32bit or 64bit binary. // {VENDOR} - The name of the vendor supplying the library. // {VERSION} - Version of the library, perferably in num#.num#.num# for// mat. / 28377, 0000, "No need to migrate from wallet to HSM" // *Cause: There are either no encrypted columns or all column keys are already // encrypted with the HSM master key. // *Action: No action required. / 28378, 0000, "Wallet not open after setting the Master Key" // *Cause: The Master Key has been set or reset. However, wallet could not be // reopened successfully. // *Action: Reopen the wallet. / 28379, 0000, "a different integrity algorithm has been chosen for the table" // *Cause: Encrypted columns were associated with a different algorithm. // // *Action: You do not need to specify an algorithm, or specify the same // one for the existing encrypted columns. / 28380, 00000, "Event to force all newly created tablespaces to be encrypted for testing" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to force all newly created // tablespaces to be encrypted tablespaces. It is an easy way to // convert an existing test to run with tablespace encryption. It is // used for testing only and not for security. Often run with event // 28381. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / 28381, 00000, "Event to bypass wallet setup for tablespace encryption" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to bypass wallet setup for // tablespace encryption. It uses a dummy encryption master key to // simulate encryption or decryption by the wallet, and has no wallet // dependency. It is an easy way to convert an existing test to run // with tablespace encryption. It is used for testing only and not for // security. Often run with event 28380. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / 28382, 00000, "Global wallet operation in RAC failed" // *Cause: Wallet operation in RAC failed. // *Action: Check V$WALLET_ENCRYPTION table to verify if the wallet operation // succeeded on any instance. Retry the operation. / 28383, 00000, "cannot do a PKI certificate-based Master Key migration" // *Cause: A PKI certificate-based Master Key migration was not allowed. // *Action: Execute a symmetric Master Key migration. / 28384, 0000, "cannot perform Tablespace Encryption" // *Cause: Tablespace Encryption was attempted when PKI certificate-based // Master Key was in use. // *Action: Perform a symmetric Master Key Rekey. / 28385, 0000, "cannot perform a PKI certificate-based migration" // *Cause: A PKI certificate-based migration to HSM was attempted. // *Action: Perform a symmetric Master Key migration. / 28386, 0000, "cannot perform a PKI certificate-based Master Key Rekey" // *Cause: A PKI certificate-based Master Key Rekey was attempted when // Tablespace Encryption or HSM was in use. // *Action: Perform a symmetric Master Key Rekey or disable Tablespace // Encryption for all tablespaces. / 28387, 00000, "Could not acquire an enqueue for wallet operation in Oracle RAC" // *Cause: Enqueue to block TDE operations in Oracle RAC database could // not be obtained. // *Action: Retry the wallet operation. / 28388, 00000, "database is not open in read/write mode" // *Cause: Database was not open in read/write mode and could not perform // these wallet operations. // *Action: Open the database in read/write mode and retry this command. / 28389, 00000, "cannot close auto login wallet" // *Cause: Auto login wallet could not be closed because it was opened with // another wallet or HSM requiring a password. // *Action: Close the wallet or HSM with a password. / 28390, 00000, "auto login wallet not open but encryption wallet may be open" // *Cause: Auto login wallet was not open. But, the encryption wallet may // still be open and subsequent TDE operations might succeed. // *Action: If auto login wallet is closed but TDE operations succeed, // check the status of the encryption wallet and close that if // required. / 28391, 00000, "cannot close wallet or HSM, password mismatch" // *Cause: Password provided did not match the password of the open // wallet or HSM. // *Action: Provide the correct password for wallet or HSM to // close the wallet or HSM. / 28392, 0000, "invalid close wallet syntax" // *Cause: The command to close the wallet contained improper spelling // or syntax. // *Action: If attempting to close the wallet, verify the spelling and // syntax and execute the command again. / 28393, 0000, "password required to close the wallet" // *Cause: A password was not provided when executing the close wallet // command. // *Action: Retry the command with a valid password. / 28394, 0000, "decryption of data of length %s failed" // *Cause: Decryption of data failed. Error may be due to plain text data in // an external file being submitted for decryption, data encrypted // with a different key or a utility being submitted for decryption, // or TDE encrypted data in data files being corrupted. // *Action: Verify that the correct external file is being specified or contact // Oracle Support Services. / 28395, 0000, "could not write the new master key to the wallet" // *Cause: An attempt was made to write the new master key to the wallet. The // wallet or the parent directory may not have the proper file // permissions to write the master key in the wallet. // *Action: Check the password-based wallet, auto login wallet, the parent // directory permissions and disk space availability on the file // system. Make sure that the Oracle processes have read/write // permissions on the password-based and auto login wallets. Retry // the command. / 28396, 0000, "rekey of enc$ dictionary table failed" // *Cause: One or more master keys required for the rekey operation could // not be found in the wallet. Either incorrect master key identifiers // were inserted into the enc$ dictionary table or the wallet // containing the referenced master keys were improperly modified // or deleted. // *Action: Restore the most recent copy of the wallet and try again. / 28397, 0000, "cannot online file %s since it has a passphrase-wrapped key" // *Cause: The encrypted tablespace file was rewrapped using passphrase // through the DBMS_TTS.PASSPHRASE_REWRAP_KEY procedure. Therefore it // cannot be part of the database until it is converted by RMAN. // // *Action: Do not attempt to online files with passphrase-wrapped keys. / 28398, 0000, "cannot rewrap encryption key for this file" // *Cause: Cannot rewrap encryption key for this file because it was not // from an encrypted tablespace, or it had already been rewrapped. // // *Action: Verify that the file is a copy of a file from an encrypted // tablespace. / 28399, 00000, "Event to disable automatic TDE wallet management in RAC" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to disable the automatic // management of wallet in RAC. / 28400, 00000, "Event to enable TDE tracing" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to obtain trace information // for Transparent Data Encryption. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. 28401, 00000, "Event to disable delay after three failed login attempts" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to disable the login delay // which will otherwise take place after three failed login attempts. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. 28403, 00000, "file %s cannot be modified because it is an online data file" // *Cause: An attempt was made to modify an online data file when the file was // not expected to be part of the database. // *Action: Check the status of the file and its tablespace and make sure it // is offline or is a copy of a data file 28406, 00000, "Event to keep connection made by database to OID open when enterprise user logs into database" // *Document: NO // *Cause: N/A // *Action: Set this event in your environment to keep connection made by // database to OID open when enterprise user logs into database. // Default behaviour is to close the connection once enterprise user // logs into database. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. 28407, 0000, "Hardware Security Module error detected" // *Cause: Hardware Security Module (HSM) connection may have been lost // or another internal HSM error was reached. // *Action: Check the trace files for error details and try the following: // 1) Retry the command. If the error repeats, go to step 2. // 2) Verify that the HSM is configured correctly and connected. // Retry the command. If the error repeats, go to step 3. // 3) Ask your Security Officer to close and open the security // module. Retry the command. If the error repeats, go to step 4. // 4) Bounce the database if possible. Retry the command. // If the error repeats, contact Oracle Support Services or your // HSM vendor's support. / 28408, 00000, "encryption using passphrase failed" // *Cause: Encryption with the passphrase failed which was likely due to an invalid // or missing passphrase or due to an internal error. // *Action: Verify that the passphrase is provided and try the operation again. If // the problem persists contact Oracle Support Services. / 28409, 00000, "decryption using passphrase failed" // *Cause: Decryption with the passphrase failed which was likely due to an invalid // or missing passphrase or due to an internal error. // *Action: Verify that the passphrase is provided and try the operation again. If // the problem persists contact Oracle Support Services. / / / 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 Heterogenous Services initialization parameter // HS_ROWID_CACHE_SIZE. // 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 and agent documentation to // determine acceptable values // 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 was used internally within Oracle Database // 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 Oracle // Database 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. // 28543, 00000, "Error initializing apply connection to non-Oracle system" // *Cause: Attempt to initialize connection to non-Oracle for heterogeneous // replication failed. // *Action: Check if the listener used to connect to the gateway is up and is // correctly configured. Make sure that the database link used has // been configured correctly and, if a tnsnames alias has been used // in the database link definition, make sure that the configuration // of the entry in tnsnames.ora has been done correctly. // 28544, 0000, "connect to agent failed, probable Net8 administration error" // *Cause: Net8 reported a failure to make a RSLV connection or // a protocol mode error when the Oracle server attempted // to establish communication with a Heterogeneous Services // agent or an external procedure agent. This usually is due // to an administration error in setting up Net8 service definitions // in TNSNAMES.ORA or LISTENER.ORA: A basic network connection // is opened, but it connects to a program which does not use // the appropriate protocol. This often is a sign that the // connection goes to the wrong program. // *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 // service name or SID. // -- Check LISTENER.ORA on the agent's host machine to assure that // the service name or SID refers to the correct agent // executable in its (PROGRAM=...) clause. // -- Confirm in TNSNAMES.ORA or the equivalent service definition // that sevice 'extproc_connection_data' does NOT contain // (HS=), or that the service definition used by a // Heterogeneous Services database link DOES contain (HS=). // 28545, 0000, "error diagnosed by Net8 when connecting to an agent" // *Cause: An attempt to call an external procedure or to issue SQL // to a non-Oracle system on a Heterogeneous Services database link // failed at connection initialization. The error diagnosed // by Net8 NCR software is reported separately. // *Action: Refer to the Net8 NCRO error message. If this isn't clear, // check connection administrative setup in tnsnames.ora // and listener.ora for the service associated with the // Heterogeneous Services database link being used, or with // 'extproc_connection_data' for an external procedure call. // 28546, 0000, "connection initialization failed, probable Net8 admin error" // *Cause: A failure occurred during initialization of a network connection // from the Oracle server to a second process: The connection // was completed but a disconnect occurred while trying to // perform protocol-specific initialization, usually due to // use of different network protocols by opposite sides // of the connection. This usually is caused by incorrect // Net8 administrative setup for database links or external // procedure calls. The most frequent specific causes are: // -- Database link setup for an Oracle-to-Oracle connection // instead connects to a Heterogeneous Services agent // or an external procedure agent. // -- Database link setup for a Heterogeneous Services connection // instead connects directly to an Oracle server. // -- The extproc_connection_data definition in tnsnames.ora // connects to an Oracle instance instead of an external // procedure agent. // -- Connect data for a Heterogeneous Services database link, // usually defined in tnsnames.ora, does not specify (HS=). // -- Connect data for an Oracle-to-Oracle database link, // usually defined in tnsnames.ora, specifies (HS=). // *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 // service name or SID. // -- Check LISTENER.ORA on the connection end point's host machine // to assure that this service name or SID connects to the // correct program. // -- Confirm in TNSNAMES.ORA or the equivalent service definition // that service 'extproc_connection_data' does NOT contain // (HS=), or that the service definition used by a // Heterogeneous Services database link DOES contain (HS=). // 28547, 0000, "connection to server failed, probable Oracle Net admin error" // *Cause: A failure occurred during initialization of a network connection // from a client process to the Oracle server. The connection // was completed but a disconnect occurred while trying to // perform protocol-specific initialization, usually due to // use of different network protocols by opposite sides // of the connection. This usually is caused by incorrect // Oracle Net administrative setup for database links or external // procedure calls. The most frequent specific causes are: // -- The connection uses a connect string which refers // to a Heterogeneous Services agent instead of // an Oracle server. // -- The connection uses a connect string which includes // an (HS=) specification. // -- Hitting Ctrl+C before connection initialization is // complete. // -- Using DRCP on Windows with SQLNET.AUTHENTICATION_SERVICES // set to NTS. // -- Connection timeout due to SQLNET.INBOUND_CONNECT_TIMEOUT // parameter when all shared servers are busy in // shared server configuration. // *Action: Check Oracle Net administration in the following ways: // -- When using TNSNAMES.ORA or an Oracle Names server, make sure // that the client connection to the Oracle server uses // the correct service name or SID. // -- Check LISTENER.ORA on the connection end point's host machine // to assure that this service name or SID refers // to the correct server. // -- Confirm in TNSNAMES.ORA or the equivalent service definition // that the connect string does not contain (HS=). // -- Set SQLNET.AUTHENTICATION_SERVICES to NONE when using DRCP // on Windows. // 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. // 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. 28562, 00000, "Heterogeneous Services data truncation error" // *Cause: A select operation was attempted with an insufficient data buffer // to satisfy the request. // *Action: Contact your DBA to verify whether your gateway initialization // parameter HS_KEEP_REMOTE_COLUMN_SIZE = TRUE. If the parameter is // set to TRUE, change it to FALSE and try the operation again. // If the problem persists, contact Oracle Support Services. // If the problem is due to size discrepancies between Oracle and // the non-Oracle system, it may not be possible to convert the value. / / 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. // 28583, 00000, "remote references are not permitted during agent callbacks" // *Cause: A Heterogeous Services agent issued a callback to the Oracle server // which attemted to to access a remote system. This is not supported. // *Action: Make sure that SQL code issued by Heterogeneous Services agents // does not reference a database link. // 28584, 00000, "heterogeneous apply internal error" // *Cause: The apply slave process encountered an error while trying to // apply changes through a gateway to a non-Oracle system. // *Action: Make sure that the apply database link is correctly configured and // that the gateway listener and the non-Oracle system are correctly // set up and are up and running. If everything is configured correctly // and the problem still occurs, contact Oracle customer support. // // 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. // 28595, 00000, "Extproc agent : Invalid DLL Path" // *Cause: The path of DLL supplied for the extproc execution is invalid. // *Action: Check if the DLL path is set properly using the EXTPROC_DLLS // environment variable. // // 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 // 28606, 00000, "block too fragmented to build bitmap index (%s,%s)" // *Cause: The block(s) exceed the maximum number of rows expected when // creating a bitmap index. This is probably // due to maximum slot allowed set too low. // The values in the message are: // (slot number found, maximum slot allowed) // *Action: alter system flush shared_pool; update tab$ set spare1 = 8192 // where obj# = (select obj# from obj$ where NAME= AND // owner# = ; commit; 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 // NLS_DO_NOT_TRANSLATE [28657,28657] 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 . 28674, 00000, "cannot reference transient index-organized table" // *Cause: An attempt was made to directly access a transient table created // created on behalf of a index-organized table partition maintenance // operation. // *Action: Issue the statement against the associated permanent // index-organized table. / $Header: security_src/mesg/nze1us.msg /main/21 2009/03/10 22:01:18 tnallath Exp $ / $Header: security_src/mesg/nze1us.msg /main/21 2009/03/10 22:01:18 tnallath 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) / bhmathur 03/02/05 - Bug 2220658 Fix / rchahal 11/23/04 - changes suggested by errors_us / rchahal 10/11/04 - pkcs11 enhancement messages / skalyana 08/22/03 - Error message changes / skalyana 05/28/03 - Errors to be documented / rchahal 08/14/03 - crl error messages / skalyana 03/07/03 - Add messages for FIPS errors / skalyana 12/06/02 - Ad SSL Plus 4.2 error messages / supriya 10/30/01 - Fix for bug # 1691606 / supriya 10/08/01 - Fix for bug # 1691606 / 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" // *Cause: An Oracle Security Server error of an unspecified type occurred. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28751, 00000, "memory allocation failure" // *Cause: The allocation of memory failed due to insufficient system memory. // *Action: Terminate other processes to free up memory or add memory to the // system. / 28752, 00000, "data source initialization failure" // *Cause: A data source failed to initialize. Frequently, this error is caused // by insufficient system resources. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28753, 00000, "failure to terminate use of data source" // *Cause: The system failed to terminate its use of a data source. This error may // have been caused by memory or disk corruption, among other things. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28754, 00000, "object storage failure" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28755, 00000, "object retrieval failure" // *Cause: The system failed to retrieve information from a file or a // database. // *Action: Check if the data source exists, or check to ensure that the correct // information exists. / 28756, 00000, "callback failure to allocate memory" // *Cause: A function supplied by the caller failed to allocate memory. This error could // have been caused by system memory exhaustion. // *Action: Terminate other processes to free up memory or add memory to the system. / 28757, 00000, "system attempt to allocate 0 bytes of memory" // *Cause: The system attempted to allocate 0 bytes of memory because there was no // available memory left to allocate. This error could have been caused by insufficient system // memory. // *Action: Terminate other processes to free up memory or add memory to the system. / 28758, 00000, "memory release failure" // *Cause: The release of a memory fragment failed. This may be due to // memory corruption either within the application or in the // Oracle Security Server library. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28759, 00000, "failure to open file" // *Cause: The system could not open the specified file. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28760, 00000, "list creation failure" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28761, 00000, "element creation failure" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28762, 00000, "failure to add element" // *Cause: Error not user-visible. // *Document: NO // *Action: / 28763, 00000, "Invalid parameter type found in configuration file." // *Cause: A parameter in the sqlnet.ora file may have been specified incorrectly. // *Action: Check the sqlnet.ora file for this parameter value. / 28764, 00000, "failure to retrieve a configuration parameter" // *Cause: The system failed to retrieve a configuration parameter from the sqlnet.ora file. // This error may have occurred because a necessary configuration parameter was // not specified in the sqlnet.ora file. // *Action: Supply the needed configuration parameter in the sqlnet.ora file. / 28765, 00000, "Data method list does not exist." // *Cause: Error not user-visible. // *Action: // *Document: NO / 28766, 00000, "failure to terminate use of data source" // *Cause: The system failed to terminate its use of a data source. This error may // have been caused by memory or disk corruption, or a system error. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28767, 00000, "invalid version number" // *Cause: Version number of the wallet was incorrect. A corrupt wallet or // an incompatible wallet was provided. // *Action: Ensure that proper wallet is being used. / 28768, 00000, "bad magic number" // *Cause: An invalid magic number was specified in a data file. This could have been // caused by a corrupted disk or by some other process overwriting the file. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28769, 00000, "Specified method does not exist." // *Cause: The data access method that was 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 is 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 is not yet initialized." // *Cause: The caller attempted to use a data source which had not yet been // initialized. // *Action: This is a programming error. The application must always initialize // the data source before it can be used. / 28772, 00000, "invalid file ID" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28773, 00000, "failure to write magic and version numbers" // *Cause: Both the magic and version numbers failed to write. This usually // occurs because of insufficient disk space. // *Action: Delete unnecessary files to free up disk space or add disk space // to the system. / 28774, 00000, "file cannot write to disk" // *Cause: The output of a file failed. This error usually occurs because of // insufficient disk space. // *Action: Delete unnecessary files to free up disk space or add disk space // to the system. / 28775, 00000, "file cannot close" // *Cause: Failed to close a file which is used by a data access method. // This error usually indicates memory corruption or a system error. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28776, 00000, "Output buffer supplied is too small." // *Cause: The data returned by a function was too large for the // supplied buffer. // *Action: Call the routine again with a larger buffer. / 28777,00000, "binding creation failure" // *Cause: Failed to create a binding for use in the parsing of a parameter // value. This error can be caused by the parameter value // being in an incorrect format, such as a right parenthesis was not // supplied where expected, or due to insufficient 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 adding more memory. / 28778, 00000, "Configuration parameter is not specified in the proper format." // *Cause: The configuration parameter was not 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 method for data access in the parameter. Consult the // Oracle Security Server documentation for the supported data access // methods for this data type. / 28780, 00000, "invalid data access method specified by the parameter" // *Cause: The data access method specified by the parameter value is not // supported. // *Action: Specify a supported data access method. Consult the Oracle Security Server // documentation for the supported data access methods for this data // data type. / 28781, 00000, "No data for the access method is specified in the 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 is not allocated" // *Cause: No memory was allocated for a data source. // *Action: Ensure that the application calls in the data source initialization // function. / 28783, 00000, "invalid parameter" // *Cause: There was no match for the parameter name that was used in the // configuration file. // *Action: Check your sqlnet.ora file for the correct parameter name. / 28784, 00000, "file name translation failure" // *Cause: The translation of a file name from Oracle format to native format has // failed. // *Action: Specify a correct file name. Consult your Oracle documentation for the // correct file name format. / 28785, 00000, "parameter does not exist" // *Cause: A necessary configuration parameter was not found in the parameter file. // *Action: Supply the required parameter. / 28786, 00000, "decryption of encrypted private key failure" // *Cause: An incorrect password was used to decrypt an encrypted private key. // *Action: Enter the correct password. / 28787, 00000, "private key encryption failure" // *Cause: This may have been caused by an error in the mkwallet parameter of the // sqlnet.ora file. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28788, 00000, "user provided invalid information, or an unknown error" // *Cause: User may have responded to a prompt with unexpected input, or an // unknown error occurred. // *Action: Enter correct input, or enable tracing to check the trace file for // errors. / 28789, 00000, "name type not found" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28790, 00000, "NLS string open failure" // *Cause: The opening of a string for use by the NLS subsystem failed. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28791, 00000, "certificate verification failure" // *Cause: Verification of the certificate, which the user supplied, failed. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28792, 00000, "PL/SQL operation failure" // *Cause: A PL/SQL operation attempted by the Oracle Security Server failed. // *Action: This is an internal error. Enable tracing and try the operation // again. Contact Oracle customer support for assistance. // *Document: NO / 28793, 00000, "variable bind failure" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28794, 00000, "data type attribute did not initialize" // *Cause: The initialization of the attribute data type failed. This error may be // due to insufficient system resources. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28795, 00000, "data type attribute did not terminate" // *Cause: The termination of the use of the attribute data type subsystem // failed. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28796, 00000, "access method is not supported" // *Cause: The method specified to access data is not supported. // *Action: Use a supported access method. Consult your Oracle documentation to determine // which access methods are supported. / 28797, 00000, "invalid key data type" // *Cause: The type specified for a key is not supported. // *Action: Correct the key type. Consult your Oracle documentation to determine which // key types are supported. / 28798, 00000, "Number of sub-keys application passes to bind does not match that in the 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 Oracle customer // support. // *Document: NO / 28799, 00000, "failure to allocate shared memory" // *Cause: The allocation of shared memory for use in operations involving // the shared server failed. This error was probably due to // insufficient memory heap supplied by the Oracle server. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. // *Document: NO / 28800, 00000, "data source failed to open" // *Cause: A data source (a file or a database) failed to open. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28801, 00000, "invalid object type" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28802, 00000, "invalid mode or data source in configuration file" // *Cause: An invalid mode or data source has been specified in the // configuration file (sqlnet.ora). // *Action: Check the method parameter in the sqlnet.ora file. // If the parameter value is correct, then enable tracing to // determine the exact error. / 28803, 00000, "I/O operation failure" // *Cause: The system or application failed to access a data source // (file or database). // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28804, 00000, "Data source cannot close." // *Cause: The data source, which could be either a file or a database), // failed to close. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28805, 00000, "Cannot retrieve information from the data source." // *Cause: The system or application failed to retrieve information from // the data source (file or database). // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28806, 00000, "Cannot write to the data source." // *Cause: The system or application failed to write to the data source // (file or database). // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28807, 00000, "Cannot update the data source." // *Cause: The system or application failed to update the data source (file // or database). // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28808, 00000, "Cannot retrieve method information from the configuration file." // *Cause: The system or application failed to retrieve method // information from the sqlnet.ora configuration file. // *Action: Check the method configuration parameters in the sqlnet.ora file. // If the method configuration parameters are correct, then enable // tracing to determine the exact error. / 28809, 00000, "Cannot delete information from the data source." // *Cause: The system or application failed to delete information from the data // source (file or database). // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28810, 00000, "Cannot create key descriptor." // *Cause: The system failed to create a key descriptor. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28811, 00000, "invalid access descriptor" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28812, 00000, "record operation failure" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28813, 00000, "invalid record type" // *Cause: Error not user-visible. // *Action: // *Document: NO / 28814, 00000, "Cannot convert a number in Oracle format to native format." // *Cause: Failed to convert a number from Oracle format to native format. // *Action: This is an internal programming exception. Enable tracing to try // and reproduce the problem. Contact Oracle customer support and // supply the trace file. / 28815, 00000, "Cannot convert a number in native format to Oracle format." // *Cause: Failed to convert a number from native format to Oracle portable // format failed. // *Action: This is an internal programming exception. Enable tracing to try // and reproduce the problem. Contact Oracle customer support and // supply the trace file. / 28816, 00000, "No password provided for a PL/SQL function." // *Cause: A required password was not passed to a PL/SQL function. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28817, 00000, "PL/SQL function returned an error." // *Cause: A PL/SQL function returned an error unexpectedly. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 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. Enable tracing to find more // information. Contact Oracle customer support if needed. / 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28820, 00000, "Signature or decryption/encryption state is 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28822, 00000, "Required seed is not specified." // *Cause: No seed was specified to the PL/SQL seed initialization function. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28823, 00000, "Number of random bytes to generate is 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28824, 00000, "invalid encryption/decryption/signature state passed" // *Cause: An invalid state was passed to a PL/SQL encryption, decryption, or // signature procedure or function. // *Action: Specify a correct state value. // *Document: NO / 28825, 00000, "No cryptographic engine function specified." // *Cause: No function was specified for the cryptographic engine. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28826, 00000, "invalid cryptographic engine function passed" // *Cause: An incorrect cryptographic engine function was passed to a PL/SQL // function or procedure. // *Action: Specify a correct engine function. // *Document: NO / 28827, 00000, "invalid cipher type passed" // *Cause: An incorrect cipher type was passed to a PL/SQL function or // procedure. // *Action: Specify a correct cipher type. // *Document: NO / 28828, 00000, "invalid identity type passed" // *Cause: An incorrect identity type was passed to a PL/SQL function or // procedure. // *Action: Specify a correct identity type. // *Document: NO / 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 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. // *Document: NO / 28833, 00000, "inadequate information provided" // *Cause: Inadequate information, which usually is in the form of parameters, // has been provided to a PL/SQL function. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28834, 00000, "Buffer is too small." // *Cause: The buffer provided by PL/SQL to an Oracle Security Server toolkit // function is too small for the data to be returned. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28835, 00000, "Identity descriptor is not present or is too small." // *Cause: An identity descriptor, which is passed to a PL/SQL function or descriptor, // was not provided or was not the correct size. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28836, 00000, "Wallet is not open." // *Cause: The wallet to be used has not yet been opened. // *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. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28838, 00000, "no identity descriptor" // *Cause: No identity descriptor was specified to a PL/SQL function or // procedure. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28839, 00000, "no persona descriptor" // *Cause: No persona descriptor was specified to a PL/SQL function or // procedure. // *Action: This is an internal error. Enable tracing to find more // information. Contact Oracle customer support if needed. // *Document: NO / 28840, 00000, "Wallet is already open." // *Cause: An attempt was made to open a wallet that was already open. // *Action: This is a programming error. A wallet should only be opened once. / 28841, 00000, "Operation is not supported." // *Cause: An attempt was made to perform an operation that is not supported. // *Action: This is a programming error. Please refer to Oracle documentation // to determine which operations are supported. / 28842, 00000, "Incorrect file permissions" // *Cause: The subject file did not have the correct permissions for the operation. // *Action: Ensure that the file permissions allow the current operation. / 28843, 00000, "Operating system error while creating/opening file" // *Cause: An operating system dependent error occurred while trying to create/ // open the file or while trying to set the appropriate permissions on // the file. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28844, 00000, "No wallet present" // *Cause: There was no wallet in the location specified. // *Action: Check to ensure that the wallet is in the correct directory // location. / 28845, 00000, "No certificate" // *Cause: Either there is no certificate or the system cannot find it. // *Action: Check to ensure that the certificate is in the specified wallet. / 28846, 00000, "No private key" // *Cause: Either there is no private key or the system cannot find it. // *Action: Check to ensure that the private key is in the specified wallet. / 28847, 00000, "No clear private key file" // *Cause: Failed to retrieve private key from SSO wallet // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28848, 00000, "No encrypted private key file" // *Cause: Failed to retrieve private key from the wallet // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28849, 00000, "No Trustpoints" // *Cause: The wallet does not have any trusted certificates // *Action: Ensure that the wallet/keystore has trusted certificates. / 28850, 00000, "No clear trustpoint file" // *Cause: // *Action: // *Document: NO / 28851, 00000, "No encrypted trustpoint file" // *Cause: // *Action: // *Document: NO / 28852, 00000, "Bad password" // *Cause: The password created for an obfuscated wallet exceeds the maximum // password length limit. // *Document: NO // *Action: / 28853, 00000, "Initialization failure" // *Cause: Either initialization or module loading has failed. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28854, 00000, "Memory allocation failure" // *Cause: The allocation of memory failed due to insufficient 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 attempt was // made to select a mode of operation that is not allowed. // *Action: Refer to the SSL chapter in the product's documentation. // / 28856, 00000, "Buffer overflow error" // *Cause: A buffer overflow error occurred during SSL handshake. // *Action: This error is not normally visible to the user. Enable tracing // and attempt the connection again. Then contact Oracle customer // support with the trace output. // *Document: NO / 28857, 00000, "Unknown SSL error" // *Cause: An unknown SSL error occurred. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28858, 00000, "SSL protocol error" // *Cause: An error occurred while negotiating the SSL handshake between two processes. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28859, 00000, "SSL negotiation failure" // *Cause: An error occurred during negotiation 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. // *Action: Configure each process so they support a common cipher suite. // Then attempt the connection again. If error occurs again, enable // tracing and retry the connection. Then contact Oracle customer // support with the trace output. / 28860, 00000, "Fatal SSL error" // *Cause: An error occurred during the SSL connection to the peer. It is likely // that this side sent data which the peer rejected. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 28861, 00000, "SSL connection would block" // *Cause: This error is informational. It should never be communicated // to the user. // *Action: Enable tracing and retry the connection to determine the exact // cause of the error. Contact Oracle customer support if needed. / 28862, 00000, "SSL connection failed" // *Cause: This error occurred because the peer closed the connection. // *Action: Enable tracing on both sides and examine the trace output. // Contact Oracle Customer support with the trace output. / 28863, 00000, "SSL session not found" // *Cause: This error is informational. It indicates that a specified // session does not exist. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 28864, 00000, "SSL connection closed gracefully" // *Cause: This error is informational. It indicates that the connection // closed without error. // *Action: This error is not normally visible to the user. Enable tracing // and retry the connection. 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 peer process quit unexpectedly. // *Action: Enable tracing and retry the connection. The trace output // should indicate how the failure occurred. / 28866, 00000, "Invalid peer certificate encoding" // *Cause: A field from a certificate in the peer's certificate chain could not be // recognized. // *Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the // peer's certificate. Then contact Oracle customer support with the peer's // certificate chain. / 28867, 00000, "Integer value is too big." // *Cause: The certificate presented had an integer field whose value was // too large. // *Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the // peer's certificate. Then contact Oracle customer support with the peer's // certificate chain. / 28868, 00000, "Peer certificate chain check failed." // *Cause: The check of the certificate list presented by the peer // failed. Possible causes include: // 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: Refer to Oracle Wallet Manager documentation to find out how to open // your wallet and ensure that: // 1. all of the certificates installed in your wallet are current // 2. a certificate authority's certificate from your peer's certificate chain // is added as a trusted certificate in your wallet / 28869, 00000, "Peer's certificate is expired." // *Cause: The certificate being used to authenticate a client or server // has expired. // *Action: Obtain a new certificate, which is unexpired, and attempt the // connection again. / 28870, 00000, "Name comparison failure" // *Cause: A comparison of the names contained in two certificates failed. // *Action: This error is not normally visible to the user. Enable tracing // and retry the connection. If the error persists, contact Oracle // customer support. / 28871, 00000, "Peer certificate chain is incomplete." // *Cause: The peer certificate chain presented was incomplete because it did not // end with a self-signed root certificate. // *Action: Refer to Oracle Wallet Manager documentation to find out how to open // your wallet and ensure that: // 1. the certificate authority's root certificate is self-signed. // 2. a certificate authority's certificate from your peer's certificate chain // is added as a trusted certificate in your wallet / 28872, 00000, "Invalid peer certificate format" // *Cause: The peer certificate does not conform to the X.509v3 standard. // *Action: Refer to Oracle Wallet Manager documentation to find out how to get the // peer certificate. Then contact Oracle customer support with the peer's // certificate. / 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 retry the connection. If the error persists, contact // Oracle customer support. // *Document: NO / 28874, 00000, "SSL: I/O closed - override goodbye kiss" // *Cause: This error is informational. It indicates that the connection closed // without error. // *Action: This error is not normally visible to the user. Enable tracing // and retry the connection. If the error persists, contact // Oracle customer support. / 28875, 00000, "SSL: use server-gated cryptographic suites" // *Cause: This is used as a internal status indicator and not really // an error. // *Action: This message is not normally visible to the user. Enable tracing // and retry the connection. If the 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 retry the connection. If the 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 the process // was a client or a server. // *Action: This error is not normally visible to the user. Enable tracing // and retry the connection. If the error persists, contact // Oracle customer support. / // 28880, 00000, "UNUSED" // *Cause: // *Action: // *Document: NO / // 28881, 00000, "UNUSED" // *Cause: // *Action: // *Document: NO / 28882, 00000, "UNUSED" // *Cause: // *Action: // *Document: NO / 28883, 00000, "UNUSED" // *Cause: // *Action: // *Document: NO / 28884, 00000, "invalid cipher suite" // *Cause: An invalid cipher suite string has been specified in the // product's configuration file. // *Action: Refer to the product documentation for information about // supported cipher suites. / 28885, 00000, "No certificate with the required key usage found." // *Cause: Certificate not created with the appropriate X509v3 key usage // extension. // *Action: Refer to Oracle Wallet Manager documentation to find out the // supported key usages. / 28890, 00000, "Entrust Login Failed" // *Cause: An application failed to log in to an Entrust Profile. // Possible causes include: // 1. Entrust Admin/Authority was not online. // 2. Invalid password for Entrust profile was specified. // 3. Invalid path to Entrust profile was specified // 4. Invalid Entrust initialization file was specified. // 5. Entrust Server Login program was 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 examine the trace output // to get exact the Entrust failure codes. / 29000, 00000, "Certificate not installed" // *Cause: Trying to delete a certificate which has not been installed. // *Action: Refer to the Oracle Wallet Manager documentation for information // about delete option. / 29001, 00000, "UNUSED" // *Cause: // *Action: // *Document: NO / 29002, 00000, "SSL transport detected invalid or obsolete server certificate." // *Cause: The client detected a mismatch between the server's distinguished name // specified on the server's certificate and the server's SID or service name. // *Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide // for information about enabling server distinguished name matching. // Contact your administrator to perform the appropriate action. / 29003, 00000, "SSL transport detected mismatched server certificate." // *Cause: The client detected a mismatch between the server's distinguished name // specified on the server's certificate and the server's SID or service name. // *Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide // for information about enabling server distinguished name matching. // Contact your administrator to perform the appropriate action. / 29004, 00000, "Callback Failure" // *Cause: The alert callback returns this error; it is not fatal. // *Document: NO // *Action: / 29005, 00000, "The certificate is invalid." // *Cause: The peer certificate encoding is invalid when using SSL 2.0. // *Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the // peer's certificate. Then contact Oracle customer support with the peer's // certificate chain. / 29006, 00000, "The certificate request message is invalid when using SSL 2.0." // *Cause: There is an error processing the SSL 2.0 REQUEST-CERTIFICATE message. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29007, 00000, "Bad Clear Key Length when using SSL 2.0" // *Cause: The clear key length of an SSL 2.0 Client Master key handshake message // is invalid. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29008, 00000, "Bad DH Param key length" // *Cause: The length of the Diffie-Hellman params exceeds export restrictions. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29009, 00000, "Bad encrypted key length when using SSL 2.0" // *Cause: The encrypted key length of an SSL 2.0 Client Master key handshake // message is invalid. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29010, 00000, "Export key length does not meet export restrictions." // *Cause: The server sent a ServerKeyExchange message with an export key which // does not meet export restrictions. For RSA, the export key must // be exactly 512 bits. // *Action: Obtain a certificate with the appropriate key length. / 29011, 00000, "Finished message is incorrect." // *Cause: The FINISHED message data verification failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29012, 00000, "Bad key argument length when using SSL 2.0" // *Cause: The key argument length of an SSL 2.0 Client Master Key handshake message // is invalid. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29013, 00000, "SSL MAC verification failure" // *Cause: Verification of SSL Record MAC failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29014, 00000, "Maximum fragment length extension is incorrect." // *Cause: The maximum fragment length extension specified is incorrect. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29015, 00000, "incorrect message length" // *Cause: The message length is not correct. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29016, 00000, "inadequate PKCS1 message padding" // *Cause: The message was not properly padded before encryption. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29017, 00000, "The premaster secret length is incorrect." // *Cause: The premaster secret sent by the peer has an incorrect length. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29018, 00000, "The premaster secret contains an incorrect version number." // *Cause: The premaster secret must contain the same version number as the ClientHello. // The version sent by the client was incorrect. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29019, 00000, "The protocol version is incorrect." // *Cause: There is a protocol version mismatch between the two peers. // *Action: Specify the correct protocol version in the product's configuration // file. / 29020, 00000, "The handshake record length is too long." // *Cause: The handshake record length exceeds the maximum that is allowed by the // SSL specification. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29021, 00000, "Secret key length is incorrect when using SSL 2.0." // *Cause: The length of the decrypted ENCRYPTED-KEY is incorrect. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29022, 00000, "Operation is being attempted on the wrong side of the client/server connection." // *Cause: The SSL network layer has detected that the operation has been attempted on // the wrong side of the client/server connection. // *Action: Select the protocol side (of this protocol) to be the same as the one selected // with a previous protocol. / 29023, 00000, "The buffers are not empty." // *Cause: Trying to free buffers that are not empty. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29024, 00000, "Certificate validation failure" // *Cause: The certificate sent by the other side could not be validated. This may occur if // the certificate has expired, has been revoked, or is invalid for another reason. // *Action: Check the certificate to determine whether it is valid. Obtain a new certificate, // alert the sender that the certificate has failed, or resend. / 29025, 00000, "Error found in certificate check callback." // *Cause: The application callback failed during additional certificate // validation. Additional checks include CRL validation and extension checking. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29026, 00000, "Decryption failure" // *Cause: SSL record decryption failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29027, 00000, "Error in entropy collection" // *Cause: The internal entropy collection failed to generate enough seed data. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29028, 00000, "Server verification failure when using SSL 2.0" // *Cause: Processing of an SSL 2.0 SERVER-VERIFY message failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29029, 00000, "SSL handshake already completed" // *Cause: The system is trying to initiate a handshake when it has already been completed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29030, 00000, "SSL handshake is requested." // *Cause: The peer sends this message if it wishes to renegotiate. The application // can either proceed with the renegotiation or reject the request. // *Action: This is not an error. To find out more details enable tracing // and retry the connection. Contact Oracle customer support with the // trace output. / 29031, 00000, "SSL handshake is required." // *Cause: Renegotiation cannot proceed before the SSL handshake is completed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29032, 00000, "The given identity is not complete." // *Cause: The certificate list does not contain both private key and certificate. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29033, 00000, "Invalid PFX" // *Cause: The PFX is invalid for this operation containing either no certificates // and private key or multiple private keys. However, the API which returns // this error is not used in our code. // *Document: NO // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29034, 00000, "Correct cipher suite or client authentication is needed." // *Cause: Before installing a private key, a cipher suite or client authentication suite // using the same key exchange algorithm must be installed first. This has not // been done. // *Action: Install a cipher suite or client authentication suite that uses the same key // exchange algorithm as the private key before re-installing the private key. / 29035, 00000, "Pseudo Random Number Generator is needed" // *Cause: PRNG not set yet. A PRNG must be installed first. // *Document: NO // *Action: / 29036, 00000, "This feature is not supported" // *Cause: Operation is not supported by the current connection parameters. // *Action: Check the Oracle documentation to determine the appropriate // connection parameters required for this operation. / 29037, 00000, "No certificate is present" // *Cause: The other client or server sent a certificate message that contained // no certificates. // *Action: Check the other side (client or server) to ensure they have // appropriate credentials. / 29038, 00000, "There are no matching certificates." // *Cause: The other client or server sent a certificate message that contained // a certificate which was not signed by a trusted certificate authority (CA). // *Action: Check to ensure that the other client or server sends a certificate which is // signed by a CA that is in your trusted list. Or, include the CA // certificate for the other client or server's certificate as a trustpoint // in your wallet. / 29039, 00000, "There are no matching cipher suites." // *Cause: Neither end of the handshake can agree on a cipher suite. // *Action: Check to ensure that both sides of the handshake select cipher suites // that are supported. / 29040, 00000, "There are no supported cipher suites." // *Cause: This end of the handshake cannot support any cipher suites. This // connection and the peer have some matching cipher suites, however, // these cipher suites cannot be negotiated because they cannot be supported // by the connection. // *Action: Check to ensure that both sides of the handshake select cipher suites // that are supported by the connection. Refer to Oracle documentation for // supported cipher suites. / 29041, 00000, "The callback is NULL." // *Cause: A NULL callback was passed. // *Document: NO // *Action: / 29042, 00000, "Read buffer is not empty." // *Cause: There is an attempt to free a read buffer that is not empty. // *Document: NO // *Action: / 29043, 00000, "Read is required." // *Cause: Renegotiation with the peer has not yet started. There is // application data which must be processed before the // handshake can proceed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29044, 00000, "Renegotiation has already been requested." // *Cause: Renegotiation has already been requested. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29045, 00000, "Renegotiation request has been refused." // *Cause: A renegotiated handshake has been refused by the peer. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29046, 00000, "Session is resumable." // *Cause: Server is trying to resume a session with different session parameters. // *Action: Server should resume the session with the correct session parameters. / 29047, 00000, "Mismatch in Transport Layer Security extension" // *Cause: Neither side can agree on a TLS extension. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29048, 00000, "Unexpected message received." // *Cause: An unexpected message has been received. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29049, 00000, "Unknown record" // *Cause: The record type is unknown. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29050, 00000, "Installed client authentication mode is not supported." // *Cause: The enabled client authentication mode(s) cannot be used within // the selected cipher suite. // *Action: Enable a client authentication mode that can be used within the selected // cipher suite. / 29051, 00000, "The given public key type is not supported." // *Cause: The public key in the first certificate is not supported. // *Action: Check to ensure that the certificate complies with the X.509v3 standard. / 29052, 00000, "Write buffer is not empty." // *Cause: There is an attempt to free a write buffer that is not empty. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29084, 00000, "The parameter specified is illegal." // *Cause: The parameter is not correct. For example, it could be bad input, // or an invalid message. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29095, 00000, "Index is not correct." // *Cause: The instance identified by the index parameter doesn't exist. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29096, 00000, "The given length is incorrect." // *Cause: The specified length is too small or is invalid. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29100, 00000, "Cannot create local key ID." // *Cause: Creation of local key identifier for the certificate or the private key // failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29101, 00000, "Cannot add private key bag." // *Cause: The private key could not be added to the PKCS#12 object. Possible reasons // are: (i) A required parameter is NULL (ii) The PKCS#12 construct is not // supported (iii) An ASN.1 encoding error occurred in the certificate. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29102, 00000, "Cannot add certificate bag." // *Cause: Creation of certificate bag failed. The application could have // run out of memory. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29103, 00000, "Cannot create PKCS #12 wallet." // *Cause: Creation of PKCS#12 wallet failed possibly due to memory allocation // failure. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29104, 00000, "Cannot add certificate request." // *Cause: Adding certificate request to the PKCS#12 wallet failed. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29105, 00000, "Cannot export PKCS #12 wallet." // *Cause: A required parameter is NULL or the PKCS#12 construct is not supported. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29106, 00000, "Cannot import PKCS #12 wallet." // *Cause: A required parameter is NULL or the BER-encoding is malformed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29107, 00000, "Cannot create PKCS #12 wallet." // *Cause: PKCS#12 wallet creation failed. The application may have // run out of memory. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29108, 00000, "Cannot initialize random object." // *Cause: The random object could not be initialized or seeded. Either memory // allocation has failed or the pseudo random number generator module // has not been installed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29109, 00000, "Cannot create private key object." // *Cause: The private key object could not be created. Memory allocation may have // failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29110, 00000, "Invalid PKCS #12 bag type" // *Cause: The PKCS #12 bag type is invalid. Either one of the required parameters // is NULL or the requested OID is not in the list. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29111, 00000, "Invalid index" // *Cause: The index passed for getting the bag type is less than 1. // *Action: Check to ensure that the index is greater than 1. / 29112, 00000, "Cannot access attributes from a PKCS #12 certificate bag." // *Cause: The certificate cannot be accessed. One of the required parameters is // probably NULL, or the index specified by the application does not contain // a certbag, or the certificate could be malformed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29113, 00000, "Cannot access attributes from a PKCS #12 key bag." // *Cause: Retrieval of the private key failed. One of the required parameters // is probably NULL or the index specified by the application does not // contain a key bag. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29114, 00000, "Cannot import private key." // *Cause: The private key could not be imported. One of the required parameters // could be NULL or the encoded private key could be malformed. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29115, 00000, "Cannot export private key." // *Cause: The private key could not be exported. Either the application ran out // of memory or the key type is not valid. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29116, 00000, "Cannot get PKCS #12 attributes." // *Cause: Retrieval of an attribute failed. One of the required parameters could // be NULL. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29117, 00000, "Cannot add PKCS #12 attributes." // *Cause: Could not add an attribute. The attribute parameter could be NULL. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29118, 00000, "Cannot create PKCS #12 attributes." // *Cause: Creation of the attributes failed, possibly due to a memory // allocation error. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29119, 00000, "Cannot import certificate." // *Cause: The certificate cannot be imported. One of the required parameters could // be NULL or the certificate has an invalid X.509 BER or DER encoding. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29120, 00000, "Cannot export certificate." // *Cause: The certificate cannot be exported. One of the required parameters could // be NULL. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29122, 00000, "could not add pkcs11 info to the pkcs12 wallet" // *Cause: Failed while adding pkcs11 information into a pkcs12 wallet. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29123, 00000, "could not get pkcs11 info from the pkcs12 wallet" // *Cause: An error was encountered while retrieving pkcs11 information from // the wallet. // *Action: Enable tracing to determine the exact cause of this error. // Contact Oracle customer support if needed. / 29124, 00000, "pkcs11 library name already set" // *Cause: pkcs11 library information was already set in the wallet. // *Action: Use a different wallet that does not have this information. // If issue persists, enable tracing to determine the exact cause of // the error. Contact Oracle customer support if needed. / 29125, 00000, "pkcs11 token label already set" // *Cause: pkcs11 token label information was already set in the wallet. // *Action: Use a different wallet that does not have this information. // If issue persists, enable tracing to determine the exact cause of // the error. Contact Oracle customer support if needed. / 29126, 00000, "pkcs11 token passphrase already set" // *Cause: The pkcs11 token passphrase can be set only once in the wallet. // *Action: Use a different wallet that does not have this information. // If issue persists, enable tracing to determine the exact cause of // the error. Contact Oracle customer support if needed. / 29127, 00000, "unknown pkcs11 information" // *Cause: An unknown pkcs11 information type was encountered. The wallet may // have been corrupted due to a system error or memory corruption. // *Action: Enable tracing and retry the failed operation. // Contact Oracle customer support with the trace output. / 29128, 00000, "pkcs11 library name not set" // *Cause: The wallet does not have pkcs11 library information. // *Action: Ensure that the wallet was created with valid library location or // update the wallet with this information. / 29129, 00000, "pkcs11 token label not set" // *Cause: The wallet does not have pkcs11 token label information. // *Action: Ensure that the wallet was created with valid token label // information or update the wallet with this information. / 29130, 00000, "pkcs11 token passphrase not set" // *Cause: The wallet does not have pkcs11 token passphrase. // *Action: Ensure that the wallet was created with valid token passphrase // information or update the wallet with this information. / 29131, 00000, "pkcs11 certificate label already set in wallet" // *Cause: The pkcs11 certificate label was already set in the wallet. // *Action: Use an empty wallet (created with orapki). / 29135, 00000, "Seed generation for Random Number Generator failed." // *Cause: Generation of seed for random number generator failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29136, 00000, "The allocated buffer is too small." // *Cause: The output buffer is too small. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29137, 00000, "The global context is incorrect." // *Cause: The global context is incorrectly configured or invalid. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29140, 00000, "Cannot create certificate object." // *Cause: Creation of the certificate object failed. The application could have // run out of memory. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29141, 00000, "Cannot import in the der format." // *Cause: Cannot import the certificate into the certificate object. The reason // could be a malformed certificate. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29150, 00000, "DES self-test failure" // *Cause: DES power up self-test has failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29151, 00000, "3DES self-test failure" // *Cause: 3DES power up self-test has failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29152, 00000, "SHA-1 self-test failure" // *Cause: The SHA-1 power up self-test has failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29153, 00000, "RSA self-test failure" // *Cause: The RSA power up self-test has failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29154, 00000, "deterministic RNG self-test failure" // *Cause: The deterministic Random Number Generator power up self-test has failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29155, 00000, "continuous key pair consistency check self-test failure" // *Cause: The public-private key pair check test failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29156, 00000, "conditional RNG self-test failure" // *Cause: Continuous Random Number Generator test, which is needed in FIPS mode, // has failed. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29157, 00000, "Unable to build an absolute path to the library." // *Cause: Not able to construct an absolute path to the // location of the library. // *Action: Enable tracing and attempt the connection again. Contact // Oracle customer support with the trace output. / 29158, 00000, "Unable to open library." // *Cause: Opening of the library failed. // *Action: Check to ensure that the library is present in the location // specified, and that it has the appropriate file permissions. / 29159, 00000, "Unable to read library." // *Cause: Not able to read the library on which the DAC check has // to be performed. Read call failed. // *Action: Check if the library has the appropriate file permissions. / 29160, 00000, "NZ library being used is different." // *Cause: The NZ library being used at runtime is not the // same one on which the digest was computed for the // software integrity check. // *Action: Check to ensure that the library being used is the same as the one on // which the digest was pre-computed. / 29161, 00000, "software integrity self-test failure" // *Cause: The software integrity check test on the NZ shared library // has failed. // *Action: Check to ensure that the library being used is the same as the one on // which the digest was pre-computed. / 29162, 00000, "Non-FIPS cipher suites being used in FIPS mode." // *Cause: The cipher suite being used does not contain FIPS-approved // algorithms. / // *Action: Use cipher suites that contain FIPS-approved algorithms. / 29163, 00000, "Third party PKI vendor is not supported in FIPS mode." // *Cause: Third party PKI vendors like Entrust and MCS are not supported // in FIPS mode. // *Action: Use only Oracle PKI when running in FIPS mode. / 29164, 00000, "External PKCS #12 wallet is not supported in FIPS mode." // *Cause: PKCS #12 wallets created using third party software cannot be // used in FIPS mode. // *Action: Use only PKCS #12 wallets created by Oracle Wallet Manager when running in // FIPS mode. / 29176, 00000, "CRL signature verification failed" // *Cause: A CRL is verified before being used. CRL signature cannot be // verified. // *Action: Get a new CRL from CA / 29177, 00000, "certificate serial number is not in CRL" // *Cause: Cert is not revoked // *Action: / 29178, 00000, "certificate serial number is in CRL" // *Cause: Cert has been revoked // *Action: Reject the certificate / 29179, 00000, "certificate validation check failed" // *Cause: Could not complete checking certificate status with a CRL. // *Action: Enable tracing to find more information on this error. // Contact Oracle customer support if needed. / 29180, 00000, "Unsupported validation protocol" // *Cause: The certificate validation protocol is not supported // *Action: Make sure a supported certificate validation protocol is specified / 29181, 00000, "ldap_open failed" // *Cause: Could not connect to the LDAP server // *Action: Ensure that correct LDAP information was provided. Enable tracing // to find more information. Contact Oracle customer support if needed. / 29182, 00000, "ldap_bind failed" // *Cause: Could not log in to the LDAP server // *Action: Ensure that correct LDAP credentials were provided. Enable tracing // to find more information. Contact Oracle customer support if needed. / 29183, 00000, "ldap_search failed" // *Cause: Failed to complete search operation in LDAP server // *Action: Enable tracing to find more information on this error. // Contact Oracle customer support if needed. / 29184, 00000, "ldap_result failed" // *Cause: Failed to retrieve results from LDAP operation // *Action: Enable tracing to find more information on this error. // Contact Oracle customer support if needed. / 29185, 00000, "ldap_first_attribute failed" // *Cause: Could not get the first attribute from LDAP entry. // *Action: Enable tracing to find more information on this error. // Contact Oracle customer support if needed. / 29186, 00000, "ldap_get_values_len failed" // *Cause: Failed to retrieve attribute values from LDAP entry // *Action: Enable tracing to find more information on this error. // Contact Oracle customer support if needed. / 29187, 00000, "unsupported validation mechanism" // *Cause: The validation mechanism specified in OID is not supported // *Action: Make sure a supported validation mechanism is set in OID / 29188, 00000, "ldap_count_entries failed" // *Cause: Failed to get count of entries from a search result chain. // *Action: Enable tracing to find more information on this error. // Contact Oracle customer support if needed. / 29189, 00000, "No entry found in OID" // *Cause: CRL not found in OID // *Action: Upload the CRL to OID / 29190, 00000, "Multiple entries in OID" // *Cause: For a given issuer name there should be only one CRL in OID // *Action: Make sure there is only one CRL for a given issuer name in OID / 29191, 00000, "OID connection information not set" // *Cause: To connect to OID the connection information must be available // *Action: Set the OID connection information. / 29192, 00000, "Validation mechanism not set in OID" // *Cause: The validation mechanism to be used is not set in OID // *Action: Set validation mechanism to be used in OID at // cn=ValidationMechanism, cn=Validation, cn=PKI, cn=Products, // cn=OracleContext / 29193, 00000, "no CRL found using CRLDP mechanism" // *Cause: A CRL could not fetched using CRL Distribution point (CRLDP) // *Action: Contact the CA / 29194, 00000, "no CRL found in cache" // *Cause: CRL not in cache // *Action: / 29195, 00000, "CRL is expired" // *Cause: CRL nextUpdate time is in the past // *Action: Get a new CRL from the CA / 29222, 00000, "Distinguished name does not match." // *Cause: Distinguished name (DN) on certificate doesn't match user. // *Action: Create the global user in the database with the DN that matches with the // one in the user certificate on the client side. / 29223, 00000, "Cannot create certificate chain." // *Cause: Unable to create a certificate chain with the existing trust points // for the certificate that is to be installed. // *Action: Install the trust point that signed the certificate. / 29224, 00000, "Cannot locate matching certificate request." // *Cause: No matching certificate request for the certificate was found. // *Action: Install the correct certificate. / 29225, 00000, "Certificate already installed." // *Cause: Attempting to install a certificate into a persona which already has it. // *Action: Do not install the certificate. / 29226, 00000, "No matching private key found." // *Cause: Could not locate a matching private key // in the persona for the given certificate (public key). // *Action: / 29227, 00000, "Certificate is expired." // *Cause: Certificate is no longer valid.. // *Action: Obtain another certificate or renew this certificate. / 29228, 00000, "Cannot calculate the number of bytes for output." // *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 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 being 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 being used. / 29231, 00000, "the cryptographic engine failed to initialize" // *Cause: During initialization of the cryptographic engine, some // failure occurred. Possible causes include 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 occurred. 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 may be passing wrong parameters. // *Action: Check the parameters being used with the cryptographic // functions. / 29241, 00000, "a buffer block needs 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 may be passing 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 unrecognized 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. 29280, 00000, "invalid directory path" // *Cause: A corresponding directory object does not exist. // *Action: Correct the directory object parameter, or create a corresponding // directory object with the CREATE DIRECTORY command. 29281, 00000, "invalid mode" // *Cause: An invalid value was specified for file open mode. // *Action: Correct the mode to be one of the values: 'r','a', or 'w'. 29282, 00000, "invalid file ID" // *Cause: A file ID handle was specified for which no corresponding // open file exists. // *Action: Verify that the file ID handle is a value returned from a // call to UTL_FILE.FOPEN. 29283, 00000, "invalid file operation" // *Cause: An attempt was made to read from a file or directory that does // not exist, or file or directory access was denied by the // operating system. // *Action: Verify file and directory access privileges on the file system, // and if reading, verify that the file exists. 29284, 00000, "file read error" // *Cause: An attempt to read from a file failed. // *Action: Verify that the file exists, and that it is accessible, and // that it is open in read mode. 29285, 00000, "file write error" // *Cause: Failed to write to, flush, or close a file. // *Action: Verify that the file exists, that it is accessible, and that // it is open in write or append mode. 29286, 00000, "internal error" // *Cause: A fatal error occurred while allocating PL/SQL session memory. // *Action: Verify that the PL/SQL session is connected and that // adequate memory resources are available. 29287, 00000, "invalid maximum line size" // *Cause: An invalid maximum line size value was specified. // *Action: Correct the maximum line size to be in the range [1, 32767]. 29288, 00000, "invalid file name" // *Cause: A NULL or zero length file name was specified. // *Action: Correct the file name to be a nonzero length string. 29289, 00000, "directory access denied" // *Cause: A directory object was specified for which no access is granted. // *Action: Grant access to the directory object using the command // GRANT READ ON DIRECTORY [object] TO [username];. 29290, 00000, "invalid offset specified for seek" // *Cause: An attempt was made to seek past the end of the file, or // both the absolute and relative offsets were NULL, or // absolute offset was less than zero. // *Action: If specifying an absolute offset, ensure it is in the range // [0, ], or // if specifying a relative offset, ensure it is no greater than the // current byte position plus the number of bytes remaining in the // file. 29291, 00000, "file remove operation failed" // *Cause: A file deletion attempt was refused by the operating system. // *Action: Verify that the file exists and delete privileges granted on // the directory and the file. 29292, 00000, "file rename operation failed" // *Cause: A file rename attempt was refused by the operating system // either because the source or destination directory does not // exist or is inaccessible, or the source file isn't accessible, // or the destination file exists. // *Action: Verify that the source file, source directory, and destination // directory exist and are accessible, and that the destination // file does not already exist. 29293, 00000, "A stream error occurred during compression or uncompression." // *Cause: The stream state was discovered to be invalid during compression // or uncompression, or an invalid compression quality was requested // or a NULL or invalid compression parameter was detected. // *Action: Verify that quality is within the range [0,9] and that valid // input source data exists. 29294, 00000, "A data error occurred during compression or uncompression." // *Cause: An error occurred while compressing or uncompressing input source. // *Action: Verify that source data is a valid compressed or uncompressed // data set. 29295, 00000, "invalid mime header tag" // *Cause: An error occurred while scanning string for mime header tag // *Action: Verify that source data is a valid mime header string, in the // format: =????= 29296, 00000, "invalid encoded string" // *Cause: An error occurred while decoding the input string // *Action: Verify that source data is a valid encoded string. 29297, 00000, "The compressed representation is too big" // *Cause: The compressed output is too big to return. // *Action: Do not attempt to compress source data. 29298, 00000, "Character set mismatch" // *Cause: The character set mode in which the file was opened did // not match the character set of the read or write operation. // *Action: Use the correct UTL_FILE read and write procedures which // coorespond to the character set mode in which the file was // opened. 29299, 00000, "Invalid handle for piecewise compress or uncompress" // *Cause: The process program opened too many handles, and the specified // handle was either uninitialized or outside a valid range. // *Action: Close some handles and verify that the specified handle is opened // or within a valid range. / / / 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. / 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, "ALTER DATABASE SET COMPATIBILITY command not supported by %s" // *Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one // or more instances do not support dynamic compatible setting change. // *Action: No action required. 29324, 00000, "SET COMPATIBILITY release string format is wrong" // *Cause: It should be of the form x.x.x // *Action: Use the correct format. / 29325, 00000, "SET COMPATIBILITY release number lower than %s" // *Cause: The SET COMPATIBILITY release compatibility release number was lower // than the current compatible setting. // *Action: Specify a higher release number. / 29326, 00000, "SET COMPATIBILITY release number higher than %s" // *Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one // or more instances had a lower release number. // *Action: Specify a lower release number. / 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. / 29329, 00000, "Table not of type XMLType" // *Cause: Table is not XMLType table // *Action: Ensure table is a XMLType table / / / 29330 - 29334 Reserved for DBMS_SCRIPT package / 29330, 00000, "Source script length too big" // *Cause: Source script length exceeded the maximum size of 4 Gigabytes. // *Action: Make sure source script length is not greater than 4 Gigabytes. / / / 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, "cannot plug a tablespace into a database using an incompatible character set" // *Cause: Oracle does not support plugging a tablespace into a database // using an incompatible 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, sysaux, or temporary tablespace '%s'" // *Cause: The referred tablespace is either the system tablespace, the // sysaux 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. 29353, 00000, "The transportable list is too long." // *Cause: The transportable list exceeds the buffer size of 32767. // *Action: Reduce the list of tablespaces to transport. / / 29355 - 29399 RESERVED FOR DBMS RESOURCE MANAGER PACKAGES / 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, or CREATE_CATEGORY of package // DBMS_RESOURCE_MANAGER is 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, "resource plan %s contains multiple directives for subplan %s" // *Cause: A resource plan and its subplans had more than one directive // for a particular subplan. // *Action: Modify the resource plan or its subplans so that there is at most // one directive for this subplan. / 29361, 00000, "value %s is outside valid range of 0 to 100" // *Cause: An invalid value was specified for a plan directive parameter. // *Action: Specify a 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, "parameters %s and %s cannot both be set" // *Cause: An attempt was made to set both parameters. // *Action: Only set one of parameters or neither of them. 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 values %s for level %s, plan %s exceeds %s" // *Cause: The sum of plan directive parameter values for the specified // plan level exceeded 100. // *Action: Alter the values for the level so that they sum to 100. / 29376, 00000, "number of consumer groups %s in plan %s exceeds %s" // *Cause: The number of consumer groups in the specified plan was // more than 28. // *Action: Change the plan to have no more than 28 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. / 29378, 00000, "invalid consumer group mapping priorities" // *Cause: The mapping priorities were not unique integers within the // valid range. // *Action: Set the mapping priorities to unique integers within the // documented range. / 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 consumer groups and subplans for plan %s exceeds %s" // *Cause: An attempt was made to create or modify the specified plan, but // the plan has more than 28 consumer groups or subplans. // *Action: Make sure the specified plan points to no more than 28 distinct // consumer groups or subplans. / 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. / 29392, 00000, "cpu parameters for level %s for plan %s must be zero" // *Cause: The cpu parameters for the specified level had a non-zero value, // which is not a valid value for the plan's current cpu policy. // *Action: Change the cpu level parameters for the specified level to zero // or change the plan cpu policy. / 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 or an INTERNAL_USE group. // *Action: Certain groups are only 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 or an INTERNAL_USE group. // *Action: Certain groups are only 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 or an INTERNAL_USE group. // *Action: Certain groups are only 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 - 29469 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. / / / 29470 - 29489 RESERVED FOR THE DBMS_SQL PACKAGE / 29470, 00000, "Effective userid or roles are not the same as when cursor was parsed" // *Cause: The effective userid or roles on this call to DBMS_SQL are not the // same as those at the time the cursor was parsed. // *Action: Make sure the effective userid and roles are the same as when cursor // was pared. / 29471, 00000, "DBMS_SQL access denied" // *Cause: DBMS_SQL access was denied due to security concerns. // *Action: Check the alert log and trace file for more information. / 29472, 00000, "DBMS_SQL.OPEN_CURSOR failed. security_level is outside the valid range of 0 to 2" // *Cause: An invalid security_level value was specified. // *Action: Specify a valid range of 0 to 2. / 29473, 00000, "privilege checking level specified for '%s' must be between 0 and 2" // *Cause: Invalid privilege checking level specified. // *Action: Correct the privilege checking level specified. / 29474, 00000, "DBMS_SQL.OPEN_CURSOR failed. security_level of 0 is not allowed" // *Cause: Security level of 0 is specified with DBMS_SQL.OPEN_CURSOR. // *Action: Specify a valid security level. 29475, 00000, "useLogonRoles=>TRUE not permitted with userid=>NULL" // *Cause: An unsupported combination of argument values was present in a call // to DBMS_SYS_SQL.PARSE_AS_USER. // *Action: Specify a valid combination of argument values. / 29476, 00000, "DBMS_SQL.CLOSE_CURSOR failed" // *Cause: An attempt was made to close a DBMS_SQL cursor while it was // executing under its own context. // *Action: Rewrite the program so that it does not attempt to close a // DBMS_SQL cursor while it is executing under its own context. 29477, 00000, "SQL statement size in bytes is too big" // *Cause: The size of the SQL statement exceeded 4 gigabytes -1. // *Action: Reduce the size of the SQL statement. / / 29490 - 29499 RESERVED FOR THE DBMS_PARALLEL_EXECUTE PACKAGE / 29490, 00000, "insufficient privilege" // *Cause: The ADM_PARALLEL_EXECUTE role needed to execute the subprogram was not granted. // *Action: Obtain ADM_PARALLEL_EXECUTE role and try again. / 29491, 00000, "invalid table for chunking" // *Cause: An attempt was made to chunk a table by ROWID, but the table was not a physical table or the table was an IOT. // physical table or the table is an IOT. // *Action: Use a table which has physical ROWID. / 29492, 00000, "invalid state for create chunk" // *Cause: An attempt was made to create chunks on a task which was not in the CREATED state. // *Action: Make sure that the task is in the CREATED state. / 29493, 00000, "invalid status" // *Cause: An attempt was made to set an invalid value to the chunk status. // *Action: Make sure that the status value is valid. / 29494, 00000, "invalid state for run task" // *Cause: An attempt was made to execute the task which was not in the CHUNKED state. // *Action: Make sure that the task is in the CHUNKED state. / 29495, 00000, "invalid state for resume task" // *Cause: An attempt was made to resume execution but the task was not the FINISHED_WITH_ERROR or CRASHED state. // *Action: Make sure that the task is in the FINISHED_WITH_ERROR or CRASHED // state. / 29496, 00000, "Parameter [%s] is null or its value length exceeds the maximum limit [%s]" // *Cause: The input argument was null, or it exceeded the maximum length limit. // *Action: Make sure that the argument is not null, and its length is within the limit. / 29497, 00000, "duplicate task name" // *Cause: A task with the same name was already in existence. // *Action: Use another name. / 29498, 00000, "task not found" // *Cause: The task did not exist. // *Action: Use an existing task. / 29499, 00000, "chunk not found" // *Cause: The specified chunk did not exist. // *Action: Specify an existing chunk. / / 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. / 29558, 00000, "JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions." // *Cause: JAccelerator (NCOMP) is not installed. // *Action: Please refer to the Post-installation Tasks section in the // Database Install Guide for instructions on how to install // JAccelerator (NCOMP). / 29561, 00000, "Java VM JIT not supported on this platform." // *Cause: Java VM JIT is not supported on this platform. // *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. / 29665, 00000, "Java thread deadlock detected" // *Cause: The Java VM has detected a thread deadlock. // // *Action: Modify the Java program to avoid the deadlock condition. / / 29700-29799 reserved for Global Enqueue Service / 29701, 00000, "unable to connect to Cluster Synchronization Service" // *Cause: Connect to CSS failed or timed out. // *Action: Verify the state of the CSS. If the CSS was not started, // start it and then retry the database startup. If the CSS died // or is not responding, check the Oracle and CSS trace files for // errors and contact Oracle Support Services. 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. // Check the Oracle LMON trace files for errors. // Also, check the related CSS trace file 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. 29707, 00000, "inconsistent value %s for initialization parameter %s with other instances" // *Cause: The value of the initialization parameter in error must be // identical on all Oracle cluster database instances and was not. // *Action: Check your INIT.ORA files on all instances and ensure that the // initialization parameters in error have the same value. 29708, 00000, "error occurred in Cluster Synchronization Services" // *Cause: An unexpected error occurred while performing a CSS operation. // *Action: Verify the state of the CSS. If the CSS died or // is not responding, check the ORACLE and CSS trace // files for errors and contact Oracle Support Services. 29709, 00000, "Communication failure with Cluster Synchronization Services" // *Cause: Could not communicate with CSS to complete the operation. // *Action: Verify the state of the CSS. If the CSS died or // is not responding, check the ORACLE and CSS trace // files for errors and contact Oracle Support Services. 29710, 00000, "Current operation aborted by Cluster Synchronization Services" // *Cause: The operation could not be performed or CSS was shutting down. // *Action: Check the log file of Cluster Synchronization Services daemon // to verify the state of the service. Start the service if needed; // otherwise, contact Oracle Support Services. 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 internal error checking event" // *Document: NO // *Cause: // *Action: check for internal errors in global enqueue service 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. 29719, 00000, "enable IMR split brain test event" // *Document: No // *Cause: // *Action: Enable specific test scenerios for various split brain tests 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: 29724, 00000, "enable global enqueue heartbeat and CSS/GIPC event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue heartbeat operations and CSS/GIPC 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. 29733, 00000, "enable multiple recovery domains event trace" // *Document: NO // *Cause: // *Action: Dump trace for ges/gcs multiple recovery domains 29735, 00000, "instance specified no longer exists" // *Cause: A client of the global enqueue service specified an instance // that no longer existed. // *Action: Process aborts current operation due to termination of // an instance 29740, 00000, "evicted by instance number %s, group incarnation %s" // *Cause: This instance was evicted from the group by another instance of the // cluster database group for one of several reasons, which may // include a communications error in the cluster and failure to issue // a heartbeat to the control file. // *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 29742, 00000, "incompatible Instance Membership Recovery protocol among instances" // *Cause: The selected Instance Membership Recovery protocol was not // compatible with other running instances in the cluster database. // *Action: Check the Instance Membership Recovery initialization parameters // of all instances to ensure their consistency. 29745, 00000, "Perform IMR test" // *Document: NO // *Cause: // *Action: Simulate various scenarios for IMR testing. 29746, 0000, "Cluster Synchronization Service is being shut down." // *Cause: The administrator has shut down the Cluster Synchronization // Service daemon. This error message is intended to be informative // to users on the status of the service. // *Action: Check the log file of the Cluster Synchronization Service daemon // to verify the state of the service. 29750, 00000, "enable CGS name service event trace" // *Document: NO // *Cause: // *Action: Dump CGS name service tracing 29760, 00000, "instance_number parameter not specified" // *Cause: The init.ora file did not contain a value for the instance_number // which is required to identify this instance to other instances of // the database running on the same cluster // *Action: Assign a value to the instance_number parameter in the init.ora // parameter file 29770, 00000, "global enqueue process %s (OSID %s) is hung for more than %s seconds" // *Cause: The specified process mades no progress within the maximum // allowed time. // *Action: Check the alert file and relevent trace files and // contact Oracle Support Services with the incident information. 29771, 00000, "process %s (OSID %s) blocks %s (OSID %s) for more than %s seconds" // *Cause: The specified process blocked a global enqueue process for // the maximum allowed time. // *Action: Check the alert file and relevent trace files and contact // Oracle Support Services with the incident information. / / 29780 -29789 Reserved for Gpnp Generic modules / 29780, 00000, "unable to connect to GPnP daemon [%s]" // *Cause: Attempt to connect to the GPnP deamon failed with the error // reported. // *Action: Take the corrective action to resolve the error reported. Refer // to GPnP logs and documentation to figure out why the call // failed. 29781, 00000, "invalid GPnP attribute [%s]" // *Document: NO // *Cause: The GPnP attribute specified was not recognized as a valid // attribute. // *Action: Correct the attribute type and retry the operation. 29782, 00000, "GPnP operation failed with error [%s]" // *Document: NO // *Cause: The GPnP operation failed with the specified error. // *Action: Contact Oracle Support Services. 29783, 00000, "GPnP attribute SET failed with error [%s]" // *Cause: Attempt to set the GPnP attribute failed. See the brackets // for the reason. // *Action: Resolve the problem in the included message and retry the request. 29784, 00000, "Attribute update operation not permitted" // *Cause: The update operation for attributes was not permitted because // Cluster Synchronization Services (CSS) was not running on the // host. // *Action: Start Cluster Synchronization Services (CSS) and retry the // operation. 29785, 00000, "GPnP attribute GET failed with error [%s]" // *Cause: Attempt to get the GPnP attribute failed. See the brackets // for the reason. // *Action: Resolve the problem in the included message and retry the request. 29786, 00000, "SIHA attribute GET failed with error [%s]" // *Cause: Attempt to get the SIHA attribute failed. See the brackets // for the reason. // *Action: Resolve the problem in the included message and retry the request. 29787, 00000, "SIHA attribute SET failed with error [%s]" // *Cause: Attempt to set the SIHA attribute failed. See the brackets // for the reason. // *Action: Resolve the problem in the included message and retry the request. 29788, 00000, "Network interface query failed with error [%s]" // *Cause: Attempt to get the network information failed. // See the brackets for the reason. // *Action: Resolve the problem in the included message and retry the request. 29789, 00000, "internal test event" // *Document: NO // *Cause: This is an internal test event. Set only under guidance of // development. // *Action: Follow up with the Oracle Support Services using the traces // generated by this event. / 29790, 00000, "Cannot change user session parameters for a non-user session" // *Cause: An attempt was made to change user session parameters for a // non-user session. // *Action: Execute the operation when connected with a user session // 29791, 00000, "Transactions cannot be replayed" // *Cause: The user attempted to replay a transaction. // *Action: Reconnect and re-execute the transaction. // 29798, 00000, "Dump diagnostics for HA only during internal testing." // *Document: NO // *Cause: // *Action: 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. // NLS_DO_NOT_TRANSLATE[29889,29889] 29889, 00000, "allow a secondary object creation" // *Document: NO // *Cause: For internal use only // *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. 29890,00000, "specified primary operator does not have an index context" // *Cause: The primary operator does not have an index and scan contexts. // *Action: Create the primary operator with a context clause. // NLS_DO_NOT_TRANSLATE[29891,29891] 29891, 00000, "enable debugging in ODCI user-defined routines" // *Document: NO // *Cause: For internal use only // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED FOR SETTING A NEW EVENT FOR // DEBUGGING SUPPORT IN ODCI USER-DEFINED ROUTINES 29892,00000, "indextypes with array DML do not support the given data type" // *Cause: The user specified a REF or a LONG datatype which is not supported // in CREATE/ALTER INDEXTYPE WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE). // *Action: Reissue the CREATE/ALTER INDEXTYPE statement without the REF or // LONG datatype. 29893,00000, "indextypes without column data do not need the given data type" // *Cause: WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE) option and WITHOUT COLUMN // DATA option conflicted in an alter indextype statement // *Action: Reissue the ALTER INDEXTYPE statement without the conflict. 29894, 00000, "base or varray datatype does not exist" // *Cause: One of the base and varray datatypes specified in WITH ARRAY DML // (DATA_TYPE, VARRAY_TYPE) clause could not be found. // *Action: Check to see if the datatype exists and the user has EXECUTE // privilege on this datatype. 29895, 00000, "duplicate base datatype specified" // *Cause : User attempted to add a base datatype to an indextype with ARRAY // DML which is already supported by the indextype // *Action: Remove the duplicate base datatype and retry the command 29896, 00000, "Length of PARAMETER string longer than %s characters" // *Cause : An attempt was made to specify a parameter value that is // longer than the allowed maximum. // *Action: Reduce the parameter value length. 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 // *Cause: For internal use only // *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 29916, 00000, "event for turning on RAW pointer arg to table function" // *Document: NO // *Cause: For internal use only // *Action: Not a user error 29917, 00000, "cannot lock a table which gets its rows from a collection operand" // *Cause: Tables which gets its rows from a collection operand cannot be locked // *Action: Don't lock the table 29918, 00000, "cannot create domain indexes on temporary tables" // *Cause : An attempt was made to create a domain index on a temporary table // *Action: Either create another type of index on the temporary // table or change the table from temporary to a permanent table 29919, 00000, "failed in the execution of the ODCIINDEXUPDPARTMETADATA routine" // *Cause: Failed to successfully execute the ODCIINDEXUPDPARTMETADATA routine. // *Action: Check to see if the routine has been coded correctly. 29920, 00000, "failed in the partition maintenance operation of secondary table" // *Cause: Failed to successfully execute the partition maintenance operation // of a secondary table in system managed domain index. // *Action: Check to see if the partition of a secondary table exists. 29921, 00000, "Ancillary operator not supported with set view query block" // *Cause : Outer view query block contains ancillary operator and view query // block contains union all. // *Action: Define the union-all view query to contain the primary // and ancillary query terms. i.e. have the operators within the view // definition rather than in the query outside the view. 29922, 00000, "Invalid rowid returned by the user-defined query methods" // *Cause: An invalid row identifier was returned by the user-defined query // methods. // *Action: Check the implementation of the indextype methods to make sure // that the index creation and query methods are correct. 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 29937, 00000, "domain index cannot be system-managed" // *Cause: An ASSOCIATE STATISTICS command was issued with a domain index // which is system-managed. // *Action: Check to see if the domain index has been implemented with // system-managed storage tables. To associate statitics with a // system-managed domain index, issue ASSOCIATE STATISTICS command // with the indextype of this domain index. 29938, 00000, "both indextype and statistics type should be system-managed" // *Cause: Either an ASSOCIATE STATISTICS WITH SYSTEM MANAGED STORAGE TABLES // command was issued with an indextype which is not system-managed, // or an ASSOCIATE STATISTICS command was issued with an indextype // which is system-managed. // *Action: Check to see if both indextype and statistics type are implemented // with system-managed storage tables. 29939, 00000, "could not implicitly transform user-managed domain index to system-managed domain index" // *Cause: Implicit validation of a user-managed domain index with a // system-managed indextype failed. // *Action: Issue an ALTER INDEX COMPILE command on the domain 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 29962, 00000, "fatal 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. 29963, 00000, "missing BINDING keyword" // *Cause: Keyword BINDING is expected . // *Action: Specify the BINDING keyword or check the SQL statement. 29964, 00000, "missing ADD or DROP keyword" // *Cause: One of the keywords ADD or DROP is expected. // *Action: Specify the ADD or DROP keyword or check the SQL statement. 29965, 00000, "The specified binding does not exist" // *Cause: The binding specified in the DROP BINDING clause is not a valid // binding for this operator. // *Action: Specify an existing binding for this op in DROP BINDING clause. 29966, 00000, "The only binding of an operator cannot be dropped" // *Cause: This operator only has one binding. It cannot be dropped using // Alter Operator Drop Binding. // *Action: If you wish to drop the entire operator, call Drop Operator. 29967, 00000, "Cannot drop an operator binding with dependent objects" // *Cause: The operator binding that is being dropped has dependent objects. // *Action: Either drop the dependent objects first and then issue the ALTER // OPERATOR DROP BINDING command or specify the FORCE option with // ALTER OPERATOR DROP BINDING. 29968, 00000, "No primary operator bindings found for ancillary binding #%s" // *Cause: At least one ancillary binding of the specified operator could // not be validated because all of its associated primary operator // bindings have been dropped. // *Action: Either drop the ancillary binding whose primary operators are // missing, or drop the entire operator, if this is the only binding. // This binding cannot be re-validated. / /29970 - 29999 Reserved for DB Change notification 29970, 00000, "Specified registration id does not exist" // *Cause: An incorrect regid value was passed to dbms_chnf procedure. // *Action: pass the correct regid value. / 29971, 0000, "Specified table name not found or does not have any registrations" // *Cause: The database could not locate the passed in table name // *Action: CHeck the table name passed in. / 29972, 0000, "user does not have privilege to change/ create registration" // *Cause: User passed in an incorrect or someone else's regid/ handle. // *Action: Check the passed in regid/ reg handle / 29973, 0000, "Unsupported query or operation during change notification registration" // *Cause: The user attempted to register an unsupported query type // or an unsupported operation like a DML/DDL for change notification. // *Action: Please check the statement being executed and refer to the // documentation. / 29974, 0000, "Internal event for PL/SQL debugging" // *Cause: None // *Action: none / 29975, 0000, "Cannot register a query in the middle of an active transaction" // *Cause: User tried to register a query within an uncommitted transction. // *Action: Commit the transaction and retry. / 29976, 0000, "Unsupported query for registration in guaranteed mode" // *Cause: An operator or expression in the query was incompatible // with query registration in the guaranteed granularity mode. // *Action: Check all expressions, clauses and operators in the query and refer // to the documentation for supported query types. // The application can reattempt // the query registration in best effort mode. / 29977, 0000, "Unsupported column type for query registration in guaranteed mode" // *Cause: An attempt was made to register a query with an unsupported // column type or too many columns. // *Action: Examine all column datatypes in the expression and refer // to the documentation for supported query types. // The application can reattempt // the query registration in best effort mode. / 29978, 0000, "Internal event for tracing Inband Notifications" // *Cause: None // *Action: none / 29979, 0000, "Query registration not supported at current compatible setting" // *Cause: An attempt was made to register a query with the database // compatible setting lower than 11. // *Action: Increase the database compatible setting to 11.0.0.0.0 / 29980, 0000, "Internal event for KTG crash recovery" // *Document: NO // *Cause: None // *Action: none / 29981, 0000, "Cannot register query: conflicting DDL in progress" // *Cause: A query registration was attempted while there was a // a concurrent DDL in progress. // *Action: Retry the query registration. / 29982, 0000, "Table type not supported for query registration in guaranteed mode" // *Cause: The user attempted to register a query // involving an unsupported table type. // *Action: Examine all tables in the query registration and refer // to the documentation for supported table types. // The application can reattempt registration in best effort mode. / 29983, 0000, "Unsupported query for Continuous Query Notification" // *Cause: The query cannot be registered for Continuous Query Notification. // *Action: The query has some constructs that make it incompatible // with Continous Query Notification like // synonyms or views. Please check the documentation for // complete list. / 29984, 0000, "Internal event to force CHNF registrations" // *Cause: None // *Action: none / 29985, 0000, "Query Registration is only supported for automatic undo management" // *Cause: User is using manual undo management // *Action: Switch to using automatic undo management / 29986, 0000, "Internal event for CQN to enable slow path ROWID generation" // *Document: NO // *Cause: None // *Action: None / 29987, 0000, "Internal event for validating context in KTG Hash Insert Item" // *Document: NO // *Cause: None // *Action: None / 29988, 0000, "Event to enable blocking on client cache registrations" // *Document: NO // *Cause: None // *Action: None / / 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 was called at places other than the // SELECT list and ORDER BY clause. // // *Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than // the SELECT list and ORDER BY clause. / 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 separator as part of column value" // *Cause: A column value contained the string that the SYS_CONNECT_BY_PATH // function was to use to separate column values. // *Action: Specify another separator for the SYS_CONNECT_BY_PATH function // to use 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. / 30007, 00000, "CONNECT BY ROOT operator is not supported in the START WITH or in the CONNECT BY condition" // *Cause: An attempt was made to use CONNECT BY ROOT operator in the START WITH or in the CONNECT BY condition. // *Action: Remove CONNECT BY ROOT operator from the START WITH or from the CONNECT BY condition. / 30008, 00000, "CONNECT BY clause must reference a PRIOR" // *Cause: A CONNECT BY clause did not include a predicate referencing a // PRIOR so there was no condition connecting a parent row to its // child row. // *Action: Add a reference to a PRIOR in the CONNECT BY clause. / 30009, 0000, "Not enough memory for %s operation" // *Cause: The memory size was not sufficient to process all the levels of the // hierarchy specified by the query. // *Action: In WORKAREA_SIZE_POLICY=AUTO mode, set PGA_AGGREGATE_TARGET to // a reasonably larger value. // Or, in WORKAREA_SIZE_POLICY=MANUAL mode, set SORT_AREA_SIZE to a // reasonably larger value. / 30010, 0000, "Not enough I/O buffers for the sort operation" // *Cause: The sort was unable to allocate enough I/O buffers. // *Action: Increase the amount of memory allowed for the sort or increase // the maximum number of I/O buffers allowed in the system and // retry the query. / / Error numbers 30011-30050 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. 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 or temporary 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, "'Retention' can only specified for undo tablespace" // *Cause: An attempt was made to specify retention for a non-undo tablespace. // *Action: Modify the CREATE TABLESPACE statement. 30045, 00000, "No undo tablespace name specified" // *Cause: If Create Database has the datafile clause, then // undo tablespace name has to be specified, unless using OMF. // *Action: Specify the undo tablespace name. 30046, 00000, "Undo tablespace %s not found in control file." // *Cause: The specified undo tablespace is not present in the control file. // *Action: Modify the CREATE CONTROLFILE statement that created the current // control file to include undo tablespace(s) and reissue the // statement. 30047, 00000, "Internal event for kti tracing" // *Cause: internal use only // *Action: none 30048, 00000, "Internal event for IMU auto-tuning" // *Cause: internal use only // *Action: none 30049, 00000, "Internal event for TA enq tracing" // *Cause: internal use only // *Action: none / 30050, 00000, "Internal event for IMU private buffer leak checks" // *Document: NO // *Cause: internal use only // *Action: none / / 30051 - 30059 Reserved for row versions query feature / 30051, 00000, "VERSIONS clause not allowed here" // *Cause: A VERSIONS clause was specified when it was not allowed. // *Action: Do not use the VERSIONS clause 30052, 00000, "invalid lower limit snapshot expression" // *Cause: The lower limit snapshot expression was below the UNDO_RETENTION // limit. // *Action: Specify a valid lower limit snapshot expression. 30053, 00000, "invalid upper limit snapshot expression" // *Cause: The upper limit snapshot expression is greater than the SQL // statement read snapshot. // *Action: Specify a valid upper limit snapshot expression. 30054, 00000, "invalid upper limit snapshot expression" // *Cause: The upper limit snapshot expression is less than the lower limit // snapshot expression. // *Action: Specify a valid upper limit snapshot expression. 30055, 00000, "NULL snapshot expression not allowed here" // *Cause: The snapshot expression is NULL. // *Action: Specify a non-NULL snapshot expression. / / 30060 - 30069 Reserved for Transaction layer internal tracing / 30060, 00000, "Internal event for RECO tracing" // *Cause: internal use only // *Action: none 30061, 00000, "Internal Event for Savepoint Tracing" // *Cause: internal use only // *Action: none 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. 30066, 00000, "test support - drop rollback segment wait" // *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. 30079, 00000, "cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns" // *Cause: An attempt was made to alter database timezone with // TIMESTAMP WITH LOCAL TIME ZONE column in the database. // *Action: Either do not alter database timezone or first drop all the // TIMESTAMP WITH LOCAL TIME ZONE columns. // 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: // 30090, 00000, "Internal general event for DST patching on TIMESTAMP WITH TIME ZONE data" // *Document: NO // *Cause: N/A // *Action: N/A // Level: // 0x01 - trace loading of TT // 0x02 - trace SQL statement generation // 0x04 - trace RAC execution // 0x08 - trace DBMS_DST procedures // 0x10 - allow to start an upgrade window without opening DB // in UPGRADE mode // 0x20 - simulate a datapump job caller // 0x40 - disable the optimization of using index to find if the // data in a TSTZ column are affected // *Comment: Not for general purpose use. // 30091, 00000, "secondary translation table not loaded" // *Cause: The secondary translation table for DST patching on TSTZ data // was not loaded. // *Action: Load the secondary translation table. // 30092, 00000, "function not allowed at this stage of DST upgrade process" // *Cause: Query included a function that is not allowed in the current // state of DST upgrade process. // *Action: This function is not allowed at the currect stage of DST upgrade. // 30093, 00000, "function not allowed until the database is restarted" // *Cause: Query included a function that is not allowed until the // database is restarted. // *Action: Shut down and restart the database. // 30094, 00000, "failed to find the time zone data file for version %s in $ORACLE_HOME/oracore/zoneinfo" // *Cause: There was no corresponding time zone data file in // $ORACLE_HOME/oracore/zoneinfo for the input time zone version. // *Action: None. // / 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 and OCI configuration. / 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. // 30136, 0000, "Drop-in compatibility is not supported for this application" // *Cause: The current application is statically linked with defopt.o // from an older release, which is incompatible with the current // client shared library. // *Action: 1) Relink the application against the new release of the client // library; or // 2) Relink the application against the older release of the client // library without statically linking defopt.o. / / 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. / / 30204, 00000, "buffer is not large enougth" // *Cause: The destination buffer is not large enough for storing // converted data. / // *Action: Check the size of the destination buffer. / / 30205, 00000, "invalid Character set" // *Cause: The specified character set is invalid. / // *Action: Check if the character set ID is valid. / / / 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: Multiple JOIN KEY clauses were 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, a non-deterministic // date format token RR, 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, "table %s.MV_CAPABILITIES_TABLE not found" // *Cause: You have used the DBMS_MVIEW.EXPLAIN_MVIEW() 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_MVIEW() 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. / 30382, 00000, "DROP MATERIALIZED VIEW %s.%s operation is not complete" // *Cause: The drop materialized view operation got an unexpected error while // dropping summary object. // *Action: Issue the drop materialized view command again / 30383, 00000, "specified dimension level does not exist in the attribute" // *Cause: An attribute level was encountered that is not defined within the // attribute. // // *Action: Check the attribute level name spelling. / 30384, 00000, "specified column name does not exist in the attribute" // *Cause: A column was encountered that is not defined within the attribute. // // *Action: Check the attribute column name spelling. / 30385, 00000, "specified attribute relationship ('%s' determines '%s') exists" // *Cause: The specified attribute relationship has already been declared // in one of the attribute clauses // // *Action: Remove the duplicate attribute relationship / 30386, 00000, "invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE" // *Cause: Either the source or destination statement is NULL // *Action: Verify both source and destination statement are valid / 30387, 00000, "invalid rewrite mode for REWRITE_EQUIVALENCE API" // *Cause: The specified rewrite mode is not supported by REWRITE_EQUIVALENCE API // *Action: Verify the rewrite mode is supported by REWRITE_EQUIVALENCE API / 30388, 00000, "name of the rewrite equivalence is not specified" // *Cause: The name of the rewrite equivalence is NULL // *Action: Input a valid rewrite equivalence name / 30389, 00000, "the source statement is not compatible with the destination statement" // *Cause: The SELECT clause of the source statement is not compatible with // the SELECT clause of the destination statement // *Action: Verify both SELECT clauses are compatible with each other such as // numbers of SELECT list items are the same and the datatype for // each SELECT list item is compatible / 30390, 00000, "the source statement is not equivalent to the destination statement" // *Cause: the set of rows returned by the source SQL text is not the same as // the set of rows returned by the destination SQL text // *Action: Make sure both source and destination statement return the same number // of rows / 30391, 00000, "the specified rewrite equivalence does not exist" // *Cause: the specified rewrite equivalence does not exist // *Action: Verify the rewrite equivalence has been created / 30392, 00000, "the checksum analysis for the rewrite equivalence failed" // *Cause: the given checksum does not match with that generated from the // source and destination statements. // *Action: Verify the create safe rewrite equivalence statement to see if it // has been modified. / 30393, 00000, "a query block in the statement did not rewrite" // *Cause: A query block with a REWRITE_OR_ERROR hint did not rewrite // *Action: Verify the rewrite equivalence has been created / 30394, 00000, "source statement identical to the destination statement" // *Cause: The source statement was identical to the destination statement // *Action: Make sure both source and destination statements are not identical / / 30397, 00000, "multiple JOIN KEY clauses specified for the same child level" // *Cause: Multiple JOIN KEY clauses were specified for a given child // level in a dimension hierarchy. // // *Action: Eliminate the redundant JOIN KEY clauses. / / 30398, 00000, "illegal JOIN KEY clause" // *Cause: A JOIN KEY clause was specified that did not conform to certain // requirements. A JOIN KEY clause connecting a child level with its // non-immediate ancestor level is allowed only when that child level // and its ancestor level satisfy the following conditions: // 1. The immediate parent of the child level must be a skip level. // 2. The child level cannot be a skip level. // 3. The ancestor level must be a non-skip level. // 4. The ancestor level must be the nearest non-skip level to // the child level in the hierarchy. // // *Action: Modify the JOIN KEY clause so that it satisfies the conditions // mentioned above. / / 30399, 00000, "a skip level must have at least one column that allows NULL values" // *Cause: A SKIP clause cannot be specified with a level when all of the // columns that make up the level have NOT NULL constraints. // // *Action: Drop the SKIP clause. / / 30400, 00000, "identical JOIN KEY clauses" // *Cause: Two JOIN KEY clauses with identical child keys and parent levels // were specified. // // *Action: Eliminate the redundant JOIN KEY clause. / / 30401, 00000, "JOIN KEY columns must be non-null" // *Cause: The dimension statement failed because the column(s) in the JOIN // KEY clause permitted NULL values. The JOIN KEY columns are related // to the columns of the dimension's skip levels in one or both of the // following ways: // 1. A skip level is defined over one or more of the JOIN KEY // columns. // 2. The attribute clauses of a skip level determine one or more of // the JOIN KEY columns. // // *Action: Modify the JOIN KEY columns so that they do not allow NULL // values. 30402, 00000, "access advisor debug/testing trace" // *Document: NO // *Cause: // *Action: access advisor debug/testing / / 30403, 00000, "Daylight Saving Time (DST) upgrade in progress" // *Cause: Daylight Saving Time upgrade was in progress on a table // in the materialized view. // *Action: Wait until all tables in the materialized view have gone // through DST upgrade. / / 30404, 00000, "general event for summary" // *Document: NO // *Cause: N/A // *Action: This internal event is used to enable various actions // associated with summary. The event level is interpreted // as a bitmap of actions to enable. // // *Comment: Not for general purpose use. // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 enable acquiring Rewrite enqueue / / / Error Numbers 30420 - 30479 are reserved for Summary Advisor and / Refresh Packages. These are raised by calling / dbms_sys_error.raise_system_error. / 30420, 00000, "%s is not a valid identifier" // *Cause: All identifiers used in the DBMS_OLAP package must have at most 30 // characters, and must start with a letter that is followed // by any combination of letters, numerals, and the signs // '$', '_', and '#'. Other characters cannot be used in identifiers. // The rules for DBMS_OLAP identifiers are the same as for PL/SQL // identifiers. // *Action: Rename object to conform to the DBMS_OLAP naming rules and // try again. / 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 / 30467, 00000, "internal data for filter 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_FILTER subprogram to remove // the inconsistent data from summary advisor's internal tables / 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. / 30516, 00000, "database role change triggers cannot have BEFORE type" // *Cause: An attempt was made to create a trigger that fires before // the role change completed. This type of trigger is not supported. // *Action: Do not attempt to create a trigger that fires before the role // change completes. / / 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: If the function is deterministic, mark it DETERMINISTIC. If it // is not deterministic (it depends on package state, database state, // current time, or anything other than the function inputs) then // do not create the index. The values returned by a deterministic // function should not change even when the function is rewritten or // recompiled. / 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, "either functional or bitmap join index is defined on the column to be modified" // *Cause : An ALTER TABLE MODIFY COLUMN was issued on a column on which // either a functional index or bitmap join index exists. // *Action: Drop the functional or bitmap join 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 clause not allowed" // *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, CONNECT BY, or START WITH" // *Cause: An attempt was made to reference (+) in select-list, CONNECT BY // clause, or START WITH clause. // *Action: Do not use the operator in select-list, CONNECT BY clause, or // START WITH clause. 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 30577, 00000, "SAMPLE group size must be in the range [1,UB4MAXVAL]" // *Cause: // *Action: 30579, 00000, "enables order by PRIMARY KEY for base table scan during create index" // *Document: NO // *Cause: // *Action: Set this event to enable order by PRIMARY KEY for base table // scan during creation of Text index. // *Comment: This event is primarily used for internal tests that require // consistent docid ordering. Turning on this event can // result in poor create index performance. / / / / / / 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: 30627, 00000, "Oracle event to pass temp lobs by ref from sql" // *Cause: // *Action: set this event only under the supervision of Oracle development 30628, 00000, "Oracle event to turn off passing temp lobs by ref" // *Cause: // *Action: set this event only under the supervision of Oracle development / / / 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! / 30659,0000, "too many locations specified for external table" // *Cause: An attempt was made to create an External Organized table with // more than the maximum allowable (32767) locations specified. // *Action: Don't do that, use fewer location clauses. Either consider // concatenating the input files, or, creating two external tables // with the input files split between them. / / / 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 allowed // connections varies 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 that 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. 30685, 00000, "package version is not compatible with Oracle version" // *Cause: The installed version of the package from which this error // is raised is not compatible with this release of Oracle. // *Action: Install a compatible version of the package's spec and body. 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, // configure a dispatcher for protocol=tcp. To route these // particular connections through a particular set of dispatchers, // you can specify presentation=kgas. However, 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 required. 30688, 00000, "maximum program calling depth exceeded" // *Cause: Your program contains a set of calls that are // 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: Restructure your program so as to not 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. 30690, 00000, "timeout occurred while registering a TCP/IP connection for data traffic detection" // *Cause: A timeout occurred while registering a TCP/IP connection for // data traffic detection. // *Action: Retry the operation later. 30691, 00000, "failed to allocate system resources while registering a TCP/IP connection for data traffic detection" // *Cause: System resources ran out while registering a TCP/IP // connection for data traffic detection. // *Action: Retry the operation later. 30695, 00000, "JDWP message format problem" // *Cause: A message passed from one software subcomponent to another // using the JDWP protocol appears invalidly formatted. // *Action: This is an internal error. Contact ORACLE Support Services. 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. 30758, 00000, "cannot specify local on a non-partitioned table" // *Cause: The user specified local or global for a nested table storage // parameter while the base table is non-partitioned. // *Action: None 30759, 00000, "nested table cannot be partitioned for a composite partitioned base table" // *Cause: The user specifed local or nested table parameters inside // partition clause for a composite partitioned table. // *Action: Issue the DDL without nested table partition clauses for composite // partitioned table. / / 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. 30772, 00000, "opaque types do not have default constructors" // *Cause: Constructor invocation did not succeed, since no user-defined // constructors were defined for the opaque type, and since opaque // types do not have default constructors. // *Action: Add user-defined constructors to opaque type, or specify a // member or static method for the opaque type. 30773, 00000, "opaque types do not have default constructors" // *Cause: Constructor invocation did not succeed, since no user-defined // constructors were defined for the opaque type, and since opaque // types do not have default constructors. // *Action: Add user-defined constructors to opaque type, or specify a // member or static method for the opaque type. 30774, 00000, "Library \"%s\" was erroneously defined as a trusted library for opaque types" // *Cause: User has defined some library as trusted library for opaque types. // *Action: Trusted libraries for opaque types can only be defined in internal // code. // / / / Error Numbers 30926 - 30930 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. / 30930, 00000, "NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn" // *Cause: CONNECT_BY_ISCYCLE was specifed in a query which does not // have the NOCYCLE keyword. // *Action: Remove CONNECT_BY_ISCYCLE or add NOCYCLE. / / Error Numbers 30931 - 31200 are reserved for Project XDB (XML Support) / / / Errors 30931 - 30979 for XMLType & schema processing / 30931, 00000, "Element '%s' cannot contain mixed text" // *Cause: XML elements must be declared mixed to contain multiple text nodes // *Action: Declare this element type as mixed in its schema 30932, 00000, "Reference node '%s' not contained in specified parent node '%s'" // *Cause: When using a reference node, it must have the specified parent // node // *Action: Use a node in the specified parent as the reference 30933, 00000, "Element '%s' may not appear at this point within parent '%s'" // *Cause: The ordering specified by the content model of the parent does // not allow for this element to occur at this position. // *Action: Reorder the child elements to conform with the content model // of the parent element 30934, 00000, "'%s' (%s node) cannot be inserted in parent '%s' (%s node)" // *Cause: The schema does not allow a child node of this type to be inserted // into a parent node of this type. For example, only element // nodes may only be inserted into a document // *Action: Insert only child nodes that make sense for this node type 30935, 00000, "XML maxoccurs value (%s) exceeded" // *Cause: An attempt was made to insert more than maxoccurs // values into a schema-based XML document. // *Action: Do not insert more than maxoccurs values into the document. 30936, 00000, "Maximum number (%s) of '%s' XML node elements exceeded" // *Cause: An attempt was made to insert more than the allowed number // of elements (specified by the maxoccurs facet) into an XML // document. // *Action: Do not attempt to add more than the maximum number of elements // to XML documents. 30937, 00000, "No schema definition for '%s' (namespace '%s') in parent '%s'" // *Cause: The schema definition for the parent node being processed does // not allow for the specified child node in its content model. // Note that any typecasting via xsi:type must occur before the // schema definitions for the new type can be used. // *Action: Only insert elements and attributes declared in the schema. // Check to make sure that xsi:type (if used) is specified first. 30938, 00000, "No prefix defined for namespace '%s' (particle %s)" // *Cause: An XML namespace mapping (xmlns:=) must // be defined for each particle (element or attribute) stored in // an schema-constrained XMLType document. // *Action: Add an xmlns attribute definition (attribute name="xmlns:prefix" // and value="namespace URL") to the current XMLType document. // The safest place to add this attribute is in the root node of // the document to ensure that the mapping will be in scope. 30939, 00000, "Order violation: Element '%s' may not follow element '%s'" // *Cause: The XML schema specifies a content model that is sequential, // where the order of nodes in the instance must follow the order // specified by the schema, and this instance relies on the schema // validity to avoid maintaining instance order information // *Action: Insert elements only in the order specified in the schema 30940, 00000, "Cannot resolve prefix '%s' for QName node '%s'" // *Cause: An attempt was made to store a QName value without having a // valid namespace in scope for that prefix. // *Action: Declare the namespace for the prefix used 30941, 00000, "Cannot specify empty URI for non-default namespace '%s'" // *Cause: An attempt was made to insert a namespace declaration for // a non-default namespace using an empty URI string. // *Action: Specify a non-empty URI for namespace declarations other than // the default namespace. //////// Errors 30942 to 30950 reserved for XML Schema Evolution 30942, 00000, "XML Schema Evolution error for schema '%s' table %s column '%s'" // *Cause: The given XMLType table/column which conforms to the given schema // had errors during evolution. For more information, see the more // specific error below this one // *Action: Based on the schema, table and column information in this error // and the more specific error below, take corrective action 30943, 00000, "XML Schema '%s' is dependent on XML schema '%s'" // *Cause: Not all dependent schemas were specified and/or the schemas were // not specified in dependency order, i.e., if schema S1 is dependent // on schema S, S must appear before S1. // *Action: Include the previously unspecified schema in the list of schemas // and/or correct the order in which the schemas are specified. Then // retry the operation. 30944, 00000, "Error during rollback for XML schema '%s' table %s column '%s'" // *Cause: The given XMLType table/column which conforms to the given schema // had errors during a rollback of XML schema evolution. For more // information, see the more specific error below this one // *Action: Based on the schema, table and column information in this error // and the more specific error below, take corrective action 30945, 00000, "Could not create mapping table '%s'" // *Cause: A mapping table could not be created during XML schema evolution. // For more information, see the more specific error below this one // *Action: Ensure that a table with the given name does not exist and retry // the operation 30946, 00000, "XML Schema Evolution warning: temporary tables not cleaned up" // *Cause: An error occurred after the schema was evolved while cleaning up // temporary tables. The schema evolution was successful // *Action: If the user needs to remove the temporary tables, use the mapping // table to get the temporary table names and drop them. 30947, 00000, "Dependent table '%s' of XML schema '%s' is version-enabled" // *Cause: An XMLType table that is dependent on an XML schema being evolved // is version-enabled. // *Action: Disable versioning on the XMLType table 30948, 00000, "Illegal in-place XML schema evolution operation: %s" // *Cause: An attempt was made to make an XML schema change that is not // permitted through in-place XML schema evolution. // *Action: Ensure that the XML schema changes specified in the XMLDiff // argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted. /////// End of XML Schema Evolution errors (30942 to 30950 reserved) 30951, 00000, "Element or attribute at Xpath %s exceeds maximum length" // *Cause: An attempt was made to insert a node of length exceeding the // maximum length (specified by the maxLength facet) into // an XML document. // *Action: Do not attempt to add a node exceeding the maximum length // to XML documents. 30952, 00000, "illegal configuration of HTTP/HTTPS in xdbconfig.xml" // *Cause: An attempt was made to update xdbconfig.xml when either // 1) a value was specified for http2-port but not for // http2-protocol (or vice versa), OR // 2) http-port and http2-port were set to the same value. // *Action: Specify values for both elements http2-port and http2-protocol, // AND set different values for http-port and http2-port. 30953, 00000, "XML minoccurs value (%s) violated" // *Cause: An attempt was made to delete more than the required minimum number // of elements (specified by the minoccurs facet) from an XML // document. // *Action: Do not attempt to delete more than the required minimum // number of elements that must be present from the XML document. 30954, 00000, "char %s is invalid in %s" // *Cause: An invalid XML character was found. // *Action: Use only characters allowed by the XML specification. // //////// Errors 30955 to 30989 reserved for XML Index 30955, 00000, "The XML Index does not exist or is not asynchronous" // *Cause: An attempt was made to synchronize a nonexistent XML Index // or a synchronous XML Index. // *Action: Create the XML Index in asynchronous mode. 30956, 00000, "invalid option for XML Index" // *Cause: Unexpected error. // *Action: File a bug. 30957, 00000, "cannot downgrade because there are XML indexes" // *Cause: An attempt was made to downgrade a database that has XML indexes. // *Action: Drop all XML indexes before attempting the downgrade. 30958, 00000, "operation directly on the Pending Table is disallowed" // *Cause: An illegal operation was attempted on secondary objects of an // XML Index. // *Action: Try appropriate operation on the XML Index. 30959, 00000, "The indexed column is not stored in CLOB." // *Cause: An attempt was made to create an XML Index on an OR-XMLType column. // *Action: Re-create the XML Index on a CLOB-XMLType column. 30960, 00000, "The entity is neither an XPATH nor a NAMESPACE." // *Cause: The given string had invalid syntax. // *Action: Check the syntax for XPATH and NAMESPACE. 30961, 00000, "internal SQL statement is too long" // *Cause: unexpected internal error // *Action: File a bug and provide the test case. 30962, 00000, "inconsistent ODCI input arguments" // *Cause: unexpected internal error // *Action: File a bug and provide the test case. 30963, 00000, "The indexed column is not of XMLType." // *Cause: An attempt was made to create an XML Index on a non-XMLType column. // *Action: Re-create the XML Index on an XMLType column. 30964, 00000, "The XML Index was not usable." // *Cause: The domain index for XML was not created properly. The Path Table is missing. // *Action: Drop and re-create the XML Index. 30965, 00000, "fragment does not fit into the VARCHAR2 VALUE column" // *Cause: The fragment size exceeded the max size. // *Action: Re-create the XML Index with values stored in CLOB. 30966, 00000, "error detected in the XML Index layer" // *Cause: Unexpected error. // *Action: File a bug. 30967, 00000, "operation directly on the Path Table is disallowed" // *Cause: illegal operation on secondary objects of a domain index // *Action: Try appropriate operation on the domain index. 30968, 00000, "invalid XPATH or NAMESPACE option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30969, 00000, "invalid syntax for PARAMETERS" // *Cause: An attempt was made to specify an invalid option. // *Action: Check and use valid options. 30970, 00000, "option not supported for XML Index" // *Cause: An attempt was made to specify an invalid option. // *Action: Check and use valid options. 30971, 00000, "illegal operation on the Path Table" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate command on the XML Index. 30972, 00000, "invalid ALTER INDEX option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30973, 00000, "invalid Path Table option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30974, 00000, "invalid Path Id Index option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30975, 00000, "invalid Order Key Index option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30976, 00000, "invalid Parent Order Key Index option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30977, 00000, "invalid Value Index option for XML Index" // *Cause: An attempt was made to use an unsupported option. // *Action: Use the appropriate option. 30978, 00000, "The XML Index is not locally partitioned." // *Cause: An attempt was made to create a global partitioned XML Index. // *Action: Do not attempt to create global partitioned XML Index // or to maintain a non-local partitioned XML Index. 30979, 00000, "Partitioned XML Index not yet supported." // *Cause: An attempt was made to create a partitioned XML Index. // *Action: Do not attempt to create partitioned XML Index. 30980, 00000, "Invalid Input." // *Cause: The input to the function is not valid. // *Action: Make sure the input is valid (both syntactically as well as semantically). 30981, 00000, "Internal event to configure Compact XML / Streaming XPath" // *Cause: N/A // *Action: Do not document. 30982, 00000, "Invalid option for a partition of an XML Index" // *Cause: An invalid option was specified at the partition level. // *Action: Remove the invalid option. 30983, 00000, "Maximum order key depth exceeded" // *Cause: The document could not be indexed because its nesting depth was // more than that allowed by XML Index. // *Action: Remove the offending document. 30984, 00000, "The XMLType column has to be declared as virtual" // *Cause: The XMLType column was not declared as virtual when creating // a structured XMLIndex. // *Action: The XMLType column has to be declared as virtual // when creating a structured XMLIndex. 30985, 00000, "The virtual XMLType column for chaining is missing" // *Cause: The virtual XMLType column for chaining was missing when creating // a structured XML index. // *Action: A virtual XMLType column for chaining has to be specified // when creating a structured XML Index. 30986, 00000, "XML Index with more than one virtual column is disallowed" // *Cause: An attempt was made to create an XML Index with more than one // virtual column. // *Action: Create only one virtual column. 30987, 00000, "XML Index on XML DB repository does not exist" // *Cause: An attempt was made to operate on a non-existent XML Index // on XML DB repository. // *Action: First create the index using // DBMS_XDB_ADMIN.CREATEREPOSITORYXMLINDEX. Try the operation again. 30988, 00000, "Metadata of XML Index corrupted" // *Cause: An attempt to locate the XML Index failed. // *Action: Contact Oracle Support Services. 30989, 00000, "XML Index on an Index Organized Table is not yet supported" // *Cause: XML Index supported only on Heap Organized Table. // *Action: Contact Oracle Support Services. /////// End of XML Index (30955 to 30989 reserved) 30990, 00000, "insufficient privileges to change owner of resource %s" // *Cause: An attempt was made to change the field of an // XML DB resource without sufficient privileges to do so. // *Action: Switch to SYS before performing the ownership change, or have // the intended recipient of the resource perform the transfer. 30991, 00000, "cannot use DOM to add special attribute to schema-based parent" // *Cause: An attempt was made to add or remove an xsi:schemaLocation, // xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute // to or from a schema-based XML node using DOM. // *Action: Use the updateXML operator instead of DOM. 30992, 00000, "error occurred at Xpath %s" // *Cause: // *Action: See the following error and take appropriate action. 30993, 00000, "complex type %s is not referred by any global element" // *Cause: // *Action: Add a dummy global element to the schema that refers to // the complex type. 30994, 00000, "Invalid argument for DOM stream" // *Cause: Either a null or a nonleaf node was passed. // *Action: Use a combination of DOM API and DOM streams to produce // desired effect. 30995, 00000, "DOM streams operations cannot be performed on null/invalid node" // *Cause: The node is NULL or inexistent // *Action: Check the input parameters. 30996, 00000, "Streams operations over non-existent stream" // *Cause: The stream passed is NULL or invalid. // *Action: Check the input parameters. 30997, 00000, "XSL processing of XML failed with error LPX-%s" // *Cause: An LPX routine (XML/XSL processing) returned an error // while tranforming an XML doc. // *Action: Look up the LPX error and follow its corrective action. 30998, 00000, "transformation error: %s" // *Cause: Error occurred while transforming an XML doc with an XSL // style sheet. // *Action: Contact Oracle Support Services. 30999, 00000, "XML context creation failed while %s" // *Cause: Error occurred while creating XML context. // *Action: Contact Oracle Support Services. 31000, 00000, "Resource '%s' is not an XDB schema document" // *Cause: The given schema URL does not refer to a registered XDB schema // *Action: Make sure the specified schema has been registered in XDB 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, "Length %s of the BLOB in XDB$H_INDEX is below the minimum %s" // *Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must // have a certain minimum length without being chained. // The calculated length of the LOB was less than the stated minimum. // *Action: Set the value of the init.ora parameter db_block_size // to at least 2K. For XDB to run at its fastest, set // db_block_size to 8K. 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, "LPX context creation failed while %s" // *Cause: Error occurred while creating LPX context because of an unexpected // NULL value. // *Action: Contact Oracle Support Services. 31009, 00000, "Access denied for property %s" // *Cause: An attempt was made to access a property you don't have access to // *Action: Check the ACL to see what privileges you have for this property 31010, 00000, "XML element index %s exceeds maximum insertion index %s" // *Cause: An attempt was made to insert an XML element at an // invalid index location in the node. // *Action: Choose a new index that falls within the allowed range. 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. 31014, 00000, "Attempted to delete the root container" // *Cause: An attempt was made to delete the root container in the // hierarchical index. // *Action: Do not delete the root container. 31015, 00000, "Attempted to insert entry without name" // *Cause: An attempt was made to insert an entry into the hierarchical // resolver without a child name. // *Action: Supply a child name and try inserting again. 31016, 00000, "Attempted to delete entry without name" // *Cause: An attempt was made to delete an entry from the hierarchical // resolver without a child name. // *Action: Supply a child name and try deleting again. 31017, 00000, "Error generating unique OID for XML document" // *Cause: An error occurred while generating a globally unique OID // for storing an XML document. // *Action: 31018, 00000, "Error deleting XML document" // *Cause: The XMLType object pointed to by the given REF could not // be deleted because either the REF was invalid or it // pointed to a non-existent table. // *Action: Either use FORCE deletion or supply a valid REF. 31019, 00000, "Recursive deletion snapshot too old for %s/%s" // *Cause: Changes were made to the structure of a directory while it // was being recursively deleted. // *Action: Try deleting the directory again. 31020, 00000, "The operation is not allowed, Reason: %s" // *Cause: The operation attempted is not allowed // *Action: See reason and change to a valid operation. 31021, 00000, "Element definition not found" // *Cause: The element definition was not found. // *Action: Supply the definition for the element or use a defined element. 31022, 00000, "Element not found" // *Cause: The element was not found. // *Action: Make sure the specified element exists. 31023, 00000, "Index size error" // *Cause: The index is greater than the allowed value. // *Action: Make sure the index is less than allowed value. 31024, 00000, "Parser initialization failed with LPX-%s error\nwhile %s" // *Cause: Error occurred while initializing a parser. // *Action: Contact Oracle Support Services. 31025, 00000, "Invalid document element" // *Cause: An attempt was made to replace the data at an invalid // index number in the XML document // *Action: Supply a correct occurrence number and try again. 31026, 00000, "unable to allocate additional memory while \n%s" // *Cause: A dynamic memory allocation failure occurred. // *Action: Report this problem to a database administrator. 31027, 00000, "Path name or handle %s does not point to a resource" // *Cause: An attempt was made to retrieve a resource based on // a path name or resource handle that points to an entity // other than a resource. // *Action: Do not attempt to retrieve a resource based on that path // name or resource handle. 31028, 00000, "Resource metadata length %s exceeded maximum length %s" // *Cause: An attempt was made to insert resource metadata that exceeded // the maximum length of that type of metadata. // *Action: Keep resource metadata within its allowed length. 31029, 00000, "Cannot bind to unsaved resource" // *Cause: An attempt was made to bind to a resource that had not // been saved to disk. // *Action: Bind only to saved resources. 31030, 00000, "Unable to retrieve XML document" // *Cause: The resource had an invalid (dangling) REF to an XML document. // *Action: Rebind the resource using a valid XMLType REF. 31031, 00000, "cannot create context to parse an XPath\n%s" // *Cause: Error occurred while parsing an XPath. // *Action: Contact Oracle Support Services. 31032, 00000, "XML parsing failed with error LPX-%s\nwhile %s" // *Cause: An LPX routine returned an error while transforming an // XML doc. // *Action: Look up the LPX error and follow its corrective action. 31033, 00000, "Requested number of XML children %s exceeds maximum %s" // *Cause: An attempt was made to add more than the maximum number of // allowable children in an XML element. // *Action: Redefine the schema to allow breaking up of the children // among siblings. 31034, 00000, "invalid node set encountered while executing %s" // *Cause: The given node set was either NULL or has an invalid type associated // with it. // *Action: Contact Oracle Support Services. 31035, 00000, "Could not bind locked resource to path %s/%s" // *Cause: An attempt was made to bind an existing resource to a new // location in the hierarchy, but a lock could not be obtained // on the resource. // *Action: Commit or roll back the transaction that has the lock on the // resource. 31036, 00000, "XSL processing context initialization failed" // *Cause: A error occurred while creating a XSL context. // *Action: Contact Oracle Support Services. 31037, 00000, "Invalid XML attribute name %s" // *Cause: The attribute name in the XML document did not match anything in // the associated schema. // *Action: Supply only schema-defined or XML standard attributes. 31038, 00000, "Invalid %s value: \"%s\"" // *Cause: The text in the XML document did not represent a valid // value given the datatype and other constraints in the schema. // *Action: Ensure that the specified value in XML documents is valid // with respect to the datatype and other constraints in the schema. 31039, 00000, "XML namespace length %s exceeds maximum %s" // *Cause: The length of the disk-formatted XML namespace exceeded the // maximum. // *Action: Keep XML namespace declarations below the maximum length. 31040, 00000, "Property %s: XML type (%s) not compatible with internal memory type (%s)" // *Cause: The XML datatype given is inconsistent with the database // datatype, and a conversion cannot be made. // *Action: This is an internal error, generally resulting from corruption // of the compiled XML schema. Re-register schemas, or contact // Oracle support. // 31041, 00000, "Property %s: Memory type (%s) not compatible with database type (%s)" // *Cause: The memory type associated with this property is mapped to // an incompatible database type, and a conversion cannot be made. // *Action: This is an internal error, generally resulting from corruption // of the compiled XML schema. Re-register schemas, or contact // Oracle support. // 31042, 00000, "Too many properties in type '%s'" // *Cause: The type can only have the same number of properties (elements // and attributes) as a table can have columns. // *Action: Modify the XML schema to move properties into subelements that // are not inlined. // 31043, 00000, "Element '%s' not globally defined in schema '%s'" // *Cause: The specified element name has not been defined at the top level // of the XML schema (i.e. globally). Elements must be defined // globally to be the root of an XMLType object. // *Action: Check the XML schema definition to make sure the specified // element name has been defined at the top level. 31044, 00000, "Top-level prefix length %s exceeds maximum %s" // *Cause: An attempt was made to save to disk a top-level XML namespace // prefix whose length exceeded the maximum. // *Action: Do not define XML namespace prefixes that exceed the maximum // length. 31045, 00000, "Cannot store more than %s extras outside the root XML node" // *Cause: An attempt was made to store more than the maximum number of // XML extras (e.g. comments and processing instructions) // either before or after the document's root node. // *Action: Keep the number of extras outside the root node below // the maximum. 31046, 00000, "Incorrect argument(s) specified in the operator" // *Cause: One or more of the arguments specified in the operator in the // query are incorrect // *Action: Correct the arguments specified in the operator // 31047, 00000, "Could not retrieve resource data at path %s" // *Cause: An error occurred while retrieving the contents and/or metadata // of a resource. // *Action: Contact Oracle customer support. 31048, 00000, "Unsaved resources cannot be updated" // *Cause: An attempt was made to update a resource that was never saved // to disk. // *Action: Perform a resource insertion instead. 31049, 00000, "Internal event to turn off direct path loading of XML" // *Cause: N/A // *Action: Do not document. 31050, 00000, "Access denied" // *Cause: The requested access privileges have not been granted to the // current user. User must be granted privileges prior to // resource access. // *Action: Check the set of requested access privileges to make sure that // they are included in the set of access privilges granted to // the user. // 31051, 00000, "Requested access privileges not supported" // *Cause: The requested access privileges are not supported for the // specified resource. // *Action: Ensure that the set of requested access privileges are valid // access privileges for the specified resource. // 31052, 00000, "Cannot delete ACL with other references" // *Cause: The requested deletion of an ACL resource cannot proceed. // The ACL is in use by other resources. // *Action: Remove the resources that are making reference to the ACL // in question and try again. // 31053, 00000, "The value of the depth argument in the operator cannot be negative" // *Cause: The value of the depth argument passed to the primary operator // is not a positive integer // *Action: Pass a positive value of the depth argument // 31054, 00000, "The %s operator cannot have an ancillary operator " // *Cause: An ancillary operator was used with an operator which does not // does not support ancillary operators // *Action: Remove the ancillary operator in the query // 31055, 00000, "A null XMLType element cannot be inserted into RESOURCE_VIEW" // *Cause: The element which is being inserted into the RESOURCE_VIEW is // NULL // *Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW // 31056, 00000, "The document being inserted does not conform to %s" // *Cause: The XMLType element being inserted into the RESOURCE_VIEW does // not conform to the specified Schema // *Action: Insert an element which conforms to the specified Schema // 31057, 00000, "Display Name of the element being inserted is null" // *Cause: The Display Name of the element which is being inserted into the // RESOURCE_VIEW is null // *Action: Specify the Display Name and insert the element into RESOURCE_VIEW // 31058, 00000, "cannot modify read-only XOBs" // *Cause: Read-Only XOBs cannot be modified. // *Action: Use only read operations on such a XOB. // 31059, 00000, "Cannot insert root XML document node if it already exists" // *Cause: An attempt was made to insert a root node into an XML // document that already had a root node. // *Action: Call the appropriate replace function to replace the node // instead of inserting it anew. 31060, 00000, "Resource at path %s could not be deleted" // *Cause: An error occurred while deleting the named resource. The // specific error can be found one lower on the error stack. // *Action: Look at the next error on the stack and take approprate action. 31061, 00000, "XDB error: %s" // *Cause: The specified error occurred in XDB. // *Action: Correct the error or contact Oracle Support Services. 31062, 00000, "Cannot delete an unsaved resource" // *Cause: An attempt was made to delete a resource that had not // been saved to disk. // *Action: Delete only saved resources. 31063, 00000, "XPath compilation failed: %s.\n%s" // *Cause: XPath compilation failed for specified reason. // *Action: Contact Oracle Support Services. 31064, 00000, "Cannot instantiate abstract element or property [%s]" // *Cause: An attempt was made instantiate an abstract element. // *Action: Use only read operations on such elements. 31065, 00000, "Cannot modify read-only property [%s]" // *Cause: An attempt was made to modify an immutable XML node. // *Action: Use only read operations on such properties. 31066, 00000, "Insertion of %s into %s creates a cycle" // *Cause: An attempt was made to insert a link into the XDB hierarchy // that would create a cycle in the tree. // *Action: Ensure that links to existing resources do not cause cycles. 31067, 00000, "XML nodes must be updated with valid nodes and of the same type" // *Cause: An attempt was made to use updateXML to update an XML // node with a node of another type. // *Action: Ensure that the node specified by the XPath matches the type of // new data provided. 31068, 00000, "updateXML expected data format [%s] instead of [%s]" // *Cause: An attempt was made to use updateXML to update data // with a node of the incorrect type. Text and attribute // nodes must be updated with string data, whereas element // nodes must be updated with XMLType data. // *Action: Use CREATEXML or getStringVal to coerce the new data to the // proper format. 31069, 00000, "Cannot apply typed changes to non-schema-based XMLType nodes" // *Cause: An attempt was made to insert, delete, or update a // non-schema-based XMLType node using an XML schema definition. // *Action: Make changes to non-typed nodes only by referencing their tag // names. 31070, 00000, "Invalid database user ID %s" // *Cause: An attempt was made set an invalid user ID into an XDB // resource metadata property. // *Action: Verify the validity of the user ID and try again. 31071, 00000, "Invalid database username or GUID %s" // *Cause: An attempt was made to set an invalid username or GUID // into an XDB resource metadata property. // *Action: Verify the validity of the username or GUID and try again. 31072, 00000, "Too many child nodes in XMLType fragment for updateXML" // *Cause: An attempt was made to pass an XMLType fragment with multiple // children as new data for the updateXML operator. // *Action: Extract the desired child from the XMLType before passing // it to updateXML as the desired new XML node. 31073, 00000, "Resource not retrieved using path name" // *Cause: An attempt was made to access the path name of a resource // that was either never saved to disk or was loaded using // a method other than with its path name. // *Action: Perform path name operations only on resources obtained using // a path name. 31074, 00000, "XML comment length %s exceeds maximum %s" // *Cause: The length of the disk-formatted XML comment exceeded the // maximum. // *Action: Keep outer XML comments declarations below the maximum length. //////// 31075 - 31099 reserved for XML Schema Compiler 31075, 00000, "invalid %s declaration in XML Schema" // *Cause: The XML schema contains an invalid declaration identified // by the message. // *Action: Fix the identified error and try again. // 31076, 00000, "required attribute \"%s\" not specified" // *Cause: The XML schema does not specify a required attribute. // *Action: Specify a value for the required attribute. // 31077, 00000, "invalid attribute \"%s\" specified" // *Cause: The XML schema specifies an invalid attribute. // *Action: Remove specification of the invalid attribute. // 31078, 00000, "error in SQL mapping information" // *Cause: There is an error in the SQL type and table specification // within the XML Schema. // *Action: Ensure that all specified SQL types and tables are // valid and compatible with the corresponding XML types. // 31079, 00000, "unable to resolve reference to %s \"%s\"" // *Cause: The identified type or attribute or element could not be resolved. // *Action: Make sure that the name corresponds to a valid // XML (simple/complex) type or attribute or element and try again. // 31080, 00000, "type not specified for attribute or element \"%s\"" // *Cause: The identified attribute or element does not have a type. // *Action: Make sure that every attribute and element has a valid // type specification. // 31081, 00000, "name not specified for global declaration" // *Cause: The XML schema does not specify the name for the global // declaration of attribute or element or simpleType or complexType. // *Action: Specify names for all global declarations. // 31082, 00000, "invalid attribute \"%s\" specified in declaration of \"%s\"" // *Cause: The XML schema specifies an invalid attribute. // *Action: Remove specification of the invalid attribute. // 31083, 00000, "error while creating SQL type \"%s\".\"%s\" " // *Cause: An error occurred while trying to create the SQL type based // on the specification of a complex type. // *Action: Fix the identified error and try again. // 31084, 00000, "error while creating table \"%s\".\"%s\" for element \"%s\"" // *Cause: An error occurred while trying to create the table based // on the declaration for the identified element. // *Action: Fix the identified error and try again. // 31085, 00000, "schema \"%s\" already registered" // *Cause: An attempt was made to register a schema with the same URL // as a previously registered schema. // *Action: Register the schema with a different URL. 31086, 00000, "insufficient privileges to register schema \"%s\"" // *Cause: An attempt was made to register a schema without // sufficient privileges. // *Action: Make sure that the user has sufficient privileges to register // the schema. 31087, 00000, "insufficient privileges to delete schema \"%s\"" // *Cause: An attempt was made to delete a schema resource without // sufficient privileges. // *Action: Make sure that the user has sufficient privileges to delete the // schema. 31088, 00000, "object \"%s\".\"%s\" depends on the schema" // *Cause: An attempt was made to delete a schema which has dependent // objects. // *Action: Either drop the dependent objects prior to deleting the schema // or use the CASCADE or FORCE options. 31089, 00000, "schema \"%s\" does not target namespace \"%s\"" // *Cause: The schema document contains references (via include and import // definitions) to other schemas that do not belong to valid // namespaces. // *Action: Make sure that all schemas referenced via include definitions // target the same namespace as the parent schema. // Further make sure that the namespace specified in the import // definition matches the actual target namespace of the // specified schema. 31090, 00000, "invalid database schema name \"%s\"" // *Cause: The XML schema document contains an invalid database schema name // For example, the value of attribute SQLSchema // *Action: Make sure that all database user/schema names specified in the // XML schema document refer to existing database users/schemas. 31091, 00000, "empty string specified as a SQL name" // *Cause: The XML schema document contains a null SQL name. For // example, the values of attributes SQLName, SQLType, defaultTable. // *Action: Make sure that all names of SQL schema objects specified in the // XML schema document are valid SQL names. Otherwise, remove // such attributes from the schema and try again. 31092, 00000, "invalid SQL name \"%s\"" // *Cause: The XML schema document contains an invalid SQL name. For // example, the values of attributes SQLName, SQLType, defaultTable. // *Action: Make sure that all names of SQL schema objects specified in the // XML schema document are valid SQL names. This implies that // the database length and other restrictions on names be satisfied. 31093, 00000, "null or invalid value specified for parameter : %s" // *Cause: The argument value passed for the given parameter is null or // invalid. // *Action: Make sure that all the input argument values are valid. 31094, 00000, "incompatible SQL type \"%s\" for attribute or element \"%s\"" // *Cause: The SQL type information provided in the XML schema is not // compatible with the XML datatype for the specified attribute // or element. // *Action: Make sure that the specified SQL types are compatible with the // declared XML datatypes. 31095, 00000, "cannot generate %s : \"%s.%s\" already exists" // *Cause: The type/table name specified in the XML schema document // cannot be generated because it is already being used. // *Action: Use different names for types/tables or use the NOGEN mode // so that schema compiler does not generate new types/tables. 31096, 00000, "validation failed for schema" // *Cause: The XML Schema could not be validated. // *Action: Make sure that the SQLType and other datatype mapping is // valid. 31097, 00000, "Hierarchical Index not empty" // *Cause: An attempt was made to rebuild the hierarchical index which is // not empty. // *Action: Delete all rows in the hierarchical index and then // rebuild it. 31098, 00000, "Internal event to turn on XDB tracing" // *Cause: N/A // *Action: Do not document. 31099, 00000, "XDB Security Internal Error" // *Cause: An XDB Security internal error has occurred. // *Action: Contact Oracle Support. //////// 31100 - 31110 reserved for WebDAV compliant resource locks 31100, 00000, "XDB Locking Internal Error" // *Cause: An XDB Locking Internal error has occurred. // *Action: Contact Oracle Support. 31101, 00000, "Token \"%s\" not given while locking resource \"%s\"" // *Cause: Locking attempted on resource when the pricipal already owns // a lock given by the token above. // *Action: Reattempt the lock with the token. 31102, 00000, "Already locked in exclusive mode. Cannot add lock." // *Cause: The resource is already locked in exclusive mode. Cannot // add another lock. // *Action: Unlock the existing lock. 31103, 00000, "Resource locked in shared mode. Cannot add exclusive lock" // *Cause: The resource is locked in shared mode. Cannot add a shared lock. // *Action: Try locking in shared mode or unlocking the existing lock. 31104, 00000, "Cannot find lock with token \"%s\" on \"%s\"" // *Cause: The lock may have been unlocked or expired. If token was // supplied, token may be wrong. // *Action: Verify this lock exists. Supply correct token. 31105, 00000, "User does not own lock with supplied token \"%s\"" // *Cause: The lock corresponding to the supplied token is not owned // by the user. // *Action: Log on as correct user. Supply correct token. 31106, 00000, "Action failed as the parent container is locked" // *Cause: // *Action: Supply the lock token on parent container or unlock it 31107, 00000, "Action failed as resource \"%s\" is locked by name lock" // *Cause: Lock requests cause the whole request URI to be locked // *Action: Supply lock token or unlock the lock 31108, 00000, "Action failed as resource %s is locked" // *Cause: Delete/Rename failed because of an existing lock // *Action: Do lockdiscovery to find the lock and delete it. 31109, 00000, "Action failed as parent resource %s is locked" // *Cause: Delete/Rename failed because of an lock on parent resource // *Action: Do lockdiscovery to find the lock and delete it. 31110, 00000, "Action failed as resource %s is locked by name" // *Cause: Delete/Rename failed because one of the children is locked. // *Action: Do lockdiscovery to find the lock and delete it. // 31111, 00000, "table %s cannot be hierarchically enabled" // *Cause: Trigger _xdb_pitrigger already exists // *Action: Either the table is already hierarchically enabled or the // user trigger _xdb_pitrigger needs to be dropped. // // *Action: Delete all rows in the hierarchical index and then // rebuild it. // 31112, 00000, "fail to %s for %s port using xdb configuration" // *Cause: port number for the defined presentation is not valid // *Action: Either the port number is already in use or // it is protected. Specify another port number. // 31113, 00000, "XDB configuration may not be updated with non-schema compliant data" // *Cause: An attempt was made to update the XDB configuration resource with // non-schema or non-schema compliant data. // *Action: Check the document to make sure it is schema based and schema // compliant. // 31114, 00000, "XDB configuration has been deleted or is corrupted" // *Cause: The XDB configuration resource has been deleted or corrupted. // *Action: Reinstall XDB, or reinsert a valid configuration document. // 31115, 00000, "XDB configuration error: %s" // *Cause: An error related to XDB configuration has occurred. // *Action: Make sure the configuration resource contains valid data. // // 31116, 00000, "Tablespace not specified correctly" // *Cause: XDB cannot be moved to the specified tablespace. // *Action: Specify a valid tablespace. // // 31117, 00000, "Table \"%s\".\"%s\" is not resource metadata enabled" // *Cause: This table does not have a RESID column for resource metadata // *Action: Use disable/enable_hierarchy to enable resource metadata // // 31118, 00000, "System schema \"%s\" already registered" // *Cause: An attempt was made to register schema with same URL as a system schema. // *Action: Change the schema URL to avoid conflicts with system XML schemas. // 31119, 00000, "XDB configuration cannot be udpated on all instances" // *Cause: An attempt was made to update XDB configuration. // *Action: Ensure that each instance is correctly configured with // its listener. // / Range 31120 - 31150 for res view, link view & path index / 31121, 00000, "The %s operator cannot be FALSE" // *Cause: The value of the operator that was specified is FALSE. // *Action: Specify an operator that evaluates to TRUE. 31122, 00000, "The %s operator has incorrect RHS value" // *Cause: The value on the right hand side, that has been specified for the // operator did not evaluate to TRUE. // *Action: Specify a value on the right hand side that evaluates to TRUE . // / Range 31125 - 31150 for events / 31127, 00000, "RCList cannot contain noncommitted resource configuration" // *Cause: A commit was not executed after adding a resource configuration // to an RCList by calling DBMS_RESCONFIG.ADDRESCONFIG() // *Action: Make sure a commit is executed after calling // DBMS_RESCONFIG.ADDRESCONFIG() 31128, 00000, "The event handler calls cannot exceed the depth of %s" // *Cause: Tried to fire an event with depth exceeding the maximum. // *Action: Make sure the event that is being fired does not generate // infinitely recursive calls, either to itself or to other // functions or procedures. 31129, 00000, "Unable to retrieve repository's resource configuration" // *Cause: Tried to access a resource configuration referenced by the XDB repository that // has been deleted. // *Action: Disassociate the resource configuration from the repository. // 31130, 00000, "Specified resource configuration is not associated with given resource" // *Cause: Tried to delete a nonexistant resource configuration // from the configuration list of the target resource. // *Action: Make sure that the resource and resource configuration names // are specified correctly and the resource configuration belongs // to the configuration list of the given resource. 31131, 00000, " contains OID that is not a resource configuration OID" // *Cause: The OID in element was not a resource configuration OID. // *Action: Update the element and resubmit statement. // 31132, 00000, "Cannot validate handler \"%s\".\"%s\"" // *Cause: Attempted to invoke an invalid event handler. This can be a result // of one of the following reasons: // 1) The handler did not exist. // 2) The handler could not be compiled successfully. // *Action: Verify that the named handler does exist, then recompile and fix // all compilation errors that may subsequently arise. // 31133, 00000, "Cannot execute handler \"%s\".\"%s\" with invoker rights" // *Cause: Attempted to invoke an event handler with invoker rights when // the SET-INVOKER attribute in the resource configuration that // defines the handler was not set to TRUE. // *Action: Either redefine the named handler with definer rights or change // the SET-INVOKER attribute in the resource configuration that // defines the named handler to TRUE. // 31134, 00000, "Cannot delete a configuration that is referenced by other resources" // *Cause: Attempted to delete a resource configuration that was referenced by other // resources. // *Action: Remove all references to the target resource configuration by // executing DELETERESCONFIG or DELETEREPOSITORYRESCONFIG procedures // in DBMS_RESCONFIG package or specify the DELETE_FORCE option in the // DELETERESOURCE statement. // 31135, 00000, "Resource has already been rendered" // *Cause: One of the following has occurred: // 1) Attempted to invoke setRender* method after the resource was // rendered through a setRender* method or after data was written // to the output stream. // 2) Attempted to access the output stream of the resource after a setRender* // method was executed on the resource. // *Action: Remove the method causing the problem. // 31136, 00000, "Resource configuration %s is already associated with the resource %s" // *Cause: The resource configuration already exists in the resource configuration list // of the resource or the repository // *Action: Check if this resource configuration really needs to be added. If so, // remove it from resource and repository lists before adding it. // 31137, 00000, "Index out of range" // *Cause: The position specified was not valid. // *Action: Check (0 <= pos < size of the configuration list of the target resource) // 31138, 00000, "Resource-configuration is being referenced by one or more resources" // *Cause: Tried to add a resource configuration to the repository // that was being referenced by existing resources. // *Action: Remove the resource configuration from other resources // before trying to add it to the repository again. // 31139, 00000, "Invalid resource configuration list" // *Cause: Attempted to create or update a resource that had duplicate resource // configurations or conflicted with the repository configurations. // *Action: Correct the resource configuration list and re-submit statement. // 31140, 00000, "Illegal operation: %s" // *Cause: Tried to invoke a method when it was not allowed. // *Action: Do not execute the indicated method. // 31141, 00000, "Must specify a valid path value" // *Cause: The path specified for the or // element must refer to an existing resource. // *Action: Correct problem and resubmit statement. // 31142, 00000, "Must specify the schema for each listener" // *Cause: The schema element was not specified. // *Action: Correct problem and resubmit statement. // 31143, 00000, "XDB_SET_INVOKER role is required" // *Cause: XDB_SET_INVOKER role was required to set the SET-INVOKER // attribute to TRUE. // *Action: Correct problem and resubmit statement. // 31144, 00000, "Implementation language for %s is not specified" // *Cause: Implementation language for specified listener source was not // specified. // *Action: Correct problem and resubmit statement. // 31145, 00000, "Duplicate listener, %s, found in resource configuration" // *Cause: Duplicate listener source was found in resource configuration. // *Action: Remove duplicates and resubmit statement. // 31146, 00000, "Invalid listener source %s.%s" // *Cause: The listener source specified in the resource configuration // did not exist or was invalid. // *Action: Correct the listener source in the element and // resubmit statement. // 31147, 00000, "%s is not an ACL resource" // *Cause: The specified resource did not conform to acl.xsd schema. // *Action: Specify a valid path for the element and // resubmit statement. // 31148, 00000, "%s is not a valid resource configuration" // *Cause: The resource specified in the element while // creating a resource configuration or specified as the rcpath in a // call using DBMS_RESCONFIG package did not conform // to XDBResConfig.xsd schema. // *Action: Specify a valid path and resubmit statement. // 31149, 00000, "no such schema: %s" // *Cause: Nonexistent schema defined in the resource configuration. // *Action: Specify a valid schema in the resource configuration and resubmit // statement. // 31150, 00000, "uncaught error in handler %s" // *Cause: The named handler raised an exception. // *Action: Fix the identified error. // //////// 31151 - 31179 reserved for XML Schema Compiler 31151, 00000, "Cyclic definition encountered for %s: \"%s\"" // *Cause: The schema definition for this type has cycles. // *Action: Remove cyclic definition and re-compile schema. 31152, 00000, "Internal event to enable lru XOBs" // *Cause: N/A // *Action: Do not document 31153, 00000, "Cannot create schema URL with reserved prefix \"http://xmlns.oracle.com/xdb/schemas/\"" // *Cause: This prefix is reserved for XDB extended schema URLs and cannot // be used in a user specified URL. // *Action: Modify the prefix to a different one. 31154, 00000, "invalid XML document" // *Cause: The XML document is invalid with respect to its XML Schema. // *Action: Fix the errors identified and try again. 31155, 00000, "attribute %s not in XDB namespace" // *Cause: The specified attribute should be prefixed with XDB's namespace. // *Action: Ensure that all XDB specified attributes are prefixed with // XDB's namespace and try again. 31156, 00000, "Internal event to turn off validation during schema registration" // *Cause: N/A // *Action: Do not document // 31157, 00000, "Invalid Content-Type charset" // *Cause: HTTP Content-Type header had a charset that Oracle does not // understand. // *Action: Fix the Content-Type header in the HTTP request. // 31158, 00000, "schema \"%s\" currently being referenced" // *Cause: The specified schema URL is currently being referenced by // the same session. This could happen because of PLSQL // XMLType variables still in scope. // *Action: Ensure all references to this schema in this session are // released and try the operation again. // 31159, 00000, "XML DB is in an invalid state" // *Cause: XML DB's internal tables are in an invalid state, probably // because the database was not upgraded or the upgrade was // not successful // *Action: Ensure that the database is upgraded successfully. If the problem // persists, contact Oracle Support // 31160, 00000, "max substitution group size %s exceeded by \"%s\" (%s) for head element \"%s\" (%s)" // *Cause: The maximum limit on nested substitution groups has been exceeded // by an element. // *Action: Delete specified schema and re-register it after removing the // offending substitution element. // 31161, 00000, "element or attribute \"%s\" cannot be stored out of line" // *Cause: An element or attribute of a simple type has SQLInline=false // *Action: Remove the SQLInline=false qualification for the offending element // or attribute 31162, 00000, "element or attribute \"%s\" has no SQLType specified" // *Cause: Schema registration was invoked with GENTYPES=false without // specifying a SQLType for some element or attribute // *Action: Specify a SQLType for the offending element or attribute and // register the schema again 31163, 00000, "element or attribute \"%s\" has invalid attribute value \"%s\" (should be \"%s\")" // *Cause: An element or attribute for a complextype derived by restriction // has an attribute whose value is different from that in the base // type // *Action: Remove the mismatched attribute values from the offending element // or attribute 31164, 0, "cannot load object-relational XML attribute using direct path \n" // *Cause: The table being loaded contains a xml column with object-relational // storage. The xmltype column contains a type with subtypes. This // type of attribute cannot be loaded with direct path. // *Action:Perform the load with conventional path mode. // 31165, 0, "cannot load object-relational XML attribute using direct path \n" // *Cause: The table being loaded contains a xml column with object-relational // storage. The xmltype column either contains an out-of-line // partitioned table or the table itself is partitioned by one of // the attributes of xmltype. This type of table cannot be loaded // with direct path. // *Action:Perform the load with conventional path mode. // 31166, 0, "internal error code to handle ignorable attributes" // *Cause: N/A // *Action: Do not document // 31167, 00000, "XML nodes over 64K in size cannot be inserted" // *Cause: An attempt was made to insert an XML Text Node with a size // greater than 64K. This is not supported. // *Action: Create text nodes under 64K. 31168, 00000, "Node localname and namespace values should be less than 64K" // *Cause: An attempt was made to specify an XML Node with localname // or namespace value greater than or equal to 64K. This is not // supported. // *Action: Node localnames and namespace values should be under 64K. 31169, 00000, "Number of children (%s) defined in '%s' exceeds maximum (%s)" // *Cause: An attempt was made to define more than the allowed number // of children in a complexType of an XMLSchema document. // *Action: Modify the XML Schema to move children of complexType into // subelements that are not inlined. 31170, 00000, "Cyclic Schema Registration without using FORCE option" // *Cause: An attempt was made to register cyclic schemas // with FORCE = false. // *Action: Use FORCE = true when registering cyclic schemas. 31171, 00000, "schema processing error LSX-%s\nwhile %s" // *Cause: An LSX routine returned an error. // *Action: Look up the LSX error and follow its corrective action. 31172, 00000, "cannot load XMLType column using direct path \n" // *Cause: The table being loaded contained an XML column with object-relational // or binary storage and supplemental logging wass enabled for the table. // Direct path load is not supported for such table when supplemental // logging is enabled. // *Action:Perform the load with conventional path mode. 31176, 00000, "API not supported in this release" // *Cause: This API was not supported. // *Action: None 31178, 00000, "Miscellaneous event for XDB" // *Document: NO // *Cause: N/A // *Action: N/A 31179, 00000, "internal XDB event for ftp test harness" // *Cause: N/A // *Action: Do not document //////// 31180 - 31189 reserved for PL/SQL DOM API 31180, 00000, "DOM Type mismatch in invalid PL/SQL DOM handle" // *Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose // DOM Type that does not match the one available in the session. // This could happen because the pl/sql handle was reused, or the // original document is no longer available. // *Action: Ensure that the pl/sql handle for the target node is valid and // try the operation again. 31181, 00000, "PL/SQL DOM handle accesses node that is no longer available" // *Cause: The specified pl/sql handle is referencing a node in a // DOM Document that is no longer available. // *Action: Ensure that the pl/sql handle for the target node is valid and // try the operation again. 31182, 00000, "Too many PL/SQL DOM handles specified" // *Cause: An attempt was made to create a PL/SQL DOM handle that exceeded // the maximum allowable number of PL/SQL DOM handles. // *Action: Free PL/SQL DOM handles and try the operation again. 31183, 00000, "Node type %s cannot be converted to desired type" // *Cause: The given node's type cannot be converted correctly for // this operation. For example, a DOM Element cannot be converted // to Document Fragment // *Action: Pass a valid node type for the conversion. 31185, 00000, "DOM Nodes do not belong to the same DOM Document" // *Cause: The specified PL/SQL DOM Node does not belong to the // parent DOM Document of the referring DOM Node. // *Action: Ensure that both the DOM Nodes are part of the same // DOM Document. // 31186, 00000, "Document contains too many nodes" // *Cause: Unable to load the document because it has exceeded // the maximum allocated number of DOM nodes. // *Action: Reduces the size of the document. // 31187, 00000, "Cannot Add Node '%s' (type='%s') to Simple Type Node '%s'" // *Cause: Trying to add attribute/element nodes to a simple type against // the schema definition. Simple types can have only special // attribute like namespaces, xsi:nil etc. // *Action: Use a valid node for the operation. 31188, 00000, "The specified printing option is invalid" // *Cause: The printing option specified in the operation is invalid. // *Action: Use a valid printing option for the operation. 31190, 00000, "Resource %s is not a version-controlled resource" // *Cause: Either one of the following is the cause: // - Checkout is requested for a resource that isn't under version // control". Only version-controlled resource can be checked out. // - Checkout is requested for a row of a non-versioned table. // *Action: put the resource under version-control before checking out. 31191, 00000, "Resource %s is already checked out" // *Cause: Either one of the following is the cause: // - Checkout is requested for a resource that is already checked // out to the workspace by the same of different user. // *Action: checked in the resource from the workspace before checking out 31192, 00000, "Resource %s has not been checked out" // *Cause: Either one of the following is the cause: // - Checkin or uncheckout is requested for a resource that has not // been checked out to the workspace by any user in a workspace // *Action: checked in the resource from the workspace before checking out 31193, 00000, "This versioning feature isn't supported for resource %s" // *Cause: Either one of the following is the cause: // - Container cannot be put under version-controlled. // *Action: Avoid using these features. 31194, 00000, "Resource %s is already deleted" // *Cause: Access a version-controlled resource that is already deleted. // *Action: Recreate the resource. // // *Action: Remove the cyclic definitions in the type and retry compilation. 31195, 00000, "XML node '%s' (type=%s) does not support this operation" // *Cause: The given node's type is not supported for this operation. For // example, trying to add children to an attribute node, or passing // in a document node as a child, are unsupported operations. // *Action: Use a valid node type for the operation. 31196, 00000, "XML nodes over %s in size cannot be printed" // *Cause: An attempt was made to use an XML Text Node with a size // greater than 64K, or an XML Comment Node with a size greater // than 4K. These cannot be printed. For // example, trying to add children to an attribute node, or passing // in a document node as a child, are unsupported operations. // *Action: Use getClobVal() or getStringVal() to print the Document. 31197, 00000, "Error in processing file %s" // *Cause: An error occurred while operating on the specifed file. // The possible causes are // the file header is corrupt or // check the next error on stack // *Action: Ensure that the specified file is correct. // Look at the next error on the stack and take appropriate action. 31198, 00000, "Mismatch in number of bytes transferred due to non-binary mode" // *Cause: An error occurred while reading the specifed file. // The most probable cause is that the transfer was initiated in // ASCII mode. // *Action: Ensure that the transfer mode is set to BINARY 31199, 00000, "Warning in processing file %s" // *Cause: A warning was raised while operating on the specifed file. // However, the current operation was completed successfully. // *Action: This is primarily an informational message. // Look at the next error on the stack to obtain further // information. 31200, 00000, "Invalid ACL Argument" // *Cause: A System Constraining ACL was passed as one of the // arguments to this function. // *Action: Please ensure that none of the aclid arguments are for // the System Constraining ACL. // // //////////////////////////// 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. 31223, 00000, "DBMS_LDAP: cannot open more than %s LDAP server connections" // *Cause: An attempt was made to open more than the maximum allowed // LDAP server connections. // *Action: Free unused connections. 31224, 00000, "DBMS_LDAP: invalid LDAP session" // *Cause: An attempt was made by a PL/SQL module to use an LDAP session // which is not valid and might have already been closed. // *Action: Check the LDAP session handle in PL/SQL module involving // DBMS_LDAP. 31225, 00000, "DBMS_LDAP: invalid BER_ELEMENT" // *Cause: An attempt was made by a PL/SQL module to use a BER_ELEMENT // which is not valid and might have already been freed. // *Action: Check the BER_ELEMENT in PL/SQL module involving DBMS_LDAP. 31226, 00000, "DBMS_LDAP: MOD_ARRAY size limit exceeded" // *Cause: An attempt was made by a PL/SQL module to add an // element beyond the MOD_ARRAY size limit. // *Action: Increase the MOD_ARRAY size limit in PL/SQL module involving // DBMS_LDAP. 31227, 00000, "DBMS_LDAP: invalid LDAP MESSAGE handle" // *Cause: An attempt was made by a PL/SQL module to use an LDAP MESSAGE // handle which is not valid and might have already been freed. // *Action: Check the LDAP MESSAGE handle in PL/SQL module involving // DBMS_LDAP. 31228, 00000, "DBMS_LDAP: invalid MOD_ARRAY" // *Cause: An attempt was made by a PL/SQL module to use a MOD_ARRAY // which is not valid and might have already been freed. // *Action: Check the MOD_ARRAY in PL/SQL module involving DBMS_LDAP. 31229, 00000, "DBMS_LDAP: invalid input parameter" // *Cause: An invalid argument has been passed by a PL/SQL module to // a DBMS_LDAP subprogram // *Action: Check the input argument to the DBMS_LDAP subprogram in // PL/SQL module involving DBMS_LDAP. 31230, 00000, "DBMS_LDAP: unable to dynamically allocate additional memory" // *Cause: An error occured during dynamic memory allocation from // session heap. // *Action: Verify that adequate memory resources are available. 31231, 00000, "DBMS_LDAP: invalid PROPERTY_SET" // *Cause: An attempt was made by a PL/SQL module to use a PROPERTY_SET // which is not valid and might have already been freed. // *Action: Check the PROPERTY_SET in PL/SQL module involving DBMS_LDAP. 31232, 00000, "DBMS_LDAP: invalid MOD_PROPERTY_SET" // *Cause: An attempt was made by a PL/SQL module to use a MOD_PROPERTY_SET // which is not valid and might have already been freed. // *Action: Check the MOD_PROPERTY_SET in PL/SQL module involving DBMS_LDAP. 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 change source" // *Cause: The caller did not use the name of an existing change // source. The name given does not match the name of any // existing 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, "invalid value specified for begin_scn or end_scn" // *Cause: The begin_scn was not greater than zero. The end_scn was less than // zero. The end_scn was 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 invalid values. // *Action: Identify the bad parameter(s) and supply correct values to the // procedure. // 31410, 00000, "change set %s is not an existing change set" // *Cause: Could not find an existing 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, "invalid SOURCE_COLMAP value" // *Cause: A source_colmap value of 'y' was specified for an asynchronous // change table. // *Action: Specify a source_colmap parameter value of 'n' 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 does not exist" // *Cause: The subscription either did not exist or did not belong to // this user. // *Action: Call the function again with a valid subscription name. // 31426, 00000, "cannot modify active subscriptions" // *Cause: The subscription was already activated so that additional // calls to SUBSCRIBE were prohibited. // *Action: Subscribe to all the desired tables and columns before // activating the subscription. Ensure that the correct // subscription name is specifed. // 31427, 00000, "publication %s already subscribed" // *Cause: The subscription already contained this publication. // *Action: Check the values of subscription_name and publication_id. // Check any other subscribe calls to see if they subscribe // to columns that are shared among more than one publication // on the same source table. Do not attempt to subscribe to // the same publication more than once in the same subscription. // Use the publication_id variant of the SUBSCRIBE call if // needed to specify precise publications. // 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 has not been activated" // *Cause: The called procedure required an activated subscription. // *Action: Check the subscription name and correct if necessary. Call the // ACTIVATE_SUBSCRIPTION procedure for this subscription and // then reissue the original command. // 31430, 00000, "subscriber view exists" // *Cause: A view that is already in use was specified for the subscriber // view. // *Action: Call the SUBSCRIBE procedure using a different subscriber // view name. // 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: Either the schema_name.source_table did not exist or it did // not belong to this subscription. // *Action: Check the spelling of the schema_name and source_table. Verify // that the specifed table exists in the specifed schema and is // subscribed to by the subscription. // 31433, 00000, "subscriber view does not exist" // *Cause: The subscription did not contain this subscriber view. // *Action: Recheck the name, and specify the name of an existing // subscriber 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, 00000, "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, 00000, "invalid value for change_source" // *Cause: The specified value was not a valid name for a Change Source. // *Action: Specify a valid name and retry the command. // 31449, 00000, "invalid value for change_set_name" // *Cause: The specified value was not a valid name for a Change Set. // *Action: Specify a valid name and retry the command. // 31450, 00000, "invalid value for change_table_name" // *Cause: The specified value was not a valid name for a Change Table. // *Action: Specify a valid name and retry the command. // 31451, 00000, "invalid value %s for capture_values, expecting: OLD, NEW, or BOTH" // *Cause: The specified value was not a valid option for a capture_values. // *Action: Specify a valid option and retry the command. // 31452, 00000, "invalid value %s for parameter, expecting: Y or N" // *Cause: The specified value was not Y or N. // *Action: Specify Y or N for the parameter and retry the command. // 31453, 00000, "invalid value %s for parameter, expecting: Y, N, or NULL" // *Cause: The specified value was not Y, N or NULL. // *Action: Specify Y, N or NULL for the parameter and retry the command. // 31454, 00000, "invalid value %s for operation parameter, expecting: ADD or DROP" // *Cause: The specified value was not ADD or DROP. // *Action: Specify ADD or DROP and retry the command. // 31455, 00000, "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, 00000, "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, 00000, "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, 00000, "an internal error occurred" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Customer Support and report the error. // 31459, 00000, "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, 00000, "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, 00000, "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, 00000, "internal error while accessing metadata" // *Cause: An unexpected internal error occurred while CDC was accessing // its internal Metadata. // *Action: Contact Oracle Corporation // 31463, 00000, "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, 00000, "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, 00000, "cannot obtain a lock on the subscription" // *Cause: A timeout occurred while trying to place a lock on the // subscription. Another session had already acquired the // lock on the subscription. // *Action: Ensure the subscription name is correct and correct it if // necessary. If it is already correct, try the operation again // after the session holding the lock has released it. // 31466, 00000, "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, 00000, "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. // 31468, 00000, "cannot process DDL change record" // *Cause: The change set has stop_on_ddl enabled and was trying to process // a DDL change record. // *Action: Check the alert log to find out what the DDL record contained. // Make any necessary changes to the change tables. Call // ALTER_CHANGE_SET with recover_after_error and remove_ddl set to // 'Y'. // 31469, 00000, "cannot enable Change Data Capture for change set %s" // *Cause: The change set has reached the specified limit that was set up // by the CREATE_CHANGE_SET command. // *Action: Check the alert log to find out whether capture, apply or both // reached the limit. Once apply reaches its limit, the change // set is permanently disabled. Create a new change set with // new limits to continue capturing data. // 31470, 00000, "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, "invalid OBJECT_ID value" // *Cause: An object_id value of 'y' was specified for an asynchronous // change table. // *Action: Specify an object_id parameter value of 'n' 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. // 31473, 00000, "date bound out of range" // *Cause: The upper_bound or lower_bound specified in // extend_window or purge_window API is beyond the range of records // in the change set. // *Action: Either select a bound that is within range or do not // select an upper or lower bound at all. // 31474, 00000, "Invalid change view window" // *Cause: The specified upper_bound or lower_bound is forcing a condition // where the change view window will have nothing in it. // *Action: Select a different upper_bound or lower_bound and reissue the // API call that produced the error. Alternatively, make the // upper_bound or lower_bound parameter NULL and reissue the // API call. // 31475, 00000, "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, 00000, "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 listis 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, 00000, "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, 00000, "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 // *Action: Contact Oracle Corporation // 31479, 00000, "could not create LogMiner session" // *Cause: Failure during create of a new LogMiner session while advancing // an asynchronous change set. This is an internal error. // *Action: Contact Oracle Corporation // 31480, 00000, "staging database and source database cannot be the same" // *Cause: A CDC API call specified a source database name that matched // the staging database on which the CDC API call is being executed. // *Action: Make sure that the CDC API call is being executed from the // staging database and that the source database is correctly // specified. The source database and staging database need to be // different databases. // 31481, 00000, "change source %s is not a HotLog change source" // *Cause: A change source was specified that was not a HotLog // change source, but a HotLog change source was required. // *Action: Correct the call to supply a HotLog change source. // 31482, 00000, "invalid option for non-distributed Hotlog change source" // *Cause: A CDC API call specified enabled_source = 'Y' on a // non-Distributed HotLog change source. // *Action: Specify a Distributed HotLog change source. // 31483, 00000, "cannot have spaces in the parameter %s " // *Cause: The specifed parameter contained at least 1 space character. // *Action: Check the value of the specified parameter. Remove the spaces // and reissue the CDC API call. // 31484, 00000, "source database version must be at least 9.2.0.6 or greater" // *Cause: The source database is not at version 9.2.0.6 or higher. // *Action: Upgrade the source database to 9.2.0.6 or higher. // 31485, 00000, "invalid database link" // *Cause: The database link used to connect from a staging database to // a source database was invalid. The database link may not exist, // may not be accessible to the current user, or may have been // redefined since the Distributed HotLog change source was // originally created. // *Action: Make sure that there is a database link to the // source_database for the Distributed HotLog change source. // Make sure this database link is accessible to the current // user. // 31486, 00000, "cannot support column %s in this configuration" // *Cause: The specified column cannot be used in a Distributed HotLog // configuration when the source database version is 9.2.0.6 or // 10.1.0.0. // *Action: Remove the specified column from the CREATE_CHANGE_TABLE or // ALTER_CHANGE_TABLE CDC API call. // 31487, 00000, "cannot support begin dates or end dates in this configuration" // *Cause: The specified values cannot be used in a Distributed HotLog // configuration. // *Action: Remove the specified values from the CREATE_CHANGE_SET // CDC API call. // 31488, 00000, "cannot support change set %s in this configuration" // *Cause: Change sources with the hot mine option enabled are limited to // 1 change set. The system detected an existing change set so a // second one can not be created. // *Action: Associate the change set with a different change source. // 31489, 00000, "invalid DDL_MARKERS value" // *Cause: A DDL_MARKERS value of 'y' was specified for an synchronous // change table. // *Action: Specify a DDL_MARKERS parameter value of 'n' and call the // procedure again. // 31490, 00000, "could not attach to LogMiner session" // *Cause: Failure during attach to a LogMiner session while advancing // an asynchronous change set. This is an internal error. // *Action: Contact Oracle Corporation // 31491, 00000, "could not add logfile to LogMiner session" // *Cause: Failure during add logfile to a LogMiner session while advancing // an asynchronous change set. This is an internal error. // *Action: Contact Oracle Corporation // 31492, 00000, "could not set session parameters for LogMiner session" // *Cause: Failure during set parameters for a LogMiner session while // advancing an asynchronous change set. This is an internal error. // *Action: Contact Oracle Corporation // 31493, 00000, "could not prepare session for LogMiner session" // *Cause: Failure during prepare session for a LogMiner session while // advancing an asynchronous change set. This is an internal error. // *Action: Contact Oracle Corporation // 31494, 00000, "could not activate a LogMiner session" // *Cause: Failure during activation of a LogMiner session while advancing // an asynchronous change set. This is an internal error. // *Action: Contact Oracle Corporation // 31495, 00000, "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. // 31496, 00000, "must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables" // *Cause: An attempt was made to use the SQL command DROP TABLE for change // tables, but DROP TABLE is not supported for change tables. // *Action: Use the DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE procedure instead // of the DROP TABLE command. // 31497, 00000, "invalid value specified for first_scn" // *Cause: The first_scn was not greater than zero or was less than the // previous value of first_scn. // *Action: Check the value of first_scn. Correct it to make sure it is // an integer greater than zero and greater than any previous // value for this change source. // 31498, 00000, "description and remove_description cannot both be specified" // *Cause: The description and remove_description parameters were both // specified. // *Action: Check the values of description and remove_description. // Correct call to only supply one of these values. // 31499, 00000, "null value specified for required parameter %s" // *Cause: A null value was specified for a parameter that requires // an explicit value. // *Action: Correct call to supply a value for this parameter. // 31500, 00000, "change source %s is not a ManualLog change source" // *Cause: A change source was specified that is not a ManualLog // change source, but a ManualLog change source is required. // *Action: Correct call to supply a ManualLog change source. // 31501, 00000, "change source %s is not an AutoLog change source" // *Cause: A change source was specified that was not an AutoLog // change source, but an AutoLog change source was required. // *Action: Correct call to supply an AutoLog change source. // 31502, 00000, "invalid number supplied for supplemental_processes" // *Cause: The caller supplied an invalid value for supplemental_processes. // The value must be a positive integer. // *Action: Correct call to supply a positive integer value for // supplemental_processes. // 31503, 00000, "invalid date supplied for begin_date or end_date" // *Cause: The caller supplied an invalid value for begin_date or end_date. // The value must be a valid date value. // *Action: Correct call to supply a valid date value for // begin_date and/or end_date. // 31504, 00000, "cannot alter or drop predefined change source" // *Cause: The caller attempted to alter or drop one of the predefined // change sources HOTLOG_SOURCE or SYNC_SOURCE. // *Action: Do not attempt to alter or drop a predefined change source // or correct call to supply the name of a user-created change // source. // 31505, 00000, "cannot alter or drop predefined change set" // *Cause: The caller attempted to alter or drop the predefined // change set SYNC_SET. // *Action: Do not attempt to alter or drop the predefined change set // or correct call to supply the name of a user-created change // set. // 31506, 00000, "duplicate subscription name %s" // *Cause: A subscription by the specifed name already exists. // *Action: Recreate the subscription with a unique name. // 31507, 00000, "%s parameter value longer than maximum length %s" // *Cause: A value was specified for a parameter that was longer // than the maximum permitted length. // *Action: Correct the call to supply a shorter value for this parameter // that fits within the maximum length. // 31508, 00000, "invalid parameter value for synchronous change set" // *Cause: A parameter value was specified that is not supported // for synchronous change sets. // *Action: Correct the call to supply only valid parameter values // for a synchronous change set. Synchronous change sets // only support the default values for the following parameters: // begin_scn, end_scn, begin_date, end_date, stop_on_ddl, // supplemental_processes. // 31509, 00000, "publication does not exist" // *Cause: The specified publication did not exist or the specified // subscription subscribed to a publication that no longer exists. // *Action: Recheck the publication or subscription specified. Either // call the procedure again with an existing publication or // create a new subscription that only subscribes to existing // publications. // 31510, 00000, "name uses reserved prefix CDC$" // *Cause: A name was specified that starts CDC$. The name prefix CDC$ // is reserved for use by Oracle Corporation. // *Action: Change the name so it does not start with characters CDC$ // 31511, 00000, "name exceeds maximum length of 30 characters" // *Cause: A name was supplied that exceeds the maximum length of // 30 characters. // *Action: Change the name so it does not exceed 30 characters // 31512, 00000, "name cannot contain double quotation marks" // *Cause: A name containing a double quotation mark was supplied. // Subscription names cannot contain the double quotation mark. // *Action: Change the name so it has no double quotation marks // 31513, 00000, "unsupported column type specified in change table" // *Cause: A source column of an unsupported type was specified for // inclusion in a change table. Columns types of LOB or LONG are // not currently supported for change capture. // *Action: Change the column list so that it does not include columns // of LOB or LONG types. // 31514, 00000, "change set %s disabled due to capture error" // *Cause: This change set has encountered a capture error and was disabled. // *Action: Contact the change set's publisher to request that the // capture error be resolved. Subscriptions using this change // set cannot be activated or have their subscription windows // extended or purged until the capture error is resolved. // 31515, 00000, "CDC change source %s already exists" // *Cause: A Change Data Capture change source intended for import already // existed. // *Action: Either verify that the existing change source has the desired // characteristics or drop the existing change source and // perform the import again. // 31516, 00000, "CDC change set %s already exists" // *Cause: A Change Data Capture change set intended for import already // existed. // *Action: Either verify that the existing change set has the desired // characteristics or drop the existing change set and // perform the import again. // 31517, 00000, "CDC change table %s.%s already exists" // *Cause: A Change Data Capture change table intended for import already // existed. // *Action: Either verify that the existing change table has the desired // characteristics or drop the existing change table and // perform the import again. // 31518, 00000, "change column %s already exists in CDC change table %s.%s" // *Cause: A column in a Change Data Capture change table intended for // import was already present in the change table. // *Action: Either verify that the change table contains the desired // columns or drop the change table and perform the import again. // 31519, 00000, "CDC subscription %s already exists" // *Cause: A Change Data Capture subscription intended for import already // existed. // *Action: Either verify that the existing subscription has the desired // characteristics or drop the existing subscription and // perform the import again. // 31520, 00000, "CDC subscription %s already subscribes to publication ID %s" // *Cause: A Change Data Capture subscription intended for import already // subscribed to a publication. // *Action: Either verify that the existing subscription has the desired // characteristics or drop the existing subscription and // perform the import again. // 31521, 00000, "CDC subscription %s already subscribes to publication ID %s column %s" // *Cause: A Change Data Capture subscription intended for import already // subscribed to a published column. // *Action: Either verify that the existing subscription has the desired // characteristics or drop the existing subscription and // perform the import again. // 31522, 00000, "could not find Streams object %s for CDC change set %s" // *Cause: An underlying Streams capture, apply, or queue was missing // for an imported Change Data Capture change set. // *Action: Drop the imported change set because it is invalid. // Retry the import, ensuring that STREAMS_CONFIGURATION=y is // specified. // 31523, 00000, "could not find change source %s for CDC change set %s" // *Cause: The change source was missing for an imported // Change Data Capture change set. // *Action: Drop the imported change set because it is invalid. // Verify that the schema containing the missing change source // was included in the original export. If needed, perform the // export again, including the schema of the missing change source. // 31524, 00000, "could not find change set %s for CDC change table %s.%s" // *Cause: The change set was missing for an imported // Change Data Capture change table. // *Action: Drop the imported change table because it is invalid. // Verify that the schema containing the missing change set // was included in the original export. If needed, perform the // export again, including the schema of the missing change set. // 31525, 00000, "could not find column %s in CDC change table %s.%s" // *Cause: A column was missing for an imported Change Data Capture // change table. // *Action: It is likely that this table existed before the import // operation and import did not overwrite it. Determine whether // the imported change table should supercede the original // table. If so, drop the original table and retry the import. // If not, the change table must have a different name in // order to be imported. // 31526, 00000, "could not find source table %s.%s for CDC change table %s.%s" // *Cause: The source table was missing or was not set up correctly for // an imported Change Data Capture change table. A synchronous // change table requires the source table to exist and have the // Change Data Capture trigger defined on it. An asynchronous // change table requires table rules to be defined for the // source table. // *Action: Drop the imported change table because it is invalid. // Verify that the schema containing the source table // was included in the original export. If needed, perform the // export again, including the schema of the source table. // If change table is asynchronous, ensure that // STREAMS_CONFIGURATION=y is specified for the import. // 31527, 00000, "could not find source column %s for CDC change table %s.%s" // *Cause: A source column was missing for an imported Change Data Capture // change table. // *Action: Drop the imported change table because it is invalid. // Verify that the schema containing the source table // was included in the original export. If needed, perform the // export again, including the schema of the missing source table. // 31528, 00000, "could not find change set %s for CDC subscription %s" // *Cause: The change set was missing for an imported // Change Data Capture subscription. // *Action: Drop the imported subscription because it is invalid. // Verify that the schema containing the missing change set // was included in the original export. If needed, perform the // export again, including the schema of the missing change set. // 31529, 00000, "could not find publication for CDC subscriber view %s.%s" // *Cause: A publication was missing for an imported // Change Data Capture subscription. // *Action: Drop the imported subscription because it is invalid. // Verify that the schema containing the missing publication // was included in the original export. If needed, perform the // export again, including the schema of the missing publication. // 31530, 00000, "could not find published column %s for CDC subscriber view %s.%s" // *Cause: A published column was missing for an imported // Change Data Capture subscription. // *Action: Drop the imported subscription because it is invalid. // Verify that the schema containing the missing published column // was included in the original export. If needed, perform the // export again, including the schema of the missing published // column. // 31531, 00000, "could not find column %s in CDC subscriber view %s.%s" // *Cause: A column was missing in a subscriber view for an imported // Change Data Capture subscription. // *Action: It is likely that this view existed before the import // operation and import did not overwrite it. Determine whether // the imported subscriber view should supercede the original // view. If so, drop the original view and retry the import. // If not, the subscriber view must have a different name in // order to be imported. // 31532, 00000, "cannot enable change source %s" // *Cause: The change source cannot be enabled when there is no change // table created in any of the change sets associated with // the change source. // *Action: Add a change table to a change set before enabling the // the change source. // 31533, 00000, "only one change set (%s) is allowed in change source" // *Cause: A Distributed HotLog change source can contain at most one // change set. // *Action: Create a new change source and create the change set in the // new change source. // 31534, 00000, "Change Data Capture %s publisher %s is missing DBA role" // *Cause: The publisher does not have the DBA role, which is required by // the Change Data Capture operation. // *Action: Grant the DBA role the Change Data Capture publisher. // / 31535, 00000, "cannot support change source %s in this configuration" // *Cause: Each database can only have one change source with hot mine // option enabled. The system detected an existing hot mine // change source in the database, therefore, a second hot mine // change source cannot be created. // *Action: Remove the existing change source and create this new change // source again. // / 31536, 00000, "cannot support encrypted column %s in the source table" // *Cause: One of the columns specified in the parameter COLUMN_TYPE_LIST // was an encrypted column in the source table // *Action: remove the encrypted column in the parameter COLUMN_TYPE_LIST / 31537, 00000, "specified purge date is invalid" // *Cause: The purge date specified was an invalid date or was outside // of the range of data currently in the change set. // *Action: Do not specify purge date or specify a date that is within // the range of data in the change set. / 31538, 00000, "change set %s disabled" // *Cause: This change set was disabled. // *Action: Contact the change set's publisher to request that the // change set be enabled. Subscriptions using this change // set cannot be activated or have their subscription windows // extended or purged until the change set is enabled. / 31539, 00000, "no privilege to create job" // *Cause: This change table could not be created because the create job // privilege is needed to submit the default purge job. // *Action: Grant the create job privilege and try again / 31540, 00000, "%s is not a valid identifier" // *Cause: All Change Data Capture (CDC) identifiers must have at most 30 // characters, and must start with a letter that is followed // by any combination of letters, numerals, and the signs // '$', '_', and '#'. Other characters cannot be used in identifiers. // The rules for CDC identifiers are the same as for PL/SQL identifiers. // *Action: Rename object to conform to CDC naming rules and try again. / / ADD NEW CHANGE DATA CAPTURE ERROR MESSAGES ABOVE THIS LINE and add / additional tests to tqccmesg.sql / / Error Numbers 31600 - 31699 are reserved for Data Pump / 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. 31608, 00000, "specified object of type %s not found" // *Cause: The specified object was not found in the database. // *Action: Correct the object specification and try the call again. 31609, 00000, "error loading file \"%s\" from file system directory \"%s\"" // *Cause: The installation script initmeta.sql failed to load // the named file from the file system directory into the database. // *Action: Examine the directory and see if the file is present // and can be read. 31610, 00000, "cannot call this function from a non-master process" // *Cause: Called a Data Pump process model function from a process which is // not a master process. // *Action: Create a master process first. Then call the function from the // master process. If this error occurs from a Data Pump client (e.g. // expdp or impdp), try the operation again. If the error occurs // again, contact Oracle Customer Support and report the error. 31611, 00000, "Data Pump multiple processing setting is locked and cannot be changed." // *Document: NO // *Cause: Internal use only. // *Action: This error should never be reported except when doing problem // analysis under the supervision of Oracle development. // *Comment: Tried to disable or enable multiple processing after a master // process was already created in this session. Exit the session and // start a new session. Or, make the call before creating a master // process. 31612, 00000, "Allocation of process descriptor failed." // *Cause: During creation of a master process or a worker process, a failure // occurred allocating a process descriptor for the process. // *Action: Try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31613, 00000, "Master process %s failed during startup." // *Cause: The master process whose name is listed failed during startup. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31614, 00000, "routine %s received this error from %s: \n%s" // *Cause: The call to the specified routine failed and the specific error // text is included in this error message (the last %s string). // *Action: Correct inputs to the specified routine. 31615, 00000, "routine %s received this error: \n%s" // *Cause: The specified routine failed and the specific error // text is included in this error message (the last %s string). // *Action: Correct inputs to the specified routine. 31616, 00000, "unable to write to dump file \"%s\"" // *Cause: Export was unable to write to the export file, probably because of // a device error. This message is usually followed by a device // message from the operating system. // *Action: Take appropriate action to restore the device. 31617, 00000, "unable to open dump file \"%s\" for write" // *Cause: Export was unable to open the export file for writing. This // message is usually followed by device messages from the operating // system. // *Action: Take appropriate action to restore the device. 31618, 00000, "FILESIZE is outside valid range of %sKB to %sTB" // *Cause: The value specified for the FILESIZE parameter was either too small // to hold the header information for the export file, plus any data, // or exceeded the allowed maximum size for a dump file. // *Action: Retry the operation using a value for FILESIZE that falls within // the valid range. 31619, 00000, "invalid dump file \"%s\"" // *Cause: Either the file was not generated by Export or it was corrupted. // *Action: If the file was indeed generated by Export, report this as an // Import bug and submit the export file to Oracle Customer Support. 31620, 00000, "file or device \"%s\" cannot be specified for %s operation" // *Cause: There was an inappropriate use of file or device in the current // operation. // *Action: Correct operation or job setup. 31621, 00000, "error creating master process" // *Cause: Setup to create a master process failed. // *Action: Refer to any following error messages for possible actions. Correct // the error, if possible, and try the operation again. If the error // occurs again, contact Oracle Customer Support and report the error. 31622, 00000, "premature end of file at block %s" // *Cause: The end of the dump file input was unexpectedly reached. This is // caused either by a corrupted Data Pump export dump file or by an // Oracle internal error. This message should be preceded by another // message identifying the name of the dump file in question. // *Action: Retry the Data Pump import operation. Contact Oracle Support // Services if the problem persists. 31623, 00000, "a job is not attached to this session via the specified handle" // *Cause: An attempt to reference a job using a handle which is invalid or // no longer valid for the current session. // *Action: Select a handle corresponding to a valid active job or start a // new job. 31624, 00000, "A job cannot be modified after it has started." // *Cause: The user attempted to change the definition of a Data Pump job // through filters, transforms or parameters after it had started. // These changes can only be made while defining a job. // *Action: Stop the current job and rerun it with the correct definition. 31625, 00000, "Schema %s is needed to import this object, but is unaccessible" // *Cause: An error occurred when attempting to import objects. The schema // specified is needed to import this object, but access to this // schema is not available. // *Action: Refer to any following error messages for possible actions. Correct // the error, if possible, and try the operation again. If the error // occurs again, contact Oracle Customer Support and report the error. 31626, 00000, "job does not exist" // *Cause: An invalid reference to a job which is no longer executing, // is not executing on the instance where the operation was // attempted, or that does not have a valid Master Table. // Refer to any following error messages for clarification. // *Action: Start a new job, or attach to an existing job that has a // valid Master Table. 31627, 00000, "API call succeeded but more information is available" // *Cause: The user specified job parameters that yielded informational // messages. // *Action: Call DBMS_DATAPUMP.GET_STATUS to retrieve additional information. 31628, 00000, "error getting worker process exception" // *Cause: Attempt to get a worker process exception failed. // *Action: Refer to any following error messages for possible actions. Correct // the error, if possible, and try the operation again. If the error // occurs again, contact Oracle Customer Support and report the error. 31629, 00000, "unable to allocate additional memory" // *Cause: A dynamic memory allocation failure occurred. // *Action: Report this problem to a database administrator. 31630, 00000, "a job name is required to attach a job for user %s" // *Cause: No job name was supplied for an attach and the user has either // no jobs executing or mutiple jobs executing. // *Action: Provide a job name for attach to use in selecting an executing // job, or to use for restarting a stopped job. 31631, 00000, "privileges are required" // *Cause: The necessary privileges are not available for operations such // as: restarting a job on behalf of another owner, using a device // as a member of the dump file set, or ommiting a directory // object associated with any of the various output files. // Refer to any following error messages for additional information. // *Action: Select a different job to restart, try a different operation, or // contact a database administrator to acquire the needed privileges. 31632, 00000, "master table \"%s.%s\" not found, invalid, or inaccessible" // *Cause: A Master Table is required but no such table exists, or the // content is not consistent with that of a valid Master Table, // or the table is not accessible. Refer to any following error // messages for clarification. // *Action: Make sure a valid Master Table exists, and eliminate any problems // indicated by the following error messages. 31633, 00000, "unable to create master table \"%s.%s\"" // *Cause: Job creation failed because a Master Table and its indexes could // not be created, most commonly due to the pre-existance of a table // with the same name (job name) in the user schema. Refer to any // following error messages for clarification. // *Action: Select a different job name, DROP the existing table, or eliminate // any problems indicated by the following error messages. 31634, 00000, "job already exists" // *Cause: Job creation or restart failed because a job having the selected // name is currently executing. This also generally indicates that // a Master Table with that job name exists in the user schema. Refer // to any following error messages for clarification. // *Action: Select a different job name, or stop the currently executing job // and re-try the operation (may require a DROP on the Master Table). 31635, 00000, "unable to establish job resource synchronization" // *Cause: A lock used in synchronizing Data Pump resources during job // creation and deletion could not be obtained during job creation. // This indicates that a process for some other Data Pump job has not // released the lock due to an internal error. // *Action: Eliminate the processes for any failed Data Pump job and try to // create the new job again. If the error continues to occur, contact // Oracle Customer Support and report the error. 31636, 00000, "session is already attached to job %s for user %s" // *Cause: The session executing the attach is already attached to // the specified job. // *Action: Select a different job or create a new session. 31637, 00000, "cannot create job %s for user %s" // *Cause: Unable to create or restart a job. Refer to any following or // prior error messages for clarification. // *Action: Eliminate the problems indicated. 31638, 00000, "cannot attach to job %s for user %s" // *Cause: Unable to attach a job to a session. Refer to any following or // prior error messages for clarification. // *Action: Eliminate the problems indicated. 31639, 00000, "unexpected data found" // *Cause: The Master Table or Data Pump file contents appear invalid. The // table or file may not have been produced by a Data Pump job, or // they may have been corrupted. // *Action: Select a different job name (Master Table) or replace the // table or file with one produced by Data Pump. 31640, 00000, "unable to open dump file \"%s\" for read" // *Cause: Import was unable to open the export file for reading. This // message is usually followed by device messages from the operating // system. // *Action: Take appropriate action to restore the device. 31641, 00000, "unable to create dump file \"%s\"" // *Cause: Export was unable to create the specified file with write enabled. // *Action: Check the file name and file system for the source of the error. 31642, 00000, "the following SQL statement fails: \n%s" // *Cause: An internal error was generated from package DBMS_METADATA. // *Action: Contact Oracle Customer Support and report the error. 31643, 00000, "unable to close dump file \"%s\"" // *Cause: Export or Import was unable to close the dump file. This message // is usually followed by device messages from the operating system. // *Action: Take appropriate action to restore the device. 31644, 00000, "unable to position to block number %s in dump file \"%s\"" // *Cause: Export or Import was unable to position its file pointer to a // specific block within the dump file. This message is usually // followed by device messages from the operating system. // *Action: Take appropriate action based on the device messages. 31645, 00000, "unable to read from dump file \"%s\"" // *Cause: Import could not read from the dumpfile, probably because of a // device error. This message is usually followed by a device message // from the operating system. // *Action: Take appropriate action to restore the device. 31646, 00000, "no dump files found" // *Document: NO // *Cause: Signal to Master process that no files have been added to the // Import job. // *Action: 31647, 00000, "Worker process received exit message from Master process" // *Document: NO // *Cause: File Manager component raises this exception to calling Worker // when it receives an exit message during a file request. Worker // can then initiate its orderly shutdown. // *Action: 31648, 00000, "Timeout before master process %s finished initialization." // *Cause: The master process whose name is listed started up but did not // finish its initialization within the allowed time limit. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31649, 00000, "Master process %s violated startup protocol." // *Cause: The master process whose name is listed started up but then exited // before notifying the creating process that it was finished with // initialization. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31650, 00000, "timeout waiting for master process response" // *Cause: After creating the job infrastructure and sending the initial // message to the master process, it failed to respond in the // allotted time and most likely aborted during startup. // *Action: Retry the open or attach request. Contact Oracle Customer Support // if the problem persists. 31651, 00000, "communication error with master process - detaching job" // *Cause: Unexpected failure trying to communicate with the master // process. // *Action: Attach again and retry operation. Contact Oracle Customer Support // if the problem persists. 31652, 00000, "command response message was invalid type - detaching job" // *Cause: Something horribly wrong with the command/response protocol. // *Action: Reattach and retry operation. Contact Oracle Customer Support if // the problem persists. 31653, 00000, "unable to determine job operation for privilege check" // *Cause: Failure trying to determine the operation of the current job // in order to test for appropriate privileges. // *Action: Retry in case it's an intermittent failure. If it still fails, // detach, reattach, and retry the call. Contact Oracle Customer // Support if the problem persists. 31654, 00000, "unable to convert file or volume size as specified to a number" // *Cause: File or volume size specification has an error the prevents it // from being converted into a numeric value. // *Action: Fix the call. 31655, 00000, "no data or metadata objects selected for job" // *Cause: After the job parameters and filters were applied, // the job specified by the user did not reference any objects. // *Action: Verify that the mode of the job specified objects to be moved. // For command line clients, verify that the INCLUDE, EXCLUDE and // CONTENT parameters were correctly set. For DBMS_DATAPUMP API // users, verify that the metadata filters, data filters, and // parameters that were supplied on the job were correctly set. 31656, 00000, "cannot use TABLESPACE_EXPR filter with transportable mode" // *Cause: A TABLESPACE_EXPR metadata filter was supplied for for a // transportable mode import job. Transportable mode import does // not support the subsetting of tablespaces from a dump file set. // *Action: Remove the filter expression. 31657, 00000, "data filter name can not be defaulted" // *Cause: A null data filter name was supplied. // *Action: Fix the call to specify a data filter name. 31658, 00000, "specifying a schema name requires a table name" // *Cause: The caller specified a schema name but neglected to specify // a corresponding table name. // *Action: Fix the call to include a table name. 31659, 00000, "status message was invalid type - detaching job" // *Cause: Message from the master process on the status queue // had an invalid message type, indicating a failure in the protocol. // *Action: Reattach and retry the operation. Contact Oracle Customer Support // if the problem persists. 31660, 00000, "metadata filter name can not be defaulted" // *Cause: A null metadata filter name was supplied. // *Action: Fix the call to specify a metadata filter name. 31661, 00000, "there are no metadata transform values of type VARCHAR2" // *Cause: The specified metadata transform value was an invalid type. // *Action: Fix the call to specify a valid metadata transform value. 31662, 00000, "metadata transform name can not be defaulted" // *Cause: A null metadata transform name was supplied. // *Action: Fix the call to specify a metadata transform name. 31663, 00000, "metadata remap name can not be defaulted" // *Cause: A null metadata remap name was supplied. // *Action: Fix the call to specify a metadata remap name. 31664, 00000, "unable to construct unique job name when defaulted" // *Cause: The job name was defaulted, and the name creation algorithm // was unable to find a unique job name for this schema where the // table name (for the master table) didn't already exist. // *Action: Specify a job name to use or delete some of the existing tables // causing the name conflicts. 31665, 00000, "mode can only be defaulted for IMPORT and SQL_FILE operations" // *Cause: The job mode can not be null except for IMPORT and SQL_FILE // operations. // *Action: Fix the call to specify the job mode. 31666, 00000, "Master process %s had an unhandled exception." // *Cause: A Data Pump process model master process had an unhandled exception // condition. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31667, 00000, "parameter name can not be defaulted" // *Cause: A null was supplied for the parameter name. // *Action: Fix the call by providing a valid parameter name. 31668, 00000, "Timeout before worker process %s finished initialization." // *Cause: The worker process whose name is listed started up but did not // finish its initialization within the allowed time limit. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31669, 00000, "Worker process %s violated startup protocol." // *Cause: The worker process whose name is listed started up but then exited // before notifying the creating process that it was finished with // initialization. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31670, 00000, "Username argument must be specified and non-null." // *Cause: Called change user with a NULL username or a null string. // *Action: Specify a valid username argument. If this error occurs from a // Data Pump client (e.g. expdp or impdp), try the operation again. // If the error occurs again, contact Oracle Customer Support and // report the error. 31671, 00000, "Worker process %s had an unhandled exception." // *Cause: A Data Pump process model worker process had an unhandled exception // condition. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31672, 00000, "Worker process %s died unexpectedly." // *Cause: A Data Pump process model worker process died unexpectedly, so // PMON is cleaning up the process. // *Action: Check your system for problems. Check the trace file for the // process, if one was created, for any additional information. // Correct the error, if possible, and try the operation again. If // the error occurs again, contact Oracle Customer Support and report // the error. 31673, 00000, "worker process interrupt for normal exit by master process" // *Cause: A worker process was requested to clean up and exit because the // master process is doing a normal exit. // *Action: If this error occurs from a Data Pump client (e.g. expdp or // impdp). it means that the master process for the operation exited // prematurely. Try the operation again. If the error occurs again, // contact Oracle Customer Support and report the error. 31674, 00000, "worker process interrupt for unhandled exception in master process" // *Cause: A worker process was requested to clean up and exit because an // unhandled exception occurred in the master process. // *Action: If this error occurs from a Data Pump client (e.g. expdp or // impdp), it means that the master process for the operation had an // unhandled exception. Check the log file for the operaton and the // trace file for the master process for any additional information. // Try the operation again. If the error occurs again, contact // Oracle Customer Support and report the error. 31675, 00000, "worker process interrupt for unexpected death of master process" // *Cause: A worker process was requested to clean up and exit (signaled // by PMON, doing cleanup because the master process died // unexpectedly). // *Action: If this error occurs from a Data Pump client (e.g. expdp or // impdp), it means that the master process for the operation died // unexpectedly. Check the log file for the operaton and the trace // file for the master process for any additional information. Try // the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31676, 00000, "illegal value for number of workers, %s" // *Cause: Called create worker processes with an illegal number of workers // specified. // *Action: Make sure that the number of workers value is greater than 0 and // less than the maximum value for the platform (normally 32767). If // this error occurs from a Data Pump client (e.g. expdp or impdp) // and you specified the parallel parameter, try the operation again // with a smaller value for the parallel parameter. If the error // occurs again, contact Oracle Customer Support and report the error. 31677, 00000, "Estimate in progress using %s method..." // *Document: NO 31678, 00000, "Worker Aborting Job" // *Document: NO 31679, 00000, "Table data object %s has long columns, and longs can not be loaded/unloaded using a network link" // *Cause: Table data objects that contain long columns can not be selected // over a network link. // *Action: Export this table to a file and then import the same table from // the file. 31680, 00000, ". . exported %s %s rows" // *Document: NO 31681, 00000, ". . imported %s %s rows" // *Document: NO 31682, 00000, "Master table %s successfully loaded/unloaded" // *Document: NO 31683, 00000, "Processing object type %s" // *Document: NO 31684, 00000, "Object type %s already exists" // *Document: NO 31685, 00000, "Object type %s failed due to insufficient privileges. Failing sql is:\n%s" // *Document: NO 31686, 00000, "error creating worker processes" // *Cause: Setup to create worker processes failed. // *Action: Refer to any following error messages for possible actions. Correct // the error, if possible, and try the operation again. If the error // occurs again, contact Oracle Customer Support and report the error. 31687, 00000, "error creating worker process %s with worker id %s" // *Cause: Attempt to create the listed worker process failed. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31688, 00000, "Worker process %s failed during startup." // *Cause: The worker process whose name is listed failed during startup. // *Action: Refer to any following error messages for possible actions. Check // the trace log for the failed process to see if there is any // information about the failure. Correct the error, if possible, and // try the operation again. If the error occurs again, contact Oracle // Customer Support and report the error. 31689, 00000, "illegal value for base worker id, %s" // *Cause: Called create worker processes with an illegal base worker id value // specified. // *Action: Make sure that the base worker id value is greater than 0 and less // than the maximum value for the platform (normally 32767). If this // error occurs from a Data Pump client (e.g. expdp or impdp), try the // operation again. If the error occurs again, contact Oracle Customer // Support and report the error. 31690, 00000, "Process name buffer size must be specified and must be greater than 0." // *Cause: Called get worker exception and either specified NULL or 0 for the // buffer size argument. // *Action: Be sure to specify a buffer size that is big enough to hold the // worker process name (e.g. 30 bytes). If this error occurs from a // Data Pump client (e.g. expdp or impdp), try the operation again. If // the error occurs again, contact Oracle Customer Support and report // the error. 31691, 00000, "The worker received message number %s from the MCP, which is invalid." // *Cause: Bad code. // *Action: Fix mcp code and reissue export/import command. 31692, 00000, "The following SQL statement failed trying to insert a row into the Master table:\n%s" // *Cause: Bad code. // *Action: Fix code and reissue export/import command. 31693, 00000, "Table data object %s failed to load/unload and is being skipped due to error:\n%s" // *Cause: Table failed to load or unload due to some error. // *Action: Check load/unload error, correct problem and retry command. 31694, 00000, "master table %s failed to load/unload" // *Cause: Master table failed to load or unload. // *Action: Check load/unload error, correct problem and retry command. 31695, 00000, "Inconsistent master table on restart. The following SQL statement returned %s identical objects.\n%s" // *Cause: Master table on restart has the same object inserted multiple // times. // *Action: Restart not possible, reissue original export/import. 31696, 00000, "unable to export/import %s using client specified %s method" // *Cause: Table attributes prevent client specified method for exporting // or importing data. // *Action: Use default 'DATA_ACCESS' parameter value. 31697, 00000, "aborting operation at process order number %s" // *Cause: User asked for it. // *Action: Don't ask for it. 31698, 00000, "Error stack buffer size must be specified and must be greater than 0." // *Cause: Called get worker exception and either specified NULL or 0 for the // error stack size argument. // *Action: Be sure to specify am error stack buffer size that is big enough to // hold the error stack string (e.g. 4096 bytes). If this error occurs // from a Data Pump client (e.g. expdp or impdp), try the operation // again. If the error occurs again, contact Oracle Customer Support // and report the error. 31699, 00000, "test error for use in testing" // *Document: NO // *Cause: Internal use only // *Action: This error should never be reported to a customer. // *Comment: Test error for use in testing. / / Data Pump errors continue with message 39001 / //////////////////////////// Future Security Features / Error Numbers 31700 to 31900 are reserved for Future Security Features 31700, 00000, "Very long string supplied for AUDIT_SYSLOG_LEVEL parameter" // *Cause: Very long string supplied for AUDIT_SYSLOG_LEVEL in init.ora // *Action: Use a valid facility.level such as "local1.notice" as described // in syslog's manual pages / 31701, 00000, "Event to enable xmltype table export/import with schema" // *Cause: Event to enable xmltype table export/import with schema // *Action: Disable the event at level 0x100 / //////////////////////////// End of Future Security Features //////////////////////////// Summary Management / Error Numbers 31901 to 31999 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 / 31902, 00000, "access advisor debug/testing trace" // *Document: NO // *Cause: // *Action: access advisor debug/testing / //////////////////////////// KSP / Error numbers 32000 to 32030 are reserved for parameter operations //////////////////////////// 32000, 00000, "write to SPFILE requested but SPFILE is not modifiable" // *Cause: An ALTER SYSTEM command or an internal self-tuning mechanism // requested a write to the SPFILE but the SPFILE was not modifiable. // *Action: Perform an in-memory parameter update only. / 32001, 00000, "write to SPFILE requested but no SPFILE is in use" // *Cause: An ALTER SYSTEM command or an internal self-tuning mechanism // requested a write to the SPFILE but no SPFILE was in use. // *Action: Re-start the instance using an SPFILE, or execute ALTER SYSTEM // SET 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, "error occured processing parameter '%s'" // *Cause: An error occured while parsing the parameter file. // *Action: See additional errors to determine the root cause. / 32004, 00000, "obsolete or deprecated parameter(s) specified for %s instance" // *Cause: Obsolete or deprecated parameters for this instance type // 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. / 32011, 00000, "cannot restore SPFILE to location already being used by the instance" // *Cause: A restore operation trying to write to an SPFILE // that was used to startup the instance. // *Action: Specify a different SPFILE name / 32012, 00000, "SPFILE format is inconsistent with value of COMPATIBLE parameter" // *Cause: The SPFILE was in H.A.R.D. (Hardware Assisted Resilient Data) // compliant format but the value of the COMPATIBLE parameter was set // to pre-11.0. This is not allowed since Oracle has a policy of // irreversible compatibility advance. // *Action: Change the value of the COMPATIBLE parameter to be 11.0 or // higher. / 32013, 00000, "failure in verifying parameters from the restored SPFILE" // *Cause: Failure during processing of parameters from restored SPFILE. // It could be that restore image of the SPFILE is corrupted. // *Action: Further diagnostic information should be in the error stack. / 32014, 00000, "error processing parameter \"%s\" from the SPFILE restore image" // *Cause: Failure during processing of parameters from restored SPFILE. // It could be that restore image of the SPFILE is corrupted. // *Action: Further diagnostic information should be in the error stack. / 32015, 00000, "unable to restore SPFILE" // *Cause: Failure during SPFILE restore. It could be that the restore // destination is not valid. // *Action: Further diagnostic information should be in the error stack. / 32016, 00000, "parameter \"%s\" cannot be updated in SPFILE" // *Cause: Database is mounted. // *Action: Unmount the database to update the parameter in the SPFILE / 32017, 00000, "failure in updating SPFILE" // *Cause: A failure occured while updating the SPFILE. // *Action: See associated errors. / 32018, 00000, "parameter cannot be modified in memory on another instance" // *Cause: Parameter adjustment can take a very long time // *Action: Modify the parameter individually on each instance using // the SID clause of the alter system command / 32019, 00000, "The parameter SPFILE cannot be updated in the server parameter file." // *Cause: An attempt was made to update the parameter SPFILE in the server // parameter file. // *Action: Convert the server parameter file into a parameter file and then // add the parameters needed and recreate the server parameter file. / 32020, 00000, "SID='*' clause needed to modify this parameter" // *Cause: The parameter did not have the same value on all RAC instances. // *Action: Retry the command by specifying SID='*' // / 32021, 00000, "parameter value longer than %s characters" // *Cause: An attempt was made to alter a parameter value but the number of // characters in the parameter value was longer than the // allowed maximum. For a list parameter, one of the // values in the list was longer than the allowed maximum. // *Action: Reduce the parameter value length and retry the command. // For the DISPATCHERS parameter, use listener aliases to // reduce value length. / 32022, 00000, "parameter value longer than %s characters" // *Cause: An attempt was made to alter a parameter value but the // combined length of all the parameter values was more than // the allowed maximum. // *Action: Reduce the parameter value length and retry the command. // For the DISPATCHERS parameter, use listener aliases to // reduce value length. / 32023, 00000, "Could not obtain PE enqueue" // *Document: NO // *Cause: Internal error used by parameter processing // *Action: None / 32024, 00000, "invalid directory specified for audit_file_dest parameter" // *Cause: Either the directory does not exist or it is not writable. // *Action: Retry the command by specifying a valid directory or granting // appropriate directory permissions. / 32025, 00000, "%s.%s is not a table or view object." // *Cause: An attempt was made to set the audit table to a non-table object // or a non-view object. // *Action: Specify a valid table or view object for the audit table option. / 32026, 00000, "%s.%s has fewer columns compared to %s table." // *Cause: An attempt was made to set the audit table to a table or view // object that has fewer columns compared to the base audit table. // *Action: Specify a valid table or view object for the audit table option. / 32027, 00000, "There is no %s column with the matching type in %s.%s." // *Cause: An attempt was made to set the audit table to a table or view // object that does not have a column with the same name and type // as the one in the audit table. // *Action: Specify a valid table or view object for the audit table option. / 32028, 00000, "Syslog facility or level not recognized" // *Cause: Syslog facility or level did not conform to the standard // facility or level provided in the syslog.h file // *Action: Specify a facility or level such as "LOCAL1.NOTICE" // which conforms to the syslog.h file / 32029, 00000, "resetting with SCOPE=MEMORY or SCOPE=BOTH is currently not supported" // *Cause: An attempt was made to reset an in-memory parameter value // *Action: Specify SCOPE=SPFILE if applicable, or explicitly set the // parameter to the desired value / 32030, 00000, "an SPFILE is already associated with the instance" // *Cause: An attempt was made to update the parameter SPFILE on an instance // that was already associated with an spfile. // *Action: Restart the instance with a parameter file. / / / Error Numbers 32031 - 32049 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 cannot be specified within parenthesis. // *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 its definition query is too simple and references another // query name. This is currently unsupported yet. // *Action: remove such query name and retry / 32037, 00000, "unsupported use of LEVEL in membership condition" // *Cause: An attempt was made to use LEVEL in membership condition with // subquery that is not supported. // *Action: Rewrite query to avoid using LEVEL in membership condition / 32038, 00000, "number of WITH clause column names does not match number of elements in select list" // *Cause: A list of column aliases or names was specified for a WITH clause // query name but the number of elements in the list did not match the // number of elements in the select list of the definition query. // *Action: Update the column alias list or the select list to ensure they // have the same number of elements. / 32039, 00000, "recursive WITH clause must have column alias list" // *Cause: A WITH clause query referred to itself (recursive) but did // not have a column alias list specified for it. // *Action: Add a column alias list for the WITH clause query name. / 32040, 00000, "recursive WITH clause must use a UNION ALL operation" // *Cause: A WITH clause query referred to itself (recursive) but did // not use a UNION ALL operation in its definition query. // *Action: Rewrite the recursive WITH clause query to use a UNION ALL // operation. / 32041, 00000, "UNION ALL operation in recursive WITH clause must have only two branches" // *Cause: A WITH clause query referred to itself (recursive) but used // a UNION ALL operation with more than two branches, which is not // currently supported. // *Action: Rewrite the recursive WITH clause query to use only two branches in // the UNION ALL operation. / 32042, 00000, "recursive WITH clause must reference itself directly in one of the UNION ALL branches" // *Cause: A WITH clause query referred to itself (recursive) indirectly, // such as through a subquery or view. // *Action: Rewrite the recursive WITH clause query to refer to itself directly // in the FROM clause of one of the UNION ALL branches. / 32043, 00000, "recursive WITH clause needs an initialization branch" // *Cause: A WITH clause query referred to itself (recursive) but did not // have a branch in a UNION ALL with no references to itself (the // initialization branch or anchor member). // *Action: Rewrite the recursive WITH query to have a branch in a UNION // ALL operation with no references to itself. / 32044, 00000, "cycle detected while executing recursive WITH query" // *Cause: A recursive WITH clause query produced a cycle and was stopped // in order to avoid an infinite loop. // *Action: Rewrite the recursive WITH query to stop the recursion or use // the CYCLE clause. / 32045, 00000, "maximum level of recursion reached while executing recursive WITH query" // *Cause: A recursive WITH query reached the maximum level of recursion // specified and was stopped. // *Action: Increase the maximum level of recursion or use the CYCLE clause. / 32046, 00000, "sequence column name for SEARCH clause must not be part of the column alias list" // *Cause: The SEARCH clause for a recursive WITH query specified a sequence // column that was already listed in the column alias list for the // WITH clause query name. // *Action: Specify a different name for the sequence column for the SEARCH // clause or remove the name from the column alias list. / 32047, 00000, "cycle mark value and non-cycle mark value must be one byte character string values" // *Cause: The cycle mark or the non-cycle mark values specified in the CYCLE // clause of a recursive WITH query were not one byte character // string values as required. // *Action: Specify a one byte character string for the cycle mark and // non-cycle mark values of the CYCLE clause for the recursive WITH // query. / 32048, 00000, "cycle mark column name for CYCLE clause must not be part of the column alias list" // *Cause: The CYCLE clause for a recursive WITH query specified a cycle mark // column that was already listed in the column alias list for the // WITH clause query name. // *Action: Specify a different name for the cycle mark column for the CYCLE // clause or remove the name from the column alias list. / 32049, 00000, "duplicate name found in column alias list for WITH clause" // *Cause: The column alias list for a WITH clause element contained a name // which appeared more than once in the list. // *Action: Remove the duplicate name from the column alias list. / ////////////////////////////// FILE MAPPING ERRORS // Error numbers 32050 to 32099 are reserved for file mapping errors ////////////////////////////// 32050, 00000, "%s operation failed" // *Cause: A mapping operation failed. // *Action: Check FMON trace files for errors. / 32051, 00000, "mapping service not available" // *Cause: The mapping service was never started or previously failed // to start properly. // *Action: Set FILE_MAPPING to TRUE if it is not currently set. Otherwise, // check FMON trace files for an ORA-32052 error. / 32052, 00000, "failed to start mapping service" // *Cause: The mapping service failed to start properly. // *Action: Check FMON trace files for errors. / 32053, 00000, "operation not supported" // *Cause: Mapping libraries do not support operation. // *Action: Check whether mapping libraries are available and // whether operation is supported by the libraries. / 32054, 00000, "lost communication with FMPUTL process" // *Cause: Lost communication with mapping utility. // *Action: Check FMON and FMPUTL trace files for errors. / 32055, 00000, "invalid file type" // *Cause: Invalid file type used when mapping files. // *Action: Specify one of expected file types. / 32056, 00000, "invalid number of extents" // *Cause: Invalid number of extents used for map operation. // *Action: Specify a non-negative number of extents. / 32057, 00000, "invalid lock mode" // *Cause: An invalid mode was used for a lock operation. // *Action: Specify one of expected lock modes. / 32058, 00000, "operation restricted to SYSDBA users" // *Cause: Operation requires SYSDBA priviliges. // *Action: Connect to the database as SYSDBA. / 32059, 00000, "deadlock detected on mapping structures" // *Cause: Mapping structures already locked by the same session. // *Action: Unlock mapping structures before proceeding with current operation. / 32060, 00000, "channel failure" // *Cause: Channel failure between foreground and background process. // *Action: Check foreground trace files for errors. / / / 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. / 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. / 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. / 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. / 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. / 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. / 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. / 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. / 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 / 32163, 00000, "Method called on Invalid Environment type" // *Cause: A non-XA call made on an XA Environment or // XA call made on non-XA Environment // *Action: Make sure Environment type is OK / 32164, 00000, "Method called on Invalid Connection type" // *Cause: A non-XA call made on an XA Connection or // XA call made on non-XA Connection // *Action: Make sure Connection type is OK / 32165, 00000, "Cannot get XA environment" // *Cause: Incorrect dbname string was passed or the // XA connection has not been opened // *Action: Pass the correct dbname string or check if // the XA connection is open / 32166, 00000, "Cannot get XA connection" // *Cause: Incorrect dbname string was passed or the // XA connection has not been opened // *Action: Pass the correct dbname string or check if // the XA connection is open / 32167, 00000, "No payload set on the Message" // *Cause: An attempt was made to enqueue a message without setting a // payload on it. // *Action: Set a payload on the message before calling the send method. / 32168, 00000, "Cannot perform operation on a null AnyData" // *Cause: The AnyData instance on which the operation was attempted // was null. // *Action: Use a valid, non-null AnyData instance to perform this operation. / / 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_MVIEW() 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_MVIEW() 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_MVIEW() 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_MVIEW() 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 container 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_MVIEW() 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_MVIEW() API. / 32322, 00000, "PCT refresh of \"%s\".\"%s\" not allowed the sequence of DMLs/PMOPs" // *Cause: A table join dependent on another table on which PCT refresh is // enabled has changed // *Action: Use REFRESH FORCE which will pick the best possible refresh method on // the materialized view / 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. // *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. / 32338, 00000, "on commit refresh grab all the detailed tables" // *Cause: an event is set to let on-commit MV refresh to grab all the detailed // tables, no matter whether they have modified or not. // *Action: / 32339, 00000, "cannot alter materialized view with the PMOP" // *Cause: the materialized view is not allowed to have destructive PMOPS // such as DROP, TRUNCATE and EXCHANGE (sub)partition. The UGA flag // of i_am_a_refresh should be set first. // *Action: execute set_i_am_a_refresh first before alter materialized view // with the PMOP. / 32340, 00000, "cannot tune the materialized view definition" // *Cause: Due to constructs in the materialized view definition, it // could not be tuned to be fast-refreshable or rewriteable. // *Action: Execute DBMS_MVIEW.EXPLAIN_MVIEW to determine the cause. / 32341, 00000, "The EXPLAIN_MVIEW facility failed to explain the materialized view \"%s\".\"%s\"" // *Cause: The dependent object(s) of the materialized view may have changed. // The materialized view may no longer be valid. // *Action: Execute ALTER MATERIALIZED VIEW COMPILE and to determine the status of // the materialized view in catalog views. / 32342, 00000, "The EXPLAIN_MVIEW facility failed to explain the materialized view statement" // *Cause: An error exists in the materialized view definition. As a result, // the materialized view statement could not be explained. // *Action: Check the syntax of the statement. If it is a CREATE MATERIALIZED // VIEW statement, then also check the PARAMETERs specified for the // materialized view. / 32343, 00000, "let MVIEW engine know that it is IMPORT from 9i or earlier" // *Cause: N/A. // *Action: Set this event only under the supervision of Oracle development. // Not for general purpose use. / 32344, 00000, "cannot create a secondary materialized view with synonym as base table" // *Cause: It is not supported to create a secondary materialized view with // synonym in the FROM clause. // *Action: Removed the synonym(s) from the statement. / 32345, 00000, "fail to refresh the materialized view %s.%s due to the changed synonym" // *Cause: The definition of one or more synonyms in the from clause // have changed. The structure of the materialized view has become // invalid. // *Action: Restore the synonym(s) or drop the materialized view and recreate // it again. / 32346, 00000, "ON COMMIT materialized view refresh caused changes to the master table/materialized view" // *Cause: ON COMMIT refresh of a read-only materialized view changed the master table/materialized view. // A trigger on the refreshed materialized view may be the cause. // *Action: Do not create triggers on materialized view which update the master table/materialized view. / 32347, 00000, "NULL capabilities during explain mview " // *Cause: The supplied defining query did not generate any capabilities // information. // *Action: Replace the query since it is not suitable for creating a // materialized view. / 32348, 0000, "revalidate summary object based on user input" // *Cause: An event was set to specify the number of attempts that the system // needed to make in order to validate an invalidated summary object. // // *Action: Revalidate an invalidated summary object based on user input. / 32349, 00000, "cannot reference prebuilt table in definition query for materialized view" // *Cause: The prebuilt container table of the materialized view was // referenced in the definition query. // *Action: Change the definition query to reference a non-prebuilt table. / 32350, 00000, "ON COMMIT refresh obtain shared lock for all the detailed tables" // *Cause: An event was set to let ON COMMIT materialized view refresh to // obtain a shared lock for all the detailed tables, whether they // have been modified or not. // *Action: No action necessary. / 32351, 00000, "database link name cannot start with a number while creating materialized view" // *Cause: This event was disabled by default. If enabled, the fix for bug // 6074902 will be disabled and you will be unable to create database // links starting with a number when creating a materialized view // on remote tables. // *Action: No action necessary. / // Error Numbers 32400 - 32479 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. / 32405, 00000, "cannot alter tablespace for existing materialized view log" // *Cause: The tablespace specification for the existing materialized view log // cannot be altered or changed. // *Action: remove the tablespace clause from the statement. / 32406, 00000, "cannot alter partitioning for existing materialized view log" // *Cause: The partitioning specification for the existing materialized view log // cannot be altered or changed. // *Action: remove the partitioning clause from the statement. / 32407, 00000, "cannot exclude new values when materialized view log includes new values" // *Cause: The excluding new values specification for the existing // materialized view log cannot be accepted when including new // values is the current option. // *Action: change excluding new values clause. / 32408, 0000, "materialized view log on \"%s\".\"%s\" already has new values" // *Cause: The materialized view log on the indicated table already has new values. // *Action: No action required. / 32409, 0000, "materialized view log on \"%s\".\"%s\" already excludes new values" // *Cause: The materialized view log on the indicated table already excludes new values. // *Action: No action required. / 32410, 0000, "internal mv logging event" // *Document: NO // *Cause: N/A // *Action: To be used only under supervision of Oracle development. // *Comment: Not for general purpose use. / 32411, 0000, "materialized view definition query exceeds the maximum length" // *Cause: The materialized view definition query exceeds the 64K limit. // *Action: Change the materialized view definition query so that it does not exceed // the maximum length of 64K. / 32412, 00000, "encrypted column \"%s\" not allowed in the materialized view log" // *Cause: The materialized view log being created/altered is to capture an encrypted // column of the base table. // *Action: Do not capture the encrypted column. / 32413, 00000, "allow concurrent refresh of materialized view and truncate" // *Cause: This event is set to allow concurrent refresh of materialized view // and truncate of base table; it prevents a deadlock situation. // (bug 6710019) // *Action: Set this event to allow concurrent refresh of materialized view // and truncate of the base table. / 32414, 00000, "materialized view logs are not compatible with each other for fast refresh" // *Cause: An attempt was made to create a fast refreshable materialized view // on tables which have commit SCN-based materialized view logs and // tables which have timestamp-based materialized view logs. // *Action: Use COMPLETE REFRESH or change underlying materailized view logs // to make them compatible with each other for fast refresh. / 32415, 0000, "fast refreshable remote materialized view on a detail table with commit SCN-based materialized view log is not supported" // *Cause: The materialized view creation failed because fast refreshable // remote materialized view on a detail table with commit SCN-based // materialized view log was not supported. // *Action: NONE. / 32416, 0000, "one or more commit SCN-based materialized view logs are not in consistent state for fast refresh" // *Cause: Dictionary table "SYS"."SNAP_XCMT$" is not in consistent state. // *Action: No action required. // / 32417, 0000, "must use DROP MATERIALIZED VIEW LOG to drop \"%s\".\"%s\"" // *Cause: An attempt was made to drop commit SCN-based materialized view log // using a command other than DROP MATERIALIZED VIEW LOG. // *Action: No action required. // / 32418, 0000, "COMMIT SCN keyword only appears in CREATE MATERIALIZED VIEW LOG statement" // *Cause: An attempt was made to alter an existing materialized view log // to have commit SCN. // *Action: No action required. // / 32419, 0000, "on commit materialized view is not supported on detail tables with commit SCN-based materialized view logs" // *Cause: An attempt was made to create an on commit materialized view on // detail tables with commit SCN-based materialized view logs. // *Action: No action required. // / 32420, 0000, "unsupported fast refreshable materialized view defined on detail tables which have commit SCN-based materialized view logs" // *Cause: An attempt was made to create an unsupported fast refreshable materialized // view on detail tables with commit SCN based materialized view logs. // *Action: No action required. // / 32421, 0000, "commit SCN-based materialized view log is not supported on a table with LOB column(s)" // *Cause: An attempt was made to create a commit SCN-based materialized // view log on a table which has LOB column(s). // *Action: No action required. // / 32422, 0000, "commit SCN-based materialized view log cannot be created on table \"%s\".\"%s\" when there exist direct load/PMOP log entries for the table" // *Cause: An attempt was made to create a commit SCN-based materialized // view log on a table which had direct load/PMOP log entries in // sys.sumdelta$ and sys.sumpartlog$. // *Action: Refresh the table's dependent materialized views before creating // commit SCN-based materialized view log on the table. // / 32423, 0000, "commit SCN-based materialized view log cannot be dropped on table \"%s\".\"%s\" when there exist direct load/PMOP log entries for the table" // *Cause: An attempt was made to drop a commit SCN-based materialized // view log on a table which had direct load/PMOP log entries in // sys.sumdelta$ and sys.sumpartlog$. // *Action: Refresh the table's dependent materialized views before dropping // commit SCN-based materialized view log on the table. // / 32424, 0000, "materialized view log on \"%s\".\"%s\" already has this purge option" // *Cause: Materialized view log on the indicated table already has // the purge option specified. // *Action: Specify a different purge option or omit the purge option. // / 32425, 0000, "asynchronous and scheduled purge option is not allowed on commit SCN-based materialized view log" // *Cause: An attempt was made to create or alter a commit SCN-based // materialized log with asynchronous and scheduled purge option. // *Action: Specify a different purge option or omit the purge option. // / 32426, 00000, "materialized view log on \"%s\".\"%s\" in DST upgrade" // *Cause: The materialized view log was created or altered on a table // that had a Daylight Saving Time upgrade in progress. // *Action: Wait until DST upgrade finishes on the master table. // 32427, 0000, "materialized view contains unsupported NLS transformation" // *Cause: An attempt was made to create or alter materialized view // under NLS settings which transformed the materialized view's // defining query in ways not by supported by Oracle. // *Action: Contact Oracle support or workaround problem by removing NLS // settings or modifying the materialized view's defining query. // / // Error Numbers 32480 - 32499 are reserved for WITH clause errors / 32480, 00000, "SEARCH and CYCLE clauses can only be specified for recursive WITH clause elements" // *Cause: A SEARCH or a CYCLE clause was specified for a WITH clause element // that was not recursive. // *Action: Remove the SEARCH or CYCLE clause, or add recursion to the WITH // clause element. / 32481, 00000, "cycle value for CYCLE clause must be different from the non-cycle value" // *Cause: A CYCLE clause was specified for a recursive WITH query but the // cycle value was the same as the non-cycle or DEFAULT value. // *Action: Change either the cycle or the non-cycle values so that they no // longer match. / 32482, 00000, "sequence column for SEARCH clause must be different from the cycle mark column for CYCLE clause" // *Cause: A SEARCH clause and a CYCLE clause was specified for a recursive // WITH query, but the sequence column of the SEARCH clause matched // the cycle mark column of the CYCLE clause. // *Action: Change either the sequence column or the cycle mark column so that // they no longer match. / 32483, 00000, "duplicate name found in sort specification list for SEARCH clause of WITH clause" // *Cause: A SEARCH clause was specified for a recursive query with a sort // specification list which contained duplicate names. // *Action: Remove the duplicate names from the sort specification list of // the SEARCH clause. / 32484, 00000, "duplicate name found in cycle column list for CYCLE clause of WITH clause" // *Cause: A CYCLE clause was specified for a recursive query with a cycle // column list which contained duplicate names. // *Action: Remove the duplicate names from the cycle column list of // the CYCLE clause. / 32485, 00000, "element in cycle column list of CYCLE clause must appear in the column alias list of the WITH clause element" // *Cause: An element in the cycle column list of a CYCLE clause that was // specified for a recursive WITH query did not appear in the column // alias list of the WITH clause element. // *Action: Change the cycle column list to use only names which are listed // in the column alias list of the WITH clause element. / 32486, 00000, "unsupported operation in recursive branch of recursive WITH clause " // *Cause: The recursive component of the UNION ALL in a recursive WITH clause // element used an operation that was currently not supported. The // following should not be used in the recursive branch of the // UNION ALL operation: GROUP BY, DISTINCT, MODEL, grouping sets, // CONNECT BY, window functions, HAVING, aggregate functions. // *Action: Rewrite the query without the unsupported operation. / 32487, 00000, "unsupported join in recursive WITH query" // *Cause: The recursive component of a recursive WITH clause element // contained one of the following: // - A LEFT OUTER join where the right side was the recursive query name. // - A RIGHT OUTER join where the left side was the recursive query name. // - A FULL OUTER join involving the recursive query name. // *Action: Rewrite the query without the unsupported join operation. / 32488, 00000, "WITH clause element did not have a column alias list" // *Cause: A WITH clause element used the SEARCH clause or CYCLE clause or both // but did not have a column alias list specified for it. // *Action: Add a column alias list for the WITH clause query name. / 32489, 00000, "element in sort specification list of SEARCH clause did not appear in the column alias list of the WITH clause element" // *Cause: An element in the sort specification list of a SEARCH clause that // was specified for a recursive WITH query did not appear in the // column alias list of the WITH clause element. // *Action: Change the sort specification list to use only names which are // listed in the column alias list of the WITH clause element. / //////////////////////////// DIAGNOSIBILITY / Error numbers 32500 to 32549 are reserved for diagnosibility //////////////////////////// 32500, 00000, "Dirname '%s' cannot exceed '%s' 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. / 32504, 00000, "expecting one of %s, %s, %s, or %s but found %s" // *Cause: illegal value specified for create watchpoint mode // *Action: specify one of the expected modes / 32505, 00000, "too many watchpoints" // *Cause: too many watchpoints created // *Action: increase appropriate initialization parameters / 32506, 00000, "expecting one of %s, %s, or %s but found %s" // *Cause: invalid arguments provided // *Action: provide one of the expected arguments / 32507, 00000, "expecting %s but found %s" // *Cause: invalid arguments to command // *Action: provide one of the expected arguments / 32508, 00000, "no such watchpoint id" // *Cause: invalid watchpoint id // *Action: use oradebug show to list valid watchpoint ids / 32509, 00000, "watchpoint was already deleted" // *Cause: trying to delete an already deleted watchpoint // *Action: use oradebug show to list valid watchpoint ids / 32510, 00000, "cannot create watchpoint on unreadable memory" // *Cause: trying to create watchpoint on invalid address // *Action: provide a different valid address / 32511, 00000, "cannot create watchpoint in memory needed by watchpointing code" // *Cause: overlap exists between requested memory range to watch // and internal memory structures that watchpointing operations need // *Action: provide a different address range / 32512, 00000, "type '%s' is unknown" // *Cause: trying to dump an invalid type name // *Action: specify a known type / 32514, 00000, "cannot dump multiple '%s' types: structure size is unknown" // *Cause: trying to dump an invalid address // *Action: provide a different valid address / 32515, 00000, "cannot issue ORADEBUG command '%s' to process '%s'; prior command execution time exceeds %s ms" // *Cause: The process targeted to execute the ORADEBUG command was // busy executing another ORADEBUG command for a time greater // than the timeout value specified. // *Action: Increase the timeout value. / 32516, 00000, "cannot wait for process '%s' to finish executing ORADEBUG command '%s'; wait time exceeds %s ms" // *Cause: The execution of the ORADEBUG command took longer than the // the timeout value specified. // *Action: Increase the timeout value. / 32517, 00000, "cannot issue ORADEBUG command '%s' to process '%s' (prior command execution time exceeds %s ms); total wait time exceeds %s ms" // *Cause: The process targeted to execute the ORADEBUG command was // busy executing another ORADEBUG command. But, because // the total wait time for all targeted processes // exceeded the maximum wait time, the ORADEBUG command was // not issued to the target process. // *Action: Increase the timeout value. / 32518, 00000, "cannot wait for process '%s' to finish executing ORADEBUG command '%s' (waited %s ms); total wait time exceeds %s ms" // *Cause: The total wait time for all targeted processes exceeded the // maximum wait time, therefore the wait for the targeted process // to finish executing the ORADEBUG command was aborted. // *Action: Increase the timeout value. / //////////////////////////// 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. / 32577, 00000, "username must be SYS or SYSTEM" // *Cause: A user name of SYS or SYSTEM was not specified when providing // a password in the CREATE DATABASE statement. // *Action: Only passwords for the SYS and SYSTEM users can be provided // in the CREATE DATABASE statement. Re-issue the statement with // passwords for users SYS or SYSTEM. / 32578, 00000, "password for SYS already specified" // *Cause: A password for the SYS user was specified twice in the // CREATE DATABASE statement. // *Action: Re-issue the CREATE DATABASE statement with only one password // for the SYS user. / 32579, 00000, "password for SYSTEM already specified" // *Cause: A password for the SYSTEM user was specified twice in the // CREATE DATABASE statement. // *Action: Re-issue the CREATE DATABASE statement with only one password // for the SYSTEM user. / 32580, 00000, "both SYS and SYSTEM passwords must be provided" // *Cause: Passwords for both the SYS and SYSTEM users were not // provided in the CREATE DATABASE statement. If one of the // passwords was provided, then both should be provided. // *Action: Re-issue the CREATE DATABASE statement with a password for // both the SYS and SYSTEM users. / 32581, 00000, "missing or invalid password" // *Cause: An incorrect password was provided for the SYS or // SYSTEM user in the CREATE DATABASE statement. // *Action: Re-issue the CREATE DATABASE statement with a valid password. / 32582, 00000, "table function with left correlation to a table cannot also be left outer-joined to the table" // *Cause: A table function T2 contains a reference to a table T1. T2 // is also left outer-joined to T1. This is not allowed. // *Action: Remove the reference to T1 from T2 or remove the left outer-join // specification (+). / 32583, 00000, "query passed to table function has wrong number of elements in select list" // *Cause: The query used as an input to a table function which takes a // a ref cursor as argument has wrong number of elements in the select // list which does not correspond to the elements in ref cursor. // The ref cursor mentioned here refers to the one referenced in // order by parition clauses. This is not allowed. // *Action: Make sure that the select list of the query matches the ref cursor // columns as defined in the function. / 32584, 00000, "missing LOG keyword" // *Cause: keyword LOG is missing. // *Action: Use LOG keyword. / 32585, 00000, "duplicate specification of a supplemental log attribute" // *Cause: In a create/alter DDL a supplemental log attribute is specified // more than once. // *Action: Rewrite the Create/Alter DDL such that it has a // single occurence of any supplemental log attribute. / 32586, 00000, "multiple specification of a supplemental logging attribute" // *Cause: The primary key, unique index, foreign key or all // column supplemental logging attribute can be specified at most // once in a create/alter ddl. // *Action: Rewrite the Create/Alter DDL with single occurence of // the offending supplemental logging attribute. / 32587, 00000, "Cannot drop nonexistent %s supplemental logging" // *Cause: specified supplemental log attribute does not exist. // *Action: None // / 32588, 00000, "supplemental logging attribute %s exists" // *Cause: specified supplemental logging attribute exits. // *Action: retry the alter/create ddl after removing this // supplemental logging attribute. // / 32589, 00000, "unable to drop minimal supplemental logging" // *Cause: Minimal supplemental logging could not be dropped as // one of primary key, foreign key, unique or all column // supplemental logging is enabled at the database level. // *Action: Use V$DATABASE to determine the databasewide supplemental // logging directives. Minimal supplemental logging could // be dropped if and only if no other databasewide supplemental // logging directives are enabled. / 32590, 00000, "log group specification not allowed here" // *Cause: Supplemental log specification is not allowed in the // statement. // *Action: Remove the supplemental log specification from the // statement. / 32591, 00000, "connect string too long" // *Cause: The connect string specified for the database link was more than // 2000 characters. // *Action: Specify a connect string less than 2000 chracters. / 32592, 00000, "all columns in log group can not be no log columns" // *Cause: A supplemental log group must have at least one column of scalar // type that is not marked as no log. // *Action: Redefine the supplemental log group with at least one column of // scalar type that is not marked as no log. / 32593, 00000, "database supplemental logging attributes in flux " // *Cause: there is another process actively modifying the database wide // supplemental logging attributes. // *Action: Retry the DDL or the LogMiner dictionary build that raised this // error. / 32594, 00000, "invalid object category for COMMENT command" // *Cause: The object category specified is not a valid object for which to // use the COMMENT command. // *Action: Retry the COMMENT command by specifying an accepted object // category. (ie, Table, Operator, Indextype, etc.) / 32595, 00000, "DDL statement cannot be audited with BY SESSION specified" // *Cause: An attempt was made to audit a DDL statement with BY SESSION // clause specified. DDL statements can be audited BY ACCESS only. // *Action: Specify BY ACCESS instead of BY SESSION to audit the DDL // statement. / 32596, 00000, "duplicate ALTER USER or CREATE USER option" // *Cause: An ALTER USER option was duplicated. // *Action: Remove the duplicate option. / 32597, 00000, "database supplemental logging attributes inconsistent" // *Cause: failed to propogate supplemental logging attributes to all // RAC instances. Most likely caused by an instance leaving // the RAC while this DDL was in progress. // *Action: Retry the DDL or the LogMiner dictionary build that raised // this error. / 32598, 00000, "user names cannot be changed in ALTER DATABASE LINK command" // *Cause: An attempt was made to change the fixed user name of the // database link. // *Action: None. / //////////////////////////// LOB RETENTION and FLASHBACK / Error numbers 32600 to 32605 are reserved for lob retention //////////////////////////// 32600, 00000, "RETENTION and PCTVERSION cannot be used together" // *Cause: cannot use both RETENTION and PCTVERSION together. // *Action: Use either RETENTION or PCTVERSION. / 32601, 00000, "value for retention cannot be provided" // *Cause: cannot give a value for Retention Period. // *Action: do not provide the value for parameter. / 32602, 00000, "FREEPOOLS and FREELIST GROUPS cannot be used together" // *Cause: cannot use both FREEPOOLS and FREELIST GROUPS together. // *Action: Use either FREEPOOLS or FREELIST GROUPS. / 32603, 00000, "invalid FREEPOOLS LOB storage option value" // *Cause: The specified FREEPOOLS LOB storage option value must be an // integer. // *Action: Choose an appropriate integer value and retry the operation. / 32604, 00000, "invalid REBUILD option" // *Cause: Keyword FREEPOOLS expected after the REBUILD keyword. // *Action: User must specify FREEPOOLS keyword. / 32605, 00000, "invalid REBUILD option" // *Cause: cannot rebuild freepools while creating table with lob column. // *Action: User must not specify REBUILD... in this context. / //////////////////////////// MODEL / Error numbers 32606 to 32689 are reserved for MODEL //////////////////////////// 32606, 00000, "missing NAV keyword in MODEL clause" // *Cause: The NAV keyword was specified where it is expected. // *Action: Specify the NAV keyword or check the SQL statement. / 32607, 00000, "invalid ITERATE value in MODEL clause" // *Cause: The specified ITERATE value must be a 4 byte positive integer. // *Action: Choose an appropriate value and retry the operation. / 32608, 00000, "missing INCREMENT or DECREMENT keyword in FOR loop" // *Cause: INCREMENT or DECREMENT keyword was not specifiedi where it is expected. // *Action: Specify the INCREMENT or DECREMENT keyword or check the SQL statement. / 32609, 00000, "missing REFERENCE keyword in MODEL clause" // *Cause: The REFERENCE keyword was not specified where it is expected. // *Action: Specify the REFERENCE keyword or check the SQL statement. / 32610, 00000, "missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause" // *Cause: SINGLE REFERENCE or DIMENSION keyword was not specified where it is // expected. // *Action: Specify the applicable keywords or check the SQL statement. / 32611, 00000, "incorrect use of MODEL CV operator" // *Cause: CV function was used outside a dimension expression, in UNTIL // condition, or with non-dimensional arguments. // *Action: Check the SQL statement and rewrite if necessary. / 32612, 00000, "invalid use of FOR loop" // *Cause: The MODEL FOR loop was used where it is not allowed. // FOR loops are not allowed in complex dimensional predicates, // on the right hand side of rules, or in the until condition. // *Action: Check the SQL statement and rewrite if necessary. / 32613, 00000, "not a MODEL cell" // *Cause: The operator requires a MODEL cell as operand. // *Action: Specify MODEL cell as operand, check SQL statement. / 32614, 00000, "illegal MODEL SELECT expression" // *Cause: An expression other than MODEL aliases, constants, // or expressions of the two is specified in the // MODEL SELECT clause. // *Action: Reformulate the query, perhaps nesting inside another SELECT. / 32615, 00000, "incorrect use of MODEL IS ANY predicate" // *Cause: IS ANY predicate is used outside dimension expression or with // non-dimensional or different dimensional arguments. // *Action: Check the SQL statement and rewrite if necessary. / 32616, 00000, "missing DIMENSION BY keyword in MODEL clause" // *Cause: The DIMENSION keyword was not pecified where it is expected. // *Action: Specify the DIMENSION keyword or check the SQL statement. / 32617, 00000, "missing MEASURES keyword in MODEL clause" // *Cause: The MEASURES keyword was not specified where it is expected. // *Action: Specify the MEASURES keyword or check the SQL statement. / 32618, 00000, "incorrect use of MODEL PREVIOUS function" // *Cause: The MODEL PREVIOUS function was used outside of MODEL // "ITERATE UNTIL" clause, or was nested. // *Action: Check the SQL statement and rewrite if necessary. / 32619, 00000, "incorrect use of MODEL ITERATION_NUMBER" // *Cause: ITERATION_NUMBER was used outside of an iterated MODEL. // *Action: Check the SQL statement and rewrite if necessary. / 32620, 00000, "illegal subquery within MODEL rules" // *Cause: A subquery was used illegally within the MODEL rule. // *Action: Check the SQL statement and rewrite if necessary. / 32621, 00000, "illegal aggregation in UNTIL iteration condition" // *Cause: An aggregate function was used in UNTIL condition. // *Action: Check the SQL statement and rewrite if necessary. / 32622, 00000, "illegal multi-cell reference" // *Cause: Multi-cell reference was specified on a measure expression // without an aggregate function. // *Action: Use an aggregate function on the measure expression or // qualify the cell reference. / 32623, 00000, "incorrect use of MODEL PRESENT* functions" // *Cause: A PRESENT* function (IS PRESENT, PRESENTV, PRESENTNNV) // was used in a measure expression. // *Action: Check the SQL statement and rewrite if necessary. / 32624, 00000, "illegal reordering of MODEL dimensions" // *Cause: The expressions to qualify dimensions were specified // in an incorrect order within a cell reference. // *Action: Reorder dimension expressions in the cell reference. / 32625, 00000, "illegal dimension in cell reference predicate" // *Cause: A non-positional dimension was referenced in the predicate. // *Action: Check the SQL statement and rewrite if necessary. / 32626, 00000, "illegal bounds or increment in MODEL FOR loop" // *Cause: FOR loop allows only numeric and datetime without timezone type // for bounds. Only constants of interval and numeric types are // allowed as increment/decrement expressions. // *Action: Check the SQL statement and rewrite if necessary. / 32627, 00000, "illegal pattern in MODEL FOR LIKE loop" // *Cause: The FOR LIKE pattern had zero or more than one wild characters. // *Action: Simplify the pattern to have a single wildcard character. / 32628, 00000, "invalid nesting of MODEL cell reference" // *Cause: MODEL cell reference was nested too deeply. // *Action: Avoid deep nesting of cell references and rewrite if necessary. / 32629, 00000, "measure used for referencing cannot be updated" // *Cause: A measure used in nested referencing is updated by a MODEL // rule in the automatic order MODEL. // *Action: Modify the SQL statement or use sequential order MODEL. / 32630, 00000, "multiple assignment in automatic order MODEL" // *Cause: A MODEL cell was updated on the same measure in // multiple MODEL rules. Multiple assignment is not allowed // in automatic order MODELs as it causes in ambiguity // and nondeterminism. // *Action: Use sequential order MODEL or rewrite the rule to avoid this. / 32631, 00000, "illegal use of objects in MODEL" // *Cause: An object column was used as a MODEL column. Object types are // not allowed as partition by, dimension by or measure expressions. // *Action: Check the SQL statement and rewrite if necessary. / 32632, 00000, "incorrect subquery in MODEL FOR cell index" // *Cause: An illegal subquery was specified in MODEL FOR cell index. // A subquery used in a MODEL FOR cell index can not have // subqueries, correlation, binds and references to WITH tables. // *Action: Check the SQL statement and rewrite if necessary. / 32633, 00000, "MODEL subquery FOR cell index returns too many rows" // *Cause: Subquery in MODEL FOR cell index returned more than // the allowed maximum. // *Action: Split the rule into multiple ones. / 32634, 00000, "automatic order MODEL evaluation does not converge" // *Cause: Evaluation using automatic rule ordering did not reach // a convergence point. // *Action: Modify the rules or use sequential order instead. / 32635, 00000, "not a single cell reference predicate" // *Cause: A predicate that is not a single cell reference predicate was specified // where a single cell reference predicate was expected. // A single cell reference predicate is either a constant expression // or a predicate of the form // *Action: Make sure that the predicate is a proper single cell // reference. In some cases, you might have to put explicit // type conversion operators (or casts) on the constant expression. / 32636, 00000, "Too many rules in MODEL" // *Cause: The number of rules (possibly after rule unfolding) exceeded // the maximum number of rules allowed. // *Action: Reduce the number of rules. / 32637, 00000, "Self cyclic rule in sequential order MODEL" // *Cause: A self-cyclic rule was detected in the sequential order MODEL. // Sequential order MODELs cannot have self cyclic rules // to guarantee that the results do not depend on the order // of evaluation of the cells that are updated or upserted. // *Action: Use ordered rule evaluation for this rule. / 32638, 00000, "Non unique addressing in MODEL dimensions" // *Cause: The address space defined for the MODEL (partition by and dimension by // expressions) do not uniquely identify each cell. // *Action: Rewrite the MODEL clause. Using UNIQUE SINGLE REFERENCE // option might help. / 32639, 00000, "Aggregate functions on reference MODELs are not allowed" // *Cause: An aggregate function was specified on the cells of a reference // MODEL. // *Action: Check the SQL statement and rewrite if necessary. / 32640, 00000, "FOR LIKE loops are not allowed for multi-byte character types" // *Cause: FOR LIKE loops was specified for a multi-byte character type. // *Action: Check the SQL statement and rewrite if necessary. / 32641, 00000, "invalid expression in MODEL rule ORDER BY clause" // *Cause: An invalid expression was specified in the MODEL rule ORDER BY clause // where only expressions of dimension and measure columns and // reference MODEL cell references are allowed // *Action: Modify the order by clause in the MODEL rule. / 32642, 00000, "non-unique cell values from the ORDER BY clause" // *Cause: The MODEL rule ORDER BY clause did not generate unique values for all // cells that satisfy the predicates in the left side of the rule. // *Action: Modify the rule ORDER BY clause in the MODEL rule. / 32643, 00000, "invalid use of window function in MODEL rule" // *Cause: The window functions can not be used in SQL Model rules // that have FOR-loops on the left side or aggregates // on the right side. // *Action: Modify the MODEL rule. / 32644, 00000, "this function is not allowed outside of MODEL clause" // *Cause: A function allowed only within the MODEL clause is used // outside of MODEL clause. // *Action: Rewrite the SQL statement. / 32689, 00000, "MODEL: event to turn on/off some optimizations" // *Document: NO // *Cause: N/A // *Action: Turns on/off some optimizations in MODEL evaluation. / //////////////////////////// Hash Table Infrastructure (HTI) / Error numbers 32690 to 32699 are reserved for hash table infrastructure //////////////////////////// / 32690, 00000, "Hash Table Infrastructure ran out of memory" // *Cause: Not enough memory. // *Action: Increase memory. / 32695, 00000, "HTI: Not enough memory" // *Cause: Memory is not enough. // *Action: Increase memory. / 32696, 00000, "HTI: No free slot" // *Cause: There is not enough memory. // *Action: Increase memory. / 32697, 00000, "HTI: max agg size" // *Document: NO // *Cause: N/A // *Action: Sets max nda size / 32698, 00000, "Overshoot in index scan prefetch" // *Document: NO // *Cause: N/A // *Action: / 32699, 00000, "HTI: event to dump statistics" // *Document: NO // *Cause: N/A // *Action: Dumps hash infrastructure statistics / ////////////////////////////// RAC DIAGNOSABILITY FRAMEWORK // Error numbers 32700 to 32729 are reserved for RAC DIAG process ////////////////////////////// 32700, 00000, "error occurred in DIAG Group Service" // *Cause: An unexpected error occurred while performing a DIAG Group Service // operation. // *Action: Verify that the DIAG process is still active. Also, check the // Oracle DIAG trace files for errors. / 32701, 00000, "Possible hangs up to hang ID=%s detected" // *Cause: Hang Manager detected one or more hangs. These could be valid // hangs that require action or the system could be overloaded causing // very slow progress which can be interpreted as hangs. If hang // resolution is enabled, Hang Manager may attempt to resolve // the hang by terminating the ultimate blocker. // *Action: Check the incident logs associated with this message for // diagnostic information. / 32702, 00000, "Rolling migration is going on" // *Cause: DIAG detected rolling migration in IPC. // *Action: No action needed. DIAG is shutting down for rolling migration. // This error number is solely used for internal purposes. / 32703, 00000, "deadlock detected: %s" // *Cause: Oracle sessions waiting for resources were deadlocked. // *Action: Reissue any commands that failed and contact Oracle Support // Services with the incident information. / ////////////////////////////// RAC DIAG-based parallel oradebug // Error numbers 32730 to 32760 are reserved for DIAG-based parallel oradebug ////////////////////////////// 32730, 00000, "Command cannot be executed on remote instance" // *Cause: DIAG is not registered with DIAG Group Service // *Action: Issue the command without the cluster database syntax / 32731, 00000, "Another Parallel Oradebug session is in progress" // *Cause: Another session for Parallel Oradebug is in progress // with the database // *Action: Issue the command later when the current session finishes / 32732, 00000, "Parallel Oradebug session is aborted" // *Cause: Group reconfiguration is occurring among DIAGs // *Action: Issue the command later when group reconfiguration completes / 32733, 00000, "Error occurred when executing Parallel Oradebug" // *Cause: Error is encountered during executing command at local node // *Action: Check alert log and DIAG trace file for error detail / 32734, 00000, "Error occurred when sending Oradebug command to remote DIAGs" // *Cause: IPC communication problem encountered // *Action: Check IPC communication between DIAGs and issue the command again / at a later time 32735, 00000, "DIAG process is not running in the instance" // *Cause: DIAG process is not alive // *Action: Check error in DIAG trace file and issue the command again // when DIAG is restarted / 32736, 00000, "Hang analysis aborted due to wrong message type" // *Cause: DIAG received wrong message. // *Action: Check DIAG trace files for errors. / 32737, 00000, "Hang analysis aborted due to failed memory allocation" // *Cause: DIAG couldn't allocate buffer for remote copy. // *Action: Check DIAG trace files for errors. / 32738, 00000, "Hang analysis aborted due to failed memory copy" // *Cause: DIAG couldn't copy buffer to remote node. // *Action: Check DIAG trace files for errors. / 32739, 00000, "Hang analysis aborted due to failed heap re-grow" // *Cause: DIAG couldn't re-grow the heap for wait-for-graphs. // *Action: Check DIAG trace files for errors. / 32740, 00000, "The requested operation cannot be proceeded" // *Cause: Operation was aborted because instance termination was in progress. // *Action: Retry later after restarting the instance. / 32741, 00000, "Hang analysis already going on" // *Cause: Hang analysis was already in process globally or for the instance. // *Action: Wait for the current operation to complete and re-run the command. / 32742, 00000, "Hang analysis initialize failed" // *Cause: Hang analyzer was not able to allocate memory to initialize. // *Action: Check the trace files. / 32743, 00000, "command cannot be executed on remote instance" // *Cause: The database was not mounted in SHARED mode. // *Action: Mount the database in SHARED mode. / ////////////////////////////// Temp LOB Ref Count // Error numbers 32761 to 32765 are reserved for Temp LOB Ref Count tracing ////////////////////////////// 32761, 00000, "Turn off Temp LOB Ref Count Feature " // *Cause: None // *Action: Turn off the whole temp lob ref count feature 32762, 00000, "Turn on Temp LOB Ref Count Tracing " // *Cause: None // *Action: Check Trace file for debug info 32763, 00000, "Turn off N-Pass Temp LOB cleanup " // *Cause: None // *Action: Facilitate debugging and testing ////////////////////////////// SQL function on LOBs // Error numbers 32766 to 32770 are reserved for SQL function on LOBs ////////////////////////////// 32766, 00000, "instr with negative offset: use varchar semantics on LOBs" // *Cause: The current varchar behavior is different. // e.g. instr('abcd', 'cd', -2, 1) returns 3, whereas // instr(to_clob('abcd'), 'cd', -2, 1) returns 0, (i.e. no match), // because the reverse search starts from offset -2, which points // to 'c' and moving backward, i.e. 'd' is ignored. // This is symmetric to instr('dcba','dc',2,1), which returns 0. // *Action: ORACLE uses the same varchar semantics on LOBs (instr). // Using the same example, instr(to_clob('abcd'), 'cd', -2, 1) // will return 3 as in the varchar case. / / 32767, 00000, "No server connection for this operation" // *Cause: The client side sql or plsql function operation requires // a connection to the server, but currently no client/server // connection existed. // // *Action: Establish a client/server connection. / / ////////////////////////////// BIGFILE TABLESPACE // Error numbers 32771 to 32779 are reserved for Bigfile Tablespace ////////////////////////////// 32771, 00000, "cannot add file to bigfile tablespace" // *Cause: An attempt was made to add the second file to a bigfile // tablespace. // *Action: Do not use this command with bigfile tablespace. 32772, 00000, "BIGFILE is invalid option for this type of tablespace" // *Cause: An attempt was made to create a bigfile tablespace that is // dictionary managed or locally managed with manual // segment-space management. // *Action: Either change the tablespace type to locally managed with // automatic segment-space management, or create a SMALLFILE // tablespace instead. 32773, 00000, "operation not supported for smallfile tablespace %s" // *Cause: An attempt was made to perform an operation which is supported // only for bigfile tablespaces, e.g. resize tablespace. // *Action: Use the appropriate clause of the ALTER DATABASE DATAFILE // command instead. 32774, 00000, "more than one file was specified for bigfile tablespace %s" // *Cause: More than one datafile or tempfile was specified in CREATE // TABLESPACE command for a bigfile tablespace. // *Action: Change command to contain only one file or create a smallfile // tablespace instead. 32775, 00000, "cannot change size attributes of read only tablespace %s" // *Cause: An attempt was made to change size attributes of a tablespace // that is read only. // *Action: Change the tablespace to read/write and retry the operation. / / // ////////////////////////// // 32780 - 32789 reserved for window function events // ////////////////////////// / 32780, 00000, "Analytical Functions: event to turn on or off optimizations" // *Document: NO // *Cause: N/A // *Action: Turns on or off some optimizations in OLAP analytical // function evaluation // Level: // 0x01 - turn off reporting aggregate optimization // 0x02 - turn off nosort rank pushdown/stopkey optimization // 0x04 - turn off range parallelism for cumulative window fns // 0x08 - turn off new sort in window functions // 0x10 - turn off ordering key minimization // 32781, 00000, "Trace window function ordering semantics rewrite" // *Cause: N/A // *Action: Set this event only under the supervision of Oracle development. // Trace level is a bitfield. // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 trace / // ////////////////////////// // Schema compiler error // ////////////////////////// / 32790, 00000, "Element '%s' cannot share the default table '%s' with element '%s'" // *Cause: An element in the restriction shared a default table with the // corresponding element in it's supertype. // *Action: Change the default table's name for the element in restriction. / / //////////////// / 32800 - 32999 are reserved for Messaging Gateway (MGW) / Used by DBMS_MGWADM package and other related packages and types. / //////////////// / //////////// OLAP framework / Error numbers 33000 to 38000 are reserved for OLAP work. / / End of File - Add errors from e38001.msg. Consult errorinf.txt / 65535 - (MAX ERROR NUMBER; NONE CAN BE LARGER) / / /********************************************************************* / / 32800 - 32999 reserved for Oracle Messaging Gateway (MGW) / These errors are used for DBMS_MGWADM package and related types. / /********************************************************************* / 32800, 00000, "internal error %s" // *Cause: An unexpected error occurred. // *Action: Contact Oracle Support Services. / 32801, 00000, "invalid value %s for %s" // *Cause: An invalid value was specified for a parameter. // *Action: Specify a valid value for the parameter. / 32802, 00000, "value for %s must be %s" // *Cause: An invalid value was specified for a parameter. // *Action: Specify the value as indicated by the message. / 32803, 00000, "value for %s cannot be altered" // *Cause: An attempt was made to alter a value that cannot be altered. // *Action: Retry the operation without altering the indicated value. / 32804, 00000, "invalid value %s, %s should have form %s" // *Cause: A value specified for a parameter has the incorrect form. // *Action: Specify a string of the correct form. / 32805, 00000, "identifier for %s too long, maximum length is %s characters" // *Cause: An identifier string exceeded the maximum allowed length. // *Action: Specify a string whose length is less than the maximum allowed // length. / 32806, 00000, "value for %s is too long, maximum length is %s" // *Cause: A value exceeded it's maximum allowed length. // *Action: Specify a value whose length is less than the maximum allowed // length. / 32807, 00000, "message system link %s already exists" // *Cause: A message system link of the specified name already exists. // *Action: Specify a different name. / 32808, 00000, "message system link %s does not exist" // *Cause: A message system link of the specified name does not exist. // *Action: Specify a message system link name that already exists. / 32809, 00000, "foreign queue %s is already registered" // *Cause: The foreign queue has already been registered for this message // system link (NAME@MSGLINK). // *Action: Specify a different name that is not being used for this // message system link. / 32810, 00000, "foreign queue %s is not registered" // *Cause: The foreign queue (NAME@MSGLINK) has not been registered for // this message system link. // *Action: Specify the name of a registered foreign queue. / 32811, 00000, "subscriber %s already exists" // *Cause: The specified subscriber identifier already exists. // *Action: Specify a different identifier. / 32812, 00000, "subscriber %s does not exist" // *Cause: The specified subscriber identifier does not exist. // *Action: Specify an existing subscriber identifier. / 32813, 00000, "propagation schedule %s already exists" // *Cause: The specified propagation schedule identifer already exists. // *Action: Specify a different identifier. / 32814, 00000, "propagation schedule %s does not exist" // *Cause: The specified propagation schedule identifier does not exist. // *Action: Specify a schedule identifier that already exists. / 32815, 00000, "message system link %s is referenced by a foreign queue" // *Cause: An attempt was made to remove a message system link currently // referenced by one or more registered foreign queues. // *Action: Unregister all foreign queues using this message system link // and retry the operation. / 32816, 00000, "foreign queue %s is referenced by a subscriber or schedule" // *Cause: An attempt was made to unregister a foreign queue currently // referenced by one or more subscribers or propagation schedules. // *Action: Remove all subscribers and propagation schedules using this // foreign queue and retry the operation. / 32817, 00000, "message system link %s is not configured with a log queue for %s" // *Cause: An attempt was made to add a propagation subscriber but the // message system link was not configured with a log queue for the // indicated propagation type. // *Action: Alter the message system link to configure the link with a log // queue for this propagation type. / 32818, 00000, "AQ queue %s does not exist" // *Cause: An operation was attempted where the specified AQ queue // does not exist. // *Action: Specify the name of an existing AQ queue. / 32819, 00000, "AQ queue %s must be a normal queue" // *Cause: An operation was attempted where the specified AQ queue exists // but is not a normal queue. // *Action: Specify the name of an AQ queue which was created as a normal // queue (NORMAL_QUEUE). / 32820, 00000, "subscriber queue and exception queue must use same message system link" // *Cause: An operation was attempted for INBOUND propagation where the // specified subscriber queue and exception queue reference // different message system links. // *Action: Specify an exception queue that is a registered foreign queue // of the same message system link as the subscriber queue. / 32821, 00000, "subscriber queue and exception queue must have same payload type" // *Cause: An operation was attempted for OUTBOUND propagation where the // AQ queues used for the subscriber queue and exception queue // have different payload types. // *Action: Specify an exception queue that has the same payload type as // the subscriber queue. / 32822, 00000, "subscriber %s is marked for removal" // *Cause: An administration operation was attempted for a subscriber which // is marked for removal. If attempting to remove a subscriber, the // Messaging Gateway agent is not running or is running but unable // to remove the subscriber at this time. // *Action: Do not issue propagation administration commands for a subscriber // for which removal is pending. Wait for the subscriber to be // removed by the agent or issue REMOVE_SUBSCRIBER with the FORCE // option to force the subscriber to be removed. / 32823, 00000, "subscriber exists for queue %s and destination %s" // *Cause: An attempt was made to create a propagation subscriber when one // already exists for the specified queue and destination pair. // *Action: Specify a different queue and destination pair, or remove the // subscriber using that pair and retry the operation. / 32824, 00000, "schedule exists for source %s and destination %s" // *Cause: An attempt was made to create a propagation schedule when one // already exists for the specified source and destination pair. // *Action: Specify a different source and destination pair, or remove the // schedule using that pair and retry the operation. / 32825, 00000, "Messaging Gateway agent has not been started" // *Cause: An attempt was made to shut down the Messaging Gateway agent when // it is not started. // *Action: No action required. / 32826, 00000, "Messaging Gateway agent has already been started" // *Cause: An attempt was made to start the Messaging Gateway agent when // it is already started. // *Action: No action required. / 32827, 00000, "Messaging Gateway agent must be shut down" // *Cause: An operation was attempted that requires the Messaging Gateway // agent to be shut down. // *Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to show a NOT_STARTED // status, and retry the operation. CLEANUP_GATEWAY may need to be // issued to reset the gateway state if the agent fails to shut down // after a reasonable time period. / 32828, 00000, "Messaging Gateway agent must be running" // *Cause: An operation was attempted that requires the Messaging Gateway // agent to be started and responsive. // *Action: Issue STARTUP, wait for MGW_GATEWAY view to show a RUNNING status, // and retry the operation. / 32829, 00000, "Messaging Gateway agent cannot be shut down while it is starting" // *Cause: An attempt was made to shut down the Messaging Gateway agent when // it is in the process of starting and initializing. // *Action: Wait for MGW_GATEWAY view to show a RUNNING status and retry the // operation. CLEANUP_GATEWAY may need to be issued to reset the // gateway state if the agent fails to start after a reasonable // time period. / 32830, 00000, "result code %s returned by Messaging Gateway agent" // *Cause: The Messaging Gateway agent terminated abnormally due to an // unexpected error. // *Action: Review the Messaging Gateway log file for further information // regarding the problem. Resolve the problem and start the // Messaging Gateway agent. Contact Oracle Support Services if // the problem cannot be resolved. / 32831, 00000, "timed out trying to acquire administration lock" // *Cause: A timeout occurred when attempting an administration operation. // Either an administration operation was attempted while the // Messaging Gateway agent was starting and initializing, or // two administration operations were attempted at the same time. // *Action: Retry the operation. If the Messaging Gateway agent is starting, // wait for MGW_GATEWAY view to show a RUNNING status and retry the // operation. / 32832, 00000, "failure %s trying to acquire administration lock" // *Cause: An unexpected error occurred trying to acquire administration lock. // *Action: Retry the operation. Contact Oracle Support Services if the error // persists. / 32833, 00000, "failure %s trying to release administration lock" // *Cause: An unexpected error occurred trying to release administration lock. // *Action: Contact Oracle Support Services if the error persists. / 32834, 00000, "Messaging Gateway agent user has not been set" // *Cause: A Messaging Gateway agent user has not been configured. // *Action: Create a database user having role MGW_AGENT_ROLE and issue // DB_CONNECT_INFO to configure an agent user. / 32835, 00000, "database user %s does not exist" // *Cause: The specified database user does not currently exist. // *Action: Create the user and grant all necessary privileges and roles. / 32836, 00000, "database user %s must be granted role %s" // *Cause: The specified database user does not have a required role. // *Action: Grant the user the indicated role. / 32837, 00000, "invalid configuration state %s" // *Cause: The specified configuration state is invalid. // *Action: Remove and re-create the configured entities. Contact Oracle // Support Services if the problem cannot be identified or resolved. / 32838, 00000, "exceeded maximum number of properties" // *Cause: An attempt was made to alter a property list where the number // of properties in the resulting list exceeds the maximum allowed. // *Action: Order the elements of the alter list differently so the number // of elements in the resulting list is less than the maximum. / 32839, 00000, "property %s is reserved, names with MGWPROP$_ prefix are not valid" // *Cause: An attempt was made to specify a reserved name for a property name. // *Action: Use a non-reserved name. / 32840, 00000, "property name cannot be NULL" // *Cause: An attempt was made to use NULL for a property name. // *Action: Specify a non-NULL name. / 32841, 00000, "invalid value for property %s" // *Cause: An attempt was made to specify an invalid value for a property. // *Action: Specify a valid property value. / 32842, 00000, "value for property %s cannot be altered" // *Cause: An attempt was made to alter a property that cannot be altered. // *Action: Retry the operation without altering the indicated property. / 32843, 00000, "value for %s is outside the valid range of %s to %s" // *Cause: A value was specified that is not in the valid range. // *Action: Specify a value within the indicated range. / 32844, 00000, "exceeded maximum number of %s values" // *Cause: An attempt was made to add a value of the specified type but // the maximum number of such values has been reached. // *Action: No action required. / 32845, 00000, "Messaging Gateway agent is already running" // *Cause: An attempt was made to start the Messaging Gateway agent // when an agent instance is already running. // *Action: Shut down the Messaging Gateway agent currently running, // verify the agent process has been terminated, and start // the Messaging Gateway agent. / 32846, 00000, "Messaging Gateway agent cannot be started; status is %s" // *Cause: An attempt to start the Messaging Gateway agent failed due to // the indicated agent status. A BROKEN status indicates a problem // that requires user intervention before the agent can be started. // *Action: Review the MGW_GATEWAY view and the Messaging Gateway log file // for further information. Resolve the problem and start the // Messaging Gateway agent. Contact Oracle Support Services if // the problem cannot be resolved. / 32847, 00000, "operation is not supported on this platform" // *Cause: An attempt was made to perform an operation that is not // supported on this platform. // *Action: Switch to a platform on which the operation is supported. / 32848, 00000, "foreign queue DOMAIN required for JMS unified connections" // *Cause: A DOMAIN was not specified when registering a foreign queue // for a messaging system link that is configured to use the // JMS unified messaging model. // *Action: Specify a non-NULL value for the DOMAIN parameter. / 32849, 00000, "%s cannot be set unless %s is set" // *Cause: An attempt was made to specify a value for a parameter that // cannot be set unless an associated parameter is also set. // *Action: Specify a valid value for both parameters, or, do not specify // a value for either parameter. / 32850, 00000, "agent %s does not exist" // *Cause: The specified Messaging Gateway agent name did not exist. // *Action: Specify an existing agent name. / 32851, 00000, "agent %s already exists" // *Cause: The specified Messaging Gateway agent name already existed. // *Action: Specify a different agent name. / 32852, 00000, "agent %s is referenced by a message system link" // *Cause: An attempt was made to remove a Messaging Gateway agent // currently referenced by one or more message system links. // *Action: Remove all message system links associated with this agent // and retry the operation. / 32853, 00000, "propagation job %s does not exist" // *Cause: The specified propagation job identifier did not exist. // *Action: Specify an existing identifier. / 32854, 00000, "propagation job %s already exists" // *Cause: The specified propagation job identifier already existed. // *Action: Specify a different identifier. / 32855, 00000, "propagation job %s is marked for removal" // *Cause: An administration operation was attempted for a propagation job // which is marked for removal. If attempting to remove a job, the // Messaging Gateway agent is not running or is running but unable // to remove the job at this time. // *Action: Do not issue propagation administration commands for a job // for which removal is pending. Wait for the job to be removed // by the agent, or, issue REMOVE_JOB with the FORCE option to // force the job to be removed. / 32856, 00000, "operation not supported for propagation job" // *Cause: An attempt was made to perform an operation that was not // supported for a propagation job. // *Action: Perform the operation using a propagation job procedure. / 32857, 00000, "propagation job exists for source %s and destination %s" // *Cause: An attempt was made to create a propagation job, subscriber, // or schedule when a propagation job already existed for the // specified source and destination pair. // *Action: Specify a different source and destination pair, or remove the // propagation job using that pair and retry the operation. / // // Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved. // // NAME // olap33k.msg - OLAP messages in the 33,000 range // // DESCRIPTION // Provides the OLAP error messages for inclusion in the RDBMS // // NOTES // Concatenated with other files to build the RDBMS message file // If you change this: // cd rdbms/mesg // gmake concat // gmake oraus.msb // // MODIFIED (MM/DD/YY) // smierau 01/28/11 - Backport smierau_bug-10432704 from main // smierau 01/20/11 - Add 35585 for _XSRWLD14_ // ghicks 01/04/11 - Backport ghicks_dimshow_for_partition_templates from // main // almurphy 04/01/10 - add 36145 for _XSSETPROP01_ // ckearney 03/31/10 - add error 37421 // ghicks 03/17/10 - add XSSPROPNA // ckearney 02/05/10 - remove "bytes" from error 33674 // byu 01/15/10 - Add extra text to 35571 to make it more meaningful // ruqtang 01/11/10 - remove XSAGDNGL46 // jdhunter 12/17/09 - Bug 8572767: OBJORG errors (37093-37099, 37166-37170) // csperry 10/01/09 - Add 37575-37577 Invalid oplog component specified // cchiappa 04/06/09 - Add sparsity advisor unexpected change message // ckearney 03/26/09 - add EXPRESS AW errors 37580 to 37582 // ghicks 03/10/09 - _MXDSS18_, tinker with _MXDSS25_ wording // ghicks 02/09/09 - _MXDSS25_ // wechen 02/04/09 - Add 37553, 37554 // ckearney 01/27/09 - _XSTFDSC06_ // ghicks 01/06/09 - _MXDSS28_ // cchiappa 12/17/08 - Add 37171: invalid number to SIGNAL // cjohnson 12/04/08 - toomany errors // smierau 11/24/08 - Add 35583 // cjohnson 11/27/08 - change deldent02 // cjohnson 11/19/08 - remove valset00 // cjohnson 10/22/08 - apaberr01 // cchiappa 10/22/08 - Add error logging to message // wechen 10/18/08 - add 35582 // cjohnson 10/13/08 - ftcode00 // akociube 10/13/08 - more logging errors // smierau 08/25/08 - Clean up modifications comments. // wechen 08/20/08 - add 37552 // cchiappa 08/08/08 - Add DBMS_CUBE_LOG spec errors // smierau 08/05/08 - Add logging reject messages. // smierau 06/25/08 - added 34123 for rejected records log // cjohnson 06/30/08 - remove mxdcl34 mxdcl35 // jcarey 06/18/08 - apibranch support // cjohnson 07/08/08 - fix bad merge // cvenezia 05/22/08 - add 37165 // wechen 05/14/08 - fix cause/action for 37541 through 37551 // jcarey 05/22/08 - restore 33275 // cchiappa 05/16/08 - Add logging errors // ckearney 05/17/08 - add _OCI13_ & _OCI14_, 34805 & 34806 respectively // wechen 05/14/08 - add 37541 through 37551 // jcarey 05/02/08 - add 33275 // jcarey 05/12/08 - add 33299 // ghicks 04/15/08 - cause and action for REGRESS00 // ruqtang 04/10/08 - add new hierck err mesg // ckearney 11/30/07 - add 37163 // zqiu 04/12/07 - add 37420 // wechen 03/20/07 - add 37162 // mdombros 01/17/07 - add _XSTBLFUNC14_, change XSOTEXPAND00 to // _XSTBLFUNC13_ // zqiu 01/12/07 - error for explain_mview on CREATE CUBE MV // ghicks 12/27/06 - add _XSLPDSC07_ // ruqtang 12/15/06 - add _XSAGMODDIM02_ // cwelton 12/08/06 - add XSCCLOAD01 and XSCCLOAD02 // ruqtang 11/21/06 - add XSDPART25 // ruqtang 11/13/06 - add XSAGDNGL51 // hyechung 11/06/06 - add and modify XSMXCLEAs // cjohnson 10/31/06 - makedcl10 // jcarey 10/30/06 - no aw detach when cursor open // jcarey 10/24/06 - add _XSCHKMAKE01_ // ckearney 10/16/06 - add XSANALYZ04, 05 & 06, delete property stat msgs // ruqtang 10/12/06 - add _XSCCOMP23, XSVPART09_ // hyechung 10/18/06 - add XSVALSETs // hyechung 10/18/06 - add XSAGDNGL16 // hyechung 10/12/06 - add causes and actions // sdonnell 10/11/06 - readonly // ruqtang 09/18/06 - cc group mesg // esoyleme 09/18/06 - xscoqa messages // jcarey 09/18/06 - Dont rollback non-frozen AW to freeze point // csperry 09/12/06 - Add no aggcount error // ghicks 08/30/06 - add XSRESREV05 // cwelton 08/25/06 - add XSAGGR35, XSCCOMP17 // cchiappa 08/22/06 - Add more COT errors // cjohnson 08/11/06 - remove obsolete messages // cjohnson 08/15/06 - remove obsolete errors // wechen 08/14/06 - recycle 37120, 37150, 37151, 37157 // jcarey 07/26/06 - add DBERRSYNC // ruqtang 08/02/06 - XSRELGID24, 25 // wechen 07/31/06 - add 37161 // ruqtang 07/21/06 - add XSRELDEP00 // cchiappa 07/12/06 - Disallow DELETE of AW with COT // ghicks 07/03/06 - new XSAWRESREVnn messages // mdombros 06/12/06 - add 36825, tabfun arg expansion failed // jcarey 06/15/06 - add xsILPMLTPreOp01 // ruqtang 06/16/06 - change err msg for GID Property // pludwig 06/13/06 - txn117409: LOOP OPTIMIZED and LOOP AGGMAP() // ruqtang 06/12/06 - more err msg for groupset option in gid // ruqtang 05/31/06 - modify XSAGGR33 // ruqtang 06/06/06 - Add XSRELGID19, 20 // ckearney 06/05/06 - add ANALYZDIM00 & ANALYZCUBE00 // wechen 05/22/06 - add 37160 // jcarey 05/25/06 - comment // wechen 05/26/06 - fix 37159 // mdombros 06/01/06 - join pushing failed msg // ckearney 05/19/06 - update lmgen messages // ruqtang 05/24/06 - add XSRELGID18 // cchiappa 06/02/06 - OLAP ORGANIZED tables error messages // cchiappa 04/18/06 - OLAP ORGANIZED tables // jcarey 04/14/06 - aw rollback // wechen 05/12/06 - add 37159 // cjohnson 04/05/06 - timestamp // cchiappa 04/07/06 - Reserve error number range for AW MVs // pludwig 03/24/06 - txn117234: Add XSTBLFUNC10, 11, 10 // cjohnson 03/28/06 - fileset04 // cjohnson 03/24/06 - date_format // cchiappa 03/20/06 - Eliminate DBERR00 // cjohnson 03/06/06 - datetime dim // ckearney 02/09/06 - update sql import error messages // cwelton 03/01/06 - cleanup CC error messages // ghicks 02/08/06 - add _OCI12_, modify wording of a couple of others // cchiappa 01/12/06 - Adjust Aggregate errors to reflect optional aggmap // ghicks 12/21/05 - remove DTNAMES00, DTNAMES01 (MONTHNAMES, DAYNAMES) // ghicks 12/12/05 - add PRMPINIT217, 218, 219 // ckearney 11/29/05 - add stat prop message // ckearney 11/16/05 - add analyze errors // cchiappa 12/01/05 - Add NXHANDLEALLO // ghicks 11/15/05 - add _VCHEX01_ // jcarey 10/26/05 - add freezing // cchiappa 11/07/05 - More verbose sparsity advisor messages // ruqtang 10/11/05 - Add _XSHIERCK09_ // cchiappa 10/03/05 - Add fatal UPDATE error // cjohnson 09/26/05 - stateq01 // ghicks 09/23/05 - add _PHYS03_, _PHYS04_ // ghicks 09/22/05 - add _SNSYN116_ // ruqtang 09/07/05 - add _XSHIERCK06-8_ // ghicks 08/24/05 - add _QFSVNS00_ // cjohnson 08/14/05 - qfget02 d ->ld // ghicks 08/02/05 - add _NLSSORT01_ // ilyubash 06/17/05 - spell check a few errors // cchiappa 07/20/05 - Add 33271: Simulated paging error // zqiu 07/21/05 - add _XSPGERRPQUPD_ // jcarey 06/29/05 - fix pgfetch messages // ruqtang 06/30/05 - add XSHIERCK05,06 and remove HIERCHECK_ // ghicks 06/29/05 - add _XSCHGDFN01_, add NTEXT to _HASHSCAN01_ // ruqtang 06/21/05 - add XSHIERCK03,04 // ghicks 06/18/05 - add _HASHSCANxx_ // zqiu 06/20/05 - better DBERR20 // ruqtang 06/16/05 - add XSAGMODHIER02 // zqiu 06/10/05 - add DBERR20 // ghicks 06/08/05 - remove _MXDCL07_, _MAKETD**_ // ghicks 04/19/05 - add _XSINPUTERR_ // dpeltier 04/21/05 - some new EIF messages // ghicks 04/19/05 - _XSAGGCNTMOVE01_ .. 06_ // ghicks 03/25/05 - add XSLANGDM02 // cchiappa 03/30/05 - Remove 37081 // akociube 03/17/05 - add XSTBLFUNC09 // ghicks 03/18/05 - update list of valid types for _XSMCSESS04_ // cjohnson 03/16/05 - remove xscgrank05 // ghicks 03/17/05 - add XSLANGDM*; tinker with XSSPROP* punctuation. // dpeltier 03/17/05 - really complicated iterators // cchiappa 03/15/05 - Add XSAGDNGLPREC (33009) // cjohnson 03/11/05 - remove unused errors // cwelton 03/11/05 - add XSAGDNGL49, XSAGDNGL50 // cchiappa 03/10/05 - Add XSPQEXPRESS (37069) // cjohnson 03/02/05 - xscgrank05 // ghicks 03/02/05 - add OPCREATE01, O2; remove PPENG04 // cchiappa 03/01/05 - Tweak sps adv errors based on errors_us feedback // cjohnson 02/16/05 - delete mxcgaf04 // cchiappa 02/15/05 - Tweak sparsity advisor messages // dpeltier 02/15/05 - partitioning / aggcount stuff // ghicks 02/12/05 - add _LOCKCHECK01_ // cchiappa 02/10/05 - Add DELDENTANON // cchiappa 02/08/05 - Move errors out of reserved ranges // ruqtang 01/31/05 - add _XSCGMDLAGG09-13_ // dpeltier 01/24/05 - add messages for _mvtopart // ghicks 01/20/05 - add XSFCAST28 (36951) // cchiappa 01/10/05 - More sparsity advisor messages // wechen 12/28/04 - add 37118 through 37120, 37150 through 37158 // ilyubash 12/09/04 - add DBERR07 (33274) // cchiappa 11/29/04 - Sparsity advisor errors // ckearney 11/01/04 - add 36849 & 36850, add %a to 36886 // ghicks 10/31/04 - spelling; remove MXSQL25, XSAGDNGL45 // dpeltier 10/13/04 - MXMSERR01 takes a qon node // pludwig 10/04/04 - Fix assignments of scalar to temp scalar variables // ruqtang 09/14/04 - correct more mesg for XSRELTBL/XSRELGID // ruqtang 09/08/04 - XSRELGID17 // esoyleme 09/07/04 - message for transportable platform mismatch // cchiappa 08/20/04 - Move bad error messages // ghicks 07/28/04 - slight adjustment to MXRECAP09 // ghicks 07/19/04 - delete EIFEXPRT00 // cjohnson 07/13/04 - Add XSBASLIM00 // cchiappa 06/29/04 - Add XSAGGRFORM // ghicks 06/30/04 - eliminate MODGONE00, add MDQUERY01 // dpeltier 06/25/04 - xsLmsMesg changes // cwelton 06/24/04 - XSCCOMP11 thru XSCCOMP15 // zqiu 06/23/04 - more action for DBERRBSZ // ckearney 06/23/04 - Add XSSRF04, XSSRF05 & XSSRF06 // cwelton 06/28/04 - Cleanup cc error messages // ghicks 06/17/04 - add SNSYN205 // cchiappa 06/17/04 - Fix XSAGGR33 arguments // cchiappa 06/09/04 - Tweak cause for XSAGGCNTPROP // cchiappa 06/07/04 - Add XSAGGCNTPROP // ghicks 06/03/04 - remove obsolete PRMPINIT initializers // dpeltier 06/01/04 - XSCCOMP0[456] wording, add XSCCOMP10 // dpeltier 05/17/04 - aw_upgrade -> polymorphic convert // cchiappa 05/14/04 - Add XSAGPROPFROM // dpeltier 05/12/04 - AGGCOUNT // ghicks 05/03/04 - XSSQLMDQ messages // dpeltier 04/15/04 - AWUPG messages // cchiappa 04/09/04 - Add XSSPROPDTYPE // cchiappa 04/09/04 - Fix text for XSMXAGGR10 // cchiappa 04/09/04 - Add XSAGGRRUVCV // cchiappa 03/29/04 - Spell correct DBERR18, text for 33269 // ruqtang 03/29/04 - RELTBL15 // dpeltier 03/16/04 - make EIFEXPRT01 more general // dpeltier 03/03/04 - XSMXAGGR06 // cjohnson 03/02/04 - obsolete errors // ilyubash 03/15/04 - Allow add SESSION in MULTI // cjohnson 02/18/04 - obsolete errors // cjohnson 02/23/04 - obsolete errors // ghicks 02/05/04 - delete obsolete messages, add XSSPFC01 // dpeltier 01/30/04 - MAINTCHK messages // ilyubash 12/29/03 - Add messages delayed since 10gR1 // jcarey 12/19/03 - add XSDBVALID 05, 06 // cwelton 08/18/03 - Add XSCCOMP00 - XSCCOMP09 // dpeltier 08/07/03 - add compressed composite messages // ckearney 08/06/03 - add _XSSRF03_ message & update other SRF messages // ghicks 08/05/03 - fix %p (-> %%p) in VCFMT005 // wechen 08/04/03 - add 37117 for xsldolap // cjohnson 07/23/03 - MAXDIMS 256 // cchiappa 07/31/03 - Fix XSDPART24 // esoyleme 07/29/03 - add 37100 // pludwig 07/29/03 - txn107486: Concat custom members // ghicks 07/22/03 - reintroduce QFHEAD01 in case of need // ckearney 07/21/03 - add _XSTBLFUNC08_ // zqiu 07/22/03 - change err text of 36770 // rtang 07/24/03 - add XSAGDNGL48 // ghicks 07/17/03 - reword QFHEAD06; 86 QFHEAD01; QFHEAD causes/actions // jcarey 07/16/03 - More cause and actions // jcarey 07/15/03 - add finegrained access control error message // zqiu 07/09/03 - add DBERRBSZ // ilyubash 07/03/03 - Add Bad Expression error to Table Fucntions // cchiappa 06/24/03 - Eliminate XSPQRO (37071) // ghicks 06/23/03 - drop word 'dimension' from PERMIT06 // wechen 06/17/03 - add 37116 for xsldolap // ilyubash 06/13/03 - Add Rollback support error messages // pludwig 06/09/03 - txn107433: dup concat leaves in model DIMENSION stmt // rtang 06/05/03 - add more errs for XSCGMDLAGG // ghicks 05/29/03 - fix run-on sentence in 37002 // cchiappa 05/28/03 - Eliminate session sharing stuff // wechen 05/27/03 - add 37115 for xsldolap // pludwig 05/27/03 - txn106886: More UNIQUE Concats // rtang 05/19/03 - XSMCSESS08 // dpeltier 05/19/03 - 9i2 compatibility & EIF // ghicks 05/15/03 - 86 FCREATE06 // ghicks 05/09/03 - 86 QFGET04 // cwelton 05/08/03 - XSCCUBE01/02 // ghicks 05/07/03 - PERMIT06 // dpeltier 05/07/03 - add ESDREAD17, XSVPART07 // dpeltier 05/07/03 - partition list maintenance // cjohnson 05/06/03 - TRGPRG02 // ghicks 04/29/03 - edit causes/actions for 4/21/03 messages // cjohnson 04/29/03 - TRGSET01 // cchiappa 04/21/03 - Add XSPQRO // ghicks 04/21/03 - CINSERT06/07, CMOVE03; reword XSMCSESS messages // cjohnson 04/21/03 - TRIGGER // rtang 04/21/03 - Add more XSRELGID err msg // rtang 04/16/03 - XSMCSESS07 // dpeltier 04/08/03 - list partitioning changes // cwelton 04/08/03 - // pludwig 04/07/03 - txn105869: Unique CONCATs // rtang 03/28/03 - More err msg for custmem // cwelton 04/03/03 - // cchiappa 03/26/03 - Add DBERRTABLE // cjohnson 03/26/03 - TRANSLATEBYTES // cchiappa 03/19/03 - DBERRLEN 8 byte arguments // ghicks 03/19/03 - Add Hide/unhide model msg // dpeltier 03/14/03 - change some partitioning messages // cchiappa 03/13/03 - Add DBERRLEN // cchiappa 03/06/03 - Reword DBDESC06 // esoyleme 02/06/03 - SQL spreadsheet error // cjohnson 02/24/03 - chgdfn inverted // cwelton 03/26/03 - XSAGPARTDEP - aggregate + recursive partitions // cwelton 03/03/03 - XSAGHIERPART - aggregate + partitions // dpeltier 02/14/03 - more partitioning stuff // dpeltier 02/13/03 - bad compatibility settings for object define // dpeltier 02/10/03 - some small partitioning stuff // ilyubash 01/20/03 - New-gen-present errors // ghicks 01/15/03 - remove (very) obsolete MAINTAIN COMPACT reference // cjohnson 01/10/03 - sharemap // zqiu 01/13/03 - remove _XSAWRENAME_* // cchiappa 01/15/03 - Add message for text ag var reuse // esoyleme 12/24/02 - fix message for 37080 // cjohnson 12/22/02 - TEMP dimension // zqiu 01/03/03 - add 37060, 37061 for aw_rename // wechen 12/19/02 - add 37111, 37112, 37113 & 37114 for xsldolap // dpeltier 12/09/02 - multiwriter dimension maintenance // ilyubash 12/02/02 - Multiwriter work // dpeltier 11/19/02 - more partitioning // ghicks 12/04/02 - substitution marker in MXCGVAR01 // cjohnson 11/26/02 - export partition template // pludwig 11/19/02 - txn105041 // ghicks 11/16/02 - various small fixes // rtang 11/15/02 - Fix MCSESS Error Msg // rtang 11/12/02 - add XSMCSESS02 // ckearney 11/12/02 - Updated MXSQL24 & SQLOUT11 // ilyubash 11/11/02 - Add more Multiwriter errors // cchiappa 11/04/02 - Optional aggmap in allocate (SNSYN163) // dpeltier 11/04/02 - LIST partitioning // dpeltier 11/02/02 - Add DELDENT05 // pludwig 11/01/02 - txn104999 // ghicks 10/28/02 - add QFSVNS01 // ilyubash 10/24/02 - More Multiwriter error msgs // pludwig 10/23/02 - txn104769 // cchiappa 10/21/02 - Add BADSPROP, NOAGM // cjohnson 10/19/02 - sort hierarchy // ghicks 10/17/02 - add 'missing or' to MXIMPORT04 // dpeltier 10/16/02 - BASE -> CONCAT // dpeltier 10/14/02 - more partitioning // rtang 10/14/02 - messages for mnt session // pludwig 10/12/02 - txn104553 // cchiappa 10/08/02 - Add _XSAGDIMBREAK_ // esoyleme 10/04/02 - more advisor messages // dpeltier 09/30/02 - subpartitioning // cchiappa 09/27/02 - Flow -> Drop // cjohnson 09/27/02 - chgdims limit arg // esoyleme 09/23/02 - aggregate advisor messages // ilyubash 09/20/02 - Add more XSACQUIRE messages // ghicks 09/19/02 - texts for AW LIST and AW(LISTALL) // cchiappa 09/19/02 - Add 37003 - May not xeq in pq sess // ckearney 09/12/02 - Change _XSSRF01 message // dpeltier 09/11/02 - fix MXPSHPOP03 // ilyubash 09/05/02 - added multiwriter error msgs // ilyubash 09/11/02 - Adding new DTB error messages // ilyubash 09/04/02 - Add table function describe error messages // dpeltier 09/04/02 - more partitioning // dpeltier 08/28/02 - more partitioning // cchiappa 09/04/02 - Add XSAGDIMFLOW // rtang 08/22/02 - Add more error for GroupingID // dpeltier 08/19/02 - Partitioned variables messages // cchiappa 09/03/02 - Modify PHYS0{0,1} // cchiappa 08/15/02 - Add autoupdate & autocommit error // dpeltier 08/08/02 - More partitioning messages // rtang 08/05/02 - Change RELTBL mesg // cwelton 08/05/02 - Add XSTBLFUNC06 // ckearney 08/07/02 - Add _XSSRF02_ & _XSTBLFUNC07_ // cchiappa 08/02/02 - Add 37002, OLAP failed to initialize // cchiappa 08/02/02 - Fix XSAGDNGL24, XSAGDNGL43 // cchiappa 08/01/02 - Add 36961, OLAP not available // ckearney 08/01/02 - Add _XSSRF01_ // dpeltier 07/10/02 - XSDPART messages // ghicks 07/30/02 - MAKEDCL35 - "date dimension" -> "time dimension" // cchiappa 07/30/02 - Add XSUNUPDATED // ghicks 07/25/02 - change MXPROPER04 to substitute min/max // ilyubash 07/24/02 - Added MXDSS29 // pludwig 07/25/02 - txn103641 // rtang 07/23/02 - Add XSAGDNGL47 // pludwig 07/23/02 - pludwig_txn103382 // cwelton 07/24/02 - Add XSTBLFUNC05 // cjohnson 07/22/02 - XSSCLLEV09 // cwelton 07/17/02 - Add XSTBLFUNC04 // cchiappa 07/16/02 - Modify XSMXAGGRFROM // pludwig 07/15/02 - pludwig_txn103382 // cchiappa 07/08/02 - Remove text from XSAGGR33 & XSAGGR34 // ghicks 07/02/02 - fix OFCENG02 ("specifiy") // ckearney 06/27/02 - Added _SQLOUT20_ - ORA-35587. // ckearney 07/10/02 - Added _XSSRF00_ // esoyleme 06/20/02 - Fix XSAGGR33 // cchiappa 06/20/02 - Add dataflow XSMXAGGR messages // cchiappa 05/24/02 - Kill XSAGINFO01, add header // jcarey 05/24/02 - LRG97582 - bad memory references past end-of-buffer // dpeltier 05/23/02 - Fix NTEXT garbage in error messages // edashevs ??/??/?? - edashevs_txn102340 // zqiu 05/14/02 - change OLAP_PAGE_POOL_SIZE to big int // cwelton 05/04/02 - Implement LMINFO function // cchiappa 05/02/02 - Alias dimension for parents in allocate // ckearney 05/02/02 - sql SELECT work // cchiappa 04/25/02 - Allow agg of unlike-dimensioned vars in one command // cwelton 04/12/02 - obj(aggmaplist) function // rtang 04/07/02 - Single dimension model only as dynamic model // rtang ??/??/?? - rtang_txn105656 // ghicks ??/??/?? - ghicks_txn105486 // cchiappa ??/??/?? - cchiappa_txn105431 // cjohnson 03/27/02 - LEVELREL args for LAG/MOVING functions // ghicks 03/13/02 - AIX porting bug 2194536 (again); // ilyubash 02/01/02 - Gracefully handle out-of-temp-space problems. // ghicks 01/26/02 - eversion and eifversion; // ghicks 01/19/02 - allow obj(numvals) etc. to return > MINSB8MAXVAL;- // cjohnson 01/18/02 - remove h files // ghicks 01/18/02 - new Geneva functionality // ghicks 01/11/02 - remove STRIP command; // cchiappa 01/08/02 - Fix allocate bugs // dpeltier 12/14/01 - More AW name: aliases, different semantics, etc. // edashevs ??/??/?? - edashevs_txn101085 // pludwig 12/12/01 - Fix Bug 2139758 - 64bit problem in xskvbn.c // dpeltier 12/11/01 - AW names / attachnames // edashevs ??/??/?? - edashevs_txn100848 // jcarey 12/05/01 - causes and actions. // dpeltier 12/05/01 - EIF export, FILEREAD, implicit conversion exceptions // ahopeman 11/29/01 - Table functions use xsinterp to execute commands // dpeltier 11/29/01 - Surrogate bug 2110865 // ghicks 11/29/01 - filequery // ilyubash 11/29/01 - Segv in EIF code without running CDA // cwelton 11/27/01 - Table Function error msg // dpeltier 11/20/01 - Clean up LMS messaging; remove OS translation // pludwig 11/20/01 - CONCAT base add and export exclude // rtang 11/20/01 - New requirement of dynamic model at current stage // cjohnson 11/19/01 - olint fixes // jcarey ??/??/?? - jcarey_txn100717 // ilyubash 11/16/01 - Further support for directory aliases // ghicks 11/16/01 - allow (slightly crippled) multi-file EIF export; // rtang 11/14/01 - fill cause and action fields in error message. // rtang 11/13/01 - number dimesnioned destination relation GID // dpeltier 11/12/01 - NUMBER dims // cjohnson 11/01/01 - remove .h files from xseng/globals.h // dpeltier 10/31/01 - NTEXT: UNISTR(), output functions // ghicks 10/31/01 - BUG2075951 - INFO(PARSE TYPE) for program/extcall // dpeltier 10/29/01 - Surrogates: unit tests and bug fixes // cjohnson 10/26/01 - GUARD/ONEXIT bugs // ghicks 10/26/01 - porting grp changes for variable name conflicts etc. // rtang 10/26/01 - hierheight & groupingid support multidim relations // dpeltier 10/24/01 - Remove data gatherer messages from olap33k.msg // cjohnson 10/21/01 - fix qa tests // cjohnson 10/19/01 - remove obsolete code and fix txengcdd.tst // ilyubash 10/19/01 - Fix AW DELETE and link it into enqueues // cjohnson 10/16/01 - fix QA log files/ CGETPOS05 xsOOPS // dpeltier 10/15/01 - Some NTEXT import / export fixes // dpeltier 10/11/01 - Fix log files for message difs // dpeltier 10/10/01 - Messages from rdbms/ora*.msb, not olap/aps*.msb // abatakis ??/??/?? - Created from old files // /************************************************************** / Message file for Oracle OLAP /************************************************************** / 33000, 00000, "(AGOPEN00) %a %j %s\nAGGMAP %1p cannot be accessed because it was compiled by a more recent version of %2p." // *Cause: The AGGMAP was already compiled by a more recent version of the // product than was being used to execute this command. // *Action: Recompile the AGGMAP in the current version. /// Codes from xsagdang.c (100-359) 33002, 00000, "(XSAGDNGL00) %a %j %lf %lf\nIn AGGMAP %1p, the FLOOR argument of %2p must be less than the CEILING argument of %3p." // *Cause: The user specified a floor argument greater than the // ceiling argument. // *Action: Adjust the floor and ceiling arguments so that the floor is // less than the ceiling. // OBSOLETE, please remove this 33003, 00000, "(XSAGDIMDROP) %j, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP." // *Cause: The user tried to specify a dimension in a dataflow-related clause // in an aggmap which is already in another RELATION statement, DIMENSION // statement, or possibly dimensioning the AGGMAP, or they specified a // composite or conjoint dimension, or an object which is not a dimension // *Action: Remove the conflicting reference or specify a valid object 33004, 00000, "(XSAGDNGL01) %q is not a relationship array." // *Cause: A RELATION clause in the AGGMAP named a workspace object that // is not a relation. // *Action: Name a valid self-relation in the RELATION statement. 33005, 00000, "(XSAGDIMBREAK) Invalid breakout for dimension %n." // *Cause: The user specified something that was not a valid dimension or // relation on a BREAKOUTDIM line in an aggmap. This might be // because the object was not a valid relation, was not over the // specified dimension or was multidimensional // *Action: Use a valid relation instead 33006, 00000, "(XSAGDNGL02) The relation %q is not related to itself." // *Cause: A relation was named in a RELATION clause of the AGGMAP that is // not a self-relation. // *Action: Name a valid self-relation in the RELATION statement. 33007, 00000, "(XSAGPVAR) %a %j\n%1p may only be used as one of: an OPERATOR, ARGS, or FROMVAR variable." 33008, 00000, "(XSAGDNGL03) %a %j %j\nThe relation %2p is not a relation over a base dimension of AGGMAP %1p." // *Cause: A relation was named in a RELATION clause of the AGGMAP that is // not a relation for a base dimension of the AGGMAP. // *Action: Name a valid self-relation in the RELATION statement, that is, one that // has a dimension that dimensions the AGGMAP. 33009, 00000, "(XSAGDNGLPREC) %a %j\n In AGGMAP %1p, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements." // *Cause: PRECOMPUTE was specified both as a line in the AGGMAP and on at least one of the RELATION lines, or it was specified more than once as a line of the AGGMAP. // *Action: Remove either the PRECOMPUTE line, or the PRECOMPUTE specification for all of the RELATION lines. 33010, 00000, "(XSAGDNGL04) %a %q %n\nRelation %1p is duplicated in the AGGMAP %2p." // *Cause: Two RELATION statements in the AGGMAP reference the same // relation object. // *Action: Remove the duplicate RELATION statement. 33012, 00000, "(XSAGDNGL05) AGGMAP %n contains invalid syntax." // *Cause: A line in the AGGMAP contains invalid syntax. // *Action: Change the line to have valid syntax. 33014, 00000, "(XSAGDNGL06) %a %n %n %j\nIn AGGMAP %1p, variable operator %2p cannot be dimensioned by rollup dimension %3p." // *Cause: Operator variables cannot have the rollup dimension as // one of their base dimensions. // *Action: Modify the definition of the operator variable so that the // current rollup dimension is not one of its bases. 33016, 00000, "(XSAGDNGL07) %a %n %q\nIn AGGMAP %1p, %2p is not a valid operator or variable name." // *Cause: An invalid argument was supplied to the OPERATOR clause in the // relation statement. // *Action: Fix the OPERATOR clause so that it specifies either a valid // variable name or a valid operator. 33018, 00000, "(XSAGDNGL08) %a %n %n %s\nIn AGGMAP %1p, the data type of %2p must be TEXT, not %3p." // *Cause: An operator variable was supplied whose data type is not TEXT. // *Action: Change the operator clause to reference a TEXT variable. 33022, 00000, "(XSAGDNGL10) %a %j %j\nThe measure dimension %2p must be a TEXT or ID base dimension that does not dimension AGGMAP %1p, but is in the same analytic workspace." // *Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable. // *Action: Modify the MEASUREDIM clause to specify a valid dimension. 33024, 00000, "(XSAGDNGL11) AGGMAP %j contains duplicate information." // *Cause: The aggmap contains multiple instances of a clause that // can only be specified once. // *Action: Remove the extra clause. 33026, 00000, "(XSAGDNGL12) %a %j %q\nIn AGGMAP %1p, %2p is not a valid valueset." // *Cause: A line in the AGGMAP contains an invalid element where a valid valueset is required. // *Action: Change the line to have a valid valueset. 33028, 00000, "(XSAGDNGL13) %a %j %n\nIn AGGMAP %1p, %2p should be scalar, not a dimensioned valueset." // *Cause: A line in the AGGMAP contains a dimensioned valueset where a scalared valueset is required. // *Action: Change the line to have a scalar valueset. 33030, 00000, "(XSAGDNGL14) In AGGMAP %j, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements." // *Cause: The AGGMAP either specified multiple PROTECT statements not // on a RELATION line, or specified PROTECT statements both // independently and on RELATION lines. // *Action: Correct the AGGMAP to have valid syntax. 33032, 00000, "(XSAGDNGL15) %a %j %n\nIn AGGMAP %1p, VALUESET %2p must be in extra dimensions of the relation." // *Cause: The RELATION phrase contains a VALUESET which is not over the extra dimension of the RELATION. // *Action: Correct the RELATION phrase to contain a valueset over the extra dimension or not to contain any valueset. 33034, 00000, "(XSAGDNGL16) %a %j %j\nIn AGGMAP %1p, VALUESET %2p in PRECOMPUTE phrase must be in the self dimension of the relation." // *Cause: The precompute phrase contains a valueset which is not over the self dimension of the relation. // *Action: Correct the relation phrase to contain a valueset over the self dimension or not to contain any valueset. 33036, 00000, "(XSAGDNGL17) ARGS option %n must be a TEXT variable." // *Cause: An ARGS value had a non-text data type. // *Action: Use a text variable for ARGS. 33038, 00000, "(XSAGDNGL18) %a %j %j\nIn AGGMAP %1p, RELATION %2p contains hierarchy dimensions that are also dimensions of the AGGMAP." // *Cause: Hierarchy dimensions(extra dimensions) of a RELATION in the AGGMAP are base dimensions of the AGGMAP. // *Action: Correct the RELATION not to have hierarchy dimensions(extra dimensions) which are also base dimensions of the AGGMAP. 33040, 00000, "(XSAGDNGL19) %a %j %j %j\nIn AGGMAP %1p, VALUESETS %2p and %3p are both over the same hierarchy dimension." // *Cause: Two or more different VALUESETs over the same hierarchy dimension are used in the AGGMAP. // *Action: Use the same VALUESET for two RELATION phrases or use two different VALUESETs over two different hierachy dimensions. 33042, 00000, "(XSAGDNGL20) %a %j %j %j\nIn AGGMAP %1p, VALUESET %2p must qualify all relations dimensioned by %3p." // *Cause: A VALUESET over a hierarchy dimension qualifies some RELATIONs but not all RELATIONs dimensioned by the same hierarchy dimension. // *Action: Use the same VALUESET to qualify all the RELATIONs dimensioned by the same hierarchy dimension. 33044, 00000, "(XSAGDNGL21) %a %s %j\nAGGREGATE operator %1p requires a WEIGHTBY clause, but the ARGS clause in AGGMAP %2p did not specify one." // *Cause: The user used an operator which needs weight values but not provided the weight values. // *Action: Provide weight values using a WEIGHTBY cluase. 33045, 00000, "(XSAGDNGL51) %a %s %j %n\nThe AGGREGATE operator %1p does not require a weight, but ARGS clause in AGGMAP %2p specified %3p as a weight." // *Cause: The ARGS variable specified a weight even though one is // not needed. // *Action: Modify the ARGS variable so that it does not specify a weight for // that operation. 33046, 00000, "(XSAGDNGL22) In AGGMAP %j, you can specify only one SCREENBY clause." // *Cause: The AGGMAP contained multiple SCREENBY clauses. // *Action: Remove one of the SCREENBY clauses from the AGGMAP. 33048, 00000, "(XSAGDNGL23) %a %n %j %j\nIn AGGMAP %1p, the relation %2p and the relation %3p are both over the same base dimension." // *Cause: The AGGMAP contains incompatible RELATION statements. // *Action: Remove one of the RELATION statements from the AGGMAP. 33050, 00000, "(XSAGDNGL24) %a %j %j\nAGGMAP %1p cannot be used to aggregate %2p, because it is defined in a different analytic workspace." // *Cause: The user attempted to aggregate a variable in another // analytic workspace. // *Action: Create an AGGMAP in the other analytic workspace to aggregate // that variable. 33052, 00000, "(XSAGDNGL25) AGGMAP %j is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables." // *Cause: The user attempted to aggregate a variable with different dimensions // than the AGGMAP. This is only possible with undimensioned AGGMAPs. // *Action: Create a new undimensioned AGGMAP. 33058, 00000, "(XSAGDNGL28) %a %j %t %d\nIn AGGMAP %1p, error code %2p is greater than the maximum error code of %3p." // *Cause: The user specified an invalid ERRORMASK value. // *Action: Remove the invalid value from the ERRORMASK list. 33060, 00000, "(XSAGDNGL29) In AGGMAP %j, the value for the ERRORLOG MAX option must be greater than 0." // *Cause: The user specified an ERRORLOG MAX of 0 or a negative number. // *Action: Adjust the AGGMAP so that it uses a positive number. 33062, 00000, "(XSAGDNGL30) %a %j %n\nIn ALLOCMAP %1p, WEIGHTBY option %2p must be a numerical VARIABLE or FORMULA." // *Cause: The WEIGHTBY clause requires numerical VARIABLE or FORMULA but the user used invalid objects. // *Action: Correct the WEIGHTBY cluase to use a valid numerical VARIABLE or FORMULA. 33064, 00000, "(XSAGDNGL31) %a %j %n\nIn AGGMAP %1p, the hierarchy dimension QDR %2p cannot refer to the related dimension of the relation." // *Cause: The user specified an invalid hierarchy dimension qualified data reference. // *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. 33066, 00000, "(XSAGDNGL32) %a %j %n\nIn AGGMAP %1p, the hierarchy dimension QDR %2p must be a hierarchy dimension of the relation." // *Cause: The user specified an invalid qualified data reference for the hierarchy dimension. // *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. 33068, 00000, "(XSAGDNGL33) %a %j %j\nIn AGGMAP %1p, the hierarchy dimension QDR over dimension %2p must specify a positive dimension offset." // *Cause: The user specified an invalid qualified data reference for the hierarchy dimension. // *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. 33070, 00000, "(XSAGDNGL34) %a %j %j\nIn AGGMAP %1p, all QDRs of dimension %2p must map to the same dimension position." // *Cause: The user specified two conflicting hierarchy dimension qualified data references. // *Action: Adjust the AGGMAP so that it uses a consistent qualified data reference. 33072, 00000, "(XSAGDNGL35) %a %j %j\nIn AGGMAP %1p, the hierarchy dimension QDR over dimension %2p must be specified for every relation dimensioned by that hierarchy dimension." // *Cause: Multiple dimensions share the same hierarchy dimension, but it is // only qualified within a subset of the AGGMAP relations. // *Action: Adjust the AGGMAP so that it uses consistent qualified data references. 33074, 00000, "(XSAGDNGL36) %a %j %j %ld\nIn AGGMAP %1p, the offset %3p is not a valid offset into dimension %2p." // *Cause: The hierarchy dimension offset is an invalid dimension position. // *Action: Adjust the AGGMAP so that it uses valid qualified data references. 33076, 00000, "(XSAGDNGL37) %a %j %j %v\nIn AGGMAP %1p, the value '%3p' is not a valid value of dimension %2p." // *Cause: The hierarchy dimension offset is an invalid dimension position. // *Action: Adjust the AGGMAP so that it uses valid qualified data references. 33078, 00000, "(XSAGDNGL39) %a %j %q\nIn AGGMAP %1p, the hierarchy dimension QDR %2p must refer to a dimension." // *Cause: The user specified an invalid qualified data reference for the hierarchy dimension. // *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. 33080, 00000, "(XSAGDNGL40) %a %j %j\nIn AGGMAP %1p, you cannot reference dimension %2p with both a RELATION statement and a DIMENSION statement." // *Cause: The user included both RELATION and DIMENSION statements in // the AGGMAP referring to the same AGGMAP. // *Action: Remove one of the conflicting clauses. 33082, 00000, "(XSAGDNGL41) %a %j %n\nIn AGGMAP %1p, the non-dimensioned valueset %2p must have a parent QDR in its VALUESET statement over the VALUESET's base dimension." // *Cause: The VALUESET statement specified a scalar valueset // but did not include a qualified data reference to specify the parent. // *Action: Add a qualified data reference specifying the parent to the VALUESET statement. 33084, 00000, "(XSAGDNGL42) %a %j %j\nIn AGGMAP %1p, you cannot qualify the dimensioned valueset %2p." // *Cause: The VALUESET line referred to a dimensioned valueset. // *Action: Use a non-dimensioned valueset to limit the status of the // dimensioned one. /// XSAGINIT and XSAGCOMP messages (379-539) from xsagcomp.c 33086, 00000, "(XSAGINIT01) %a %j %j\nAGGMAP %1p cannot be dimensioned by a conjoint dimension." // *Cause: The specified AGGMAP was dimensioned by // a conjoint dimension. // *Action: Use the CHGDFN command to change the conjoint to a composite dimension. 33088, 00000, "(XSAGINIT03) You do not have read permission for AGGMAP object %j." // *Cause: // *Action: 33090, 00000, "(XSAGINIT05) %a %j %j\nYou must have read permission for %1p to use AGGMAP %2p." // *Cause: // *Action: 33092, 00000, "(XSAGCOMP04) %v is not the name of a MODEL in any attached analytic workspace." // *Cause: An invalid model name was attached to an AGGMAP. // *Action: Remove the model from the AGGMAP or create a model with that name. 33094, 00000, "(XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting." // *Cause: formulas likely refer to each other recursively or with a great // deal of depth. // *Action: eliminate recursion and flatten formula trees. 33098, 00000, "(APABBR01) %a %V %j\nA value of '%1p' is not valid for the %2p option." // *Cause: An inappropriate value was specified for the // named option. // *Action: Set a legal value for the option. 33100, 00000, "(APABBR02) %a %d %j\nValue '%1p' is not valid for the %2p option." // *Cause: An inappropriate value was specified for the // named option. // *Action: Set a legal value for the option. 33102, 00000, "(APEIFV01) EIFVERSION cannot be greater than the current EVERSION, which is %d." // *Cause: // *Action: 33104, 00000, "(APEIFV02) EIFVERSION cannot be less than 371." // *Cause: // *Action: 33106, 00000, "(APESCBAS01) '%i' is not a valid value for the ESCAPEBASE option. Valid values are 'd' and 'x'." // *Cause: // *Action: 33108, 00000, "(APFTMAX01) MAXFETCH must be between 1,000 and 2,147,483,647." // *Cause: // *Action: 33110, 00000, "(APXPKTSZ01) XAPIBUFFER must be between 1,000 and 64,512." // *Cause: // *Action: 33112, 00000, "(APFTBUFF01) FETCHBUFFER must be between 1,000 and 64,512." // *Cause: // *Action: 33114, 00000, "(APLIKESC01) %i is not a valid value for the LIKEESCAPE option because it is more than one character long." // *Cause: // *Action: 33116, 00000, "(APMSTYPE00) MODSIMULTYPE must be either AITKENS or GAUSS." // *Cause: // *Action: 33118, 00000, "(APMTOLER00) Value %d is out of range for MODTOLERANCE." // *Cause: // *Action: 33120, 00000, "(APMOVFLO00) Value %d is out of range for MODOVERFLOW." // *Cause: // *Action: 33122, 00000, "(APMGAMMA00) MODGAMMA must be a whole number greater than or equal to zero." // *Cause: // *Action: 33124, 00000, "(APMITERS00) MODMAXITERS must be a whole number greater than zero." // *Cause: // *Action: 33126, 00000, "(APMDAMPF00) MODDAMP must be greater than or equal to zero and less than one." // *Cause: // *Action: 33128, 00000, "(APMERROR00) MODERROR must be either STOP, CONTINUE, or DEBUG." // *Cause: // *Action: 33130, 00000, "(APMERROR01) The current connection type does not support interactive debugging." // *Cause: // *Action: 33132, 00000, "(APPGMGR00) %a %j %d\nThe %1p option value must be between 0 and %2p." // *Cause: // *Action: 33134, 00000, "(APSORTBUFSZ01) %a %d %d\nThe value of SORTBUFFERSIZE must represent a number between 0 and %1p. You supplied %2p." // *Cause: // *Action: 33136, 00000, "(APSPARSX01) The value of SPARSEINDEX cannot be a multi-line string." // *Cause: // *Action: 33138, 00000, "(APSPARSX02) The value '%v' is not valid for SPARSEINDEX." // *Cause: // *Action: 33140, 00000, "(AUTOCOMP1) %n is being compiled automatically." // *Cause: // *Action: 33141, 00000, "(XSAWFREEZE1) The analytic workspace %s is already frozen." // *Cause: Attempting to freeze an AW when it is already frozen // *Action: Thaw the AW before freezing it again. 33142, 00000, "(BADSYN00) The format of the %t command is incorrect." // *Cause: // *Action: 33143, 00000, "(XSAWFREEZE2) The analytic workspace %s must be attached RW or RX." // *Cause: The AW must be updatable to change the freeze state // *Action: Reattach AW before freezing or thawing it again. 33144, 00000, "(BADSYN01) The format of the %t command is incorrect." // *Cause: // *Action: 33145, 00000, "(XSAWFREEZE3) Cannot rollback analytic workspace %s; generations are in use." // *Cause: One or more generations due to be destroyed as part of a rollback // to freeze command are currently in use. // *Action: Get sessions using those generations to detach the AW. 33146, 00000, "(BINENG00) The width argument for binary conversion can only be specified for INTEGER and BOOLEAN data." // *Cause: // *Action: 33147, 00000, "(XSAWFREEZE4) The analytic workspace %s is not frozen." // *Cause: You are attempting to "rollback to freeze" an AW that is not // frozen. // *Action: Only execute this command on a frozen AW. 33148, 00000, "(BINENG01) The width argument for binary conversion must be 1, 2, or 4." // *Cause: // *Action: 33150, 00000, "(BOOLTOK01) %t is not a Boolean." // *Cause: // *Action: 33152, 00000, "(CDELETE03) %a %j %ld\nThe %1p dimension does not have a value at position %2p." // *Cause: // *Action: 33154, 00000, "(CFINDVAL01) The %j dimension does not have identifiers." // *Cause: // *Action: 33156, 00000, "(CFINDVAL02) Positions greater than 2**63 in a dimension map cannot be referenced." // *Cause: // *Action: 33158, 00000, "(CGETPOS02) %a %j %ld\nThe %1p dimension does not have a value numbered %2p." // *Cause: // *Action: 33160, 00000, "(CGETSEQ02) %a %j %ld\nThe %1p dimension does not have a value at position %2p." // *Cause: // *Action: 33162, 00000, "(CGFIN00) principal-value" // *Cause: // *Action: 33164, 00000, "(CGFIN01) asset-value" // *Cause: // *Action: 33166, 00000, "(CGFIN02) The number of periods of the %t function cannot be dimensioned by time." // *Cause: // *Action: 33168, 00000, "(CGFIN03) The salvage value argument of the %t function must be dimensioned by the time dimension." // *Cause: // *Action: 33170, 00000, "(CGFIN04) The decline factor argument of the %t function cannot be dimensioned by the time dimension." // *Cause: // *Action: 33172, 00000, "(CGFIN05) The portion argument of the %t function cannot be dimensioned by time." // *Cause: // *Action: 33174, 00000, "(CGFIN06) The switch period argument of the DEPRDECLSW function cannot be dimensioned by time." // *Cause: // *Action: 33176, 00000, "(CGMCALC01) The member list expression in aggregation phrase %d is multidimensional." // *Cause: // *Action: 33178, 00000, "(CGMCALC02) %j appears as the dimension of more than one member list expression." // *Cause: // *Action: 33180, 00000, "(CGMCALC03) WEIGHTBY can only be specified for the AVERAGE aggregation method." // *Cause: // *Action: 33182, 00000, "(CGMCALC04) The base measure expression is not dimensioned by %j." // *Cause: // *Action: 33184, 00000, "(CGMCALC05) A valueset argument to MCALC must have one dimension and be a valueset of the same dimension." // *Cause: // *Action: 33186, 00000, "(CGMODSET01) The ACROSS option is not supported in model equations." // *Cause: // *Action: 33188, 00000, "(CGMODSET02) %a %j %v %j\nThe left-hand side of an equation involves the %1p dimension, whereas the '%2p' term on the right-hand side involves %3p." // *Cause: // *Action: 33190, 00000, "(CGMODSET03) An internal error caused the model assignment code generator to be called, but no MODEL is currently being compiled." // *Cause: // *Action: 33192, 00000, "(CGTCVT00) TCONVERT requires an argument dimensioned by time." // *Cause: // *Action: 33194, 00000, "(CGTCVT01) The argument to TCONVERT cannot be dimensioned by more than a single time dimension." // *Cause: // *Action: 33196, 00000, "(CGTCVT03) Invalid conversion method for TCONVERT." // *Cause: // *Action: 33198, 00000, "(CGTCVT04) The two conversion methods requested of TCONVERT are incompatible." // *Cause: // *Action: 33200, 00000, "(CGTCVT05) You cannot convert by both DAY and PERIOD. You must use one or the other." // *Cause: // *Action: 33202, 00000, "(CGTCVT06) The breakout dimension %j is not a time dimension." // *Cause: // *Action: 33204, 00000, "(CGTCVT07) %a %j %j\nIn converting data from time dimension %1p to %2p using TCONVERT, a conversion direction must be given." // *Cause: // *Action: 33206, 00000, "(CGTCVT08) %a %j %j\nIt is not possible to convert data dimensioned by %1p to be dimensioned by %2p." // *Cause: // *Action: 33208, 00000, "(CGTDF00) You can only find the start or end of a time period." // *Cause: // *Action: 33210, 00000, "(CGTDF01) The argument of the BEGINDATE or ENDDATE function must be dimensioned by exactly one time dimension." // *Cause: // *Action: 33213, 00000, "(CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values." // *Cause: The user specified a BEFORE or AFTER clause specifying a position in // the range of SESSION dimension values. // *Action: Do not use a position clause, or specify a position before the // first SESSION value. 33214, 00000, "(CINSERT02) The %j dimension is too large." // *Cause: The dimension has too many values. // *Action: Deleted values can still take up space in the dimension and cause // this error. Try removing the deleted values by exporting the // dimension to EIF and reimporting it with the REPLACE DELETE option. 33215, 00000, "(CINSERT07) You cannot add session-only values to the %j dimension." // *Cause: The user tried to add a SESSION dimension value while a spreadsheet // spreadsheet cursor was open. // *Action: Try adding the SESSION value while the cursor is not active. 33216, 00000, "(CINSERT03) %a %j %ld\nThe %1p dimension does not have a value numbered %2p." // *Cause: // *Action: 33217, 00000, "(CINSERT20) %a %j\nCustom member values cannot be added to concat dimension %1p, or to any of its bases, because it is not defined as UNIQUE." // *Cause: Only UNIQUE concat dimensions can have custom member values. // *Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry. 33218, 00000, "(CINSERT04) %a %K %j %d %d\n%1p is not a valid value for the %2p dimension. Values for this dimension can have at most %3p significant digits after rounding to %4p decimal places." // *Cause: The user attempted to insert a value that // had too many digits into a NUMBER dimension. For instance, the user might have tried to insert the // value 99999 (5 digits) into a dimension with data type NUMBER(4). // *Action: Use a smaller number for the dimension value, or define a // new dimension with a larger precision and replace the old dimension // with the new one. 33219, 00000, "(CINSERT05) %a %K %j %j %j\n%1p cannot be added to %2p because it is already a value of the dependent UNIQUE concat dimension %3p, from leaf dimension %4p." // *Cause: A value cannot be added to a dimension if it conflicts with an // existing value in a unique concat dimension containing this dimension. // *Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, // or either of the duplicate values could be renamed to make them UNIQUE. 33220, 00000, "(CLOPEN01) %a %j %s\nThe time dimension %1p cannot be accessed because it consists of time periods not recognized in this release of %2p." // *Cause: // *Action: 33222, 00000, "(CLOPEN02) %a %j %s\nThe dimension %1p cannot be accessed because it was created by an incompatible version of %2p." // *Cause: // *Action: 33223, 00000, "(CMOVE03) You cannot move a session-only dimension value." // *Cause: The user named a SESSION dimension value in the MAINTAIN MOVE // command. // *Action: Do not try to MAINTAIN MOVE session-only dimension values. 33224, 00000, "(CMOVE02) %a %j %ld\nThe %1p dimension does not have a value at position %2p." // *Cause: // *Action: 33226, 00000, "(COLDEL01) %a %d %d\nThe starting column must be between 1 and the maximum width of a text value (%1p). You cannot start removing at column %2p." // *Cause: // *Action: 33228, 00000, "(COLDEL02) %a %d %d\nThe columns to be removed must be between 1 and the maximum width of a text value (%1p). You cannot remove column %2p." // *Cause: // *Action: 33230, 00000, "(COLDEL03) The number of columns to be removed must be greater than zero. You cannot remove %d columns." // *Cause: // *Action: 33232, 00000, "(COLEXTR01) %a %d %d\nThe starting column must be between 1 and the maximum width of a text value (%1p). %2p is out of range." // *Cause: // *Action: 33234, 00000, "(COLEXTR02) %a %d %d\nThe columns to be extracted must be between 1 and the maximum width of a text value (%1p). You cannot extract column %2p." // *Cause: // *Action: 33236, 00000, "(COLEXTR03) The number of columns to be extracted must be greater than or equal to zero. You cannot extract %d columns." // *Cause: // *Action: 33238, 00000, "(COLINS01) %a %d %d\nThe starting column must be between 0 and the maximum width of a text value (%1p). You cannot start inserting at column %2p." // *Cause: // *Action: 33240, 00000, "(COLREP01) %a %d %d\nThe starting column must be between 1 and the maximum width of a text value (%1p). You cannot start replacing at column %2p." // *Cause: // *Action: 33242, 00000, "(COMPOSITE01) %j is a dimension composite and does not have position numbers that can be used in this context." // *Cause: // *Action: 33243, 00000, "(XSDPART51) %j is a PARTITION TEMPLATE and does not have position numbers that can be used in this context." // *Cause: // *Action: 33244, 00000, "(CRENAME01) %a %j %ld\nThe %1p dimension does not have a value at position %2p." // *Cause: // *Action: 33246, 00000, "(CRENAME02) The %j dimension does not have identifiers that can be renamed." // *Cause: // *Action: 33247, 00000, "(CRENAME03) %a %K %j %j\n%1p is already a value of the dependent UNIQUE concat dimension %2p, from leaf dimension %3p." // *Cause: A value cannot be renamed in a dimension if the new value conflicts with an // existing value in a unique concat dimension containing this dimension. // *Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, // or either of the duplicate values could be changed to make them UNIQUE. 33248, 00000, "(CTDDEL04) %a %j %d\nDeletions from time dimension %1p must occur at either end. %2p values were not deleted." // *Cause: // *Action: 33250, 00000, "(CTDINSRT00) You attempted to add a value that was outside the allowable range of dates for time dimension %j." // *Cause: // *Action: 33252, 00000, "(CTXENG00) The CONTEXT name cannot be NA." // *Cause: // *Action: 33254, 00000, "(CTXENG01) CONTEXT '%v' already exists." // *Cause: // *Action: 33256, 00000, "(CTXENG02) CONTEXT '%v' does not exist." // *Cause: // *Action: 33258, 00000, "(CTXENG03) %a %n %v\n%1p has not been saved in CONTEXT '%2p'." // *Cause: // *Action: 33260, 00000, "(DIMSHOW01) Partition %v does not exist." // *Cause: The DIMSHOW command specified a nonexistent partition. // *Action: Specify the name of an existing partition, or remove the PARTITION // qualification from the DIMSHOW command. 33261, 00000, "(DIMSHOW02) A partition name may be specified only for a partitioned variable." // *Cause: A PARTITION qualification was provided for an object other than a // partitioned variable. // *Action: Remove the PARTITION qualification. 33262, 00000, "(DBERR01) Analytic workspace %s does not exist." // *Cause: The analytic workspace requested does not seem to be in the current // database // *Action: Check that you are in the correct schema and have access to the // requested AW. 33263, 00000, "Could not create analytic workspace %s" // *Cause: A serious error was encountered while trying to set up the // tables for the named analytic workspace. Possibilities include // a tablespace that can't be written to, corrupted metadata // about which AWs exist, bogus tables with names the code expects // to be able to use, or the remains of a partially removed AW. // *Action: There should be another error on the error stack. Consult it to // determine what is causing the problem and remove that table. 33264, 00000, "(DBERR02) %a %s %s\nAnalytic workspace %1p cannot be accessed because it has been damaged or belongs to an incompatible version of %2p." // *Cause: // *Action: 33265, 00000, "(DBERRBSZ) %a %s %d %d\nAnalytic workspace %1p cannot be opened. Tablespace blocksize %2p does not match database cache size %3p." // *Cause: The blocksize of the containing tablespace didn't match database cache size. // *Action: Change either size to make them consistent, or set olap_page_pool_size to 0 to allow automatic OLAP pool management when compatibility is greater than 10.2. 33266, 00000, "(DBERR03) %a %s %s\nAnalytic workspace %1p cannot be accessed because it was last modified by an incompatible version of %2p." // *Cause: // *Action: 33267, 00000, "(DBERRRLS) %a %s\nAnalytic workspace %1p cannot be accessed because it has fine-grained access control applied to it" // *Cause: An attempt was made to access the specified analytic workspace's // LOB table. The OLAP option detected the table had fine-grained // security applied to it. The OLAP option requires full access to // this table to operate correctly. // *Action: Remove the fine-grained access control. 33268, 00000, "(DBERRTHW) Analytic workspace %s cannot be attached with the THAW option because it was frozen with the NOTHAW option" // *Cause: An attempt to attach the AW using the thaw option was made; the AW // was frozen using the NOTHAW option. // *Action: Either attempt the command again without the THAW option. 33269, 00000, "while operating on '%s'" // *Cause: Error is raised to inform user what object was being worked on // when an error occurred during the creation of an AW. It should // always be signaled with 33263 // *Action: See error#33263 33270, 00000, "(DBERR05) Analytic workspace %s already exists." // *Cause: The AW CREATE command was passed the name of an analytic // workspace that already exists // *Action: Specify a different name. 33271, 00000, "simulated paging error" // *Cause: This is an internal error that should never be seen // *Action: Contact Oracle technical support 33272, 00000, "(DBERR06) Analytic workspace %s cannot be opened." // *Cause: // *Action: 33273, 00000, "(XSCHKRLS01) Analytic workspace %s has open cursors and cannot be detached." // *Cause: A session attempted to detach an analytic workspace while there // are cursors open against it. // *Action: Close the open cursor before attempting to close the analytic // workspace. 33274, 00000, "(DBERR07) %a %s %s\nTimed out while trying to lock analytic workspace %1p for %2p." // *Cause: A lock operation that was supposed to happen very quickly was taking too long. It can be due to another session being stopped while holding that lock, another session crashing while holding that lock, or an internal error. // *Action: If another session is stopped, resume that session to let it release the lock. If another session has crashed, wait for a few minutes while PMON or SMON process is recovering that lock. Contact Oracle OLAP Support if none of the situations above apply. 33275, 00000, "Autonomous transaction query of an UPDATEd analytic workspace is not supported" // *Cause: The user made attempt to reference an anayltic workspace that has uncommited updates within an autonomous query. // *Action: Either COMMIT or ROLLBACK your uncommited changes, or don't use an autonomous transaction. 33276, 00000, "(DBERR08) Another user has analytic workspace %s attached." // *Cause: // *Action: 33278, 00000, "(DBERR09) Analytic workspace %s cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back." // *Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in MULTI mode. // *Action: Either try attaching the workspace is RO or MULTI mode or commit or roll back the transaction before trying to attach the workspace in RW or EXCLUSIVE mode. 33280, 00000, "(DBERR10) Analytic workspace %s cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back." // *Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in RW or EXCLUSIVE mode. // *Action: Either try attaching the workspace is RO, RW, or EXCLUSIVE mode or commit or roll back the transaction before trying to attach the workspace in MULTI mode. 33282, 00000, "(DBERR11) Cannot wait for analytic workspace %s to become available since doing so would cause a deadlock." // *Cause: Trying to wait for the workspace to become available caused a deadlock. // *Action: Release an analytic workspace that some other user might be waiting for before proceeding to attach this analytic workspace in this mode. 33284, 00000, "(DBERR12) %a %s %s\nAnalytic workspace %1p cannot be opened in MULTI mode before converting it by the latest version of %2p." // *Cause: The AW is stored in 9i format. // *Action: Convert the AW to a later format 33286, 00000, "(DBERR14) The specified access mode for analytic workspace %s is invalid." // *Cause: // *Action: 33288, 00000, "(DBERR15) Another user has incompatible access to analytic workspace %s, and the wait timeout has expired." // *Cause: An attempt to access an analytic workspace conflicted with another // user's access, and the timeout specified has elapsed. // *Action: Wait until the conflicting user is done. 33290, 00000, "(DBERR17) Analytic workspace %s cannot be attached in the mode you requested because another user has it attached in an incompatible mode." // *Cause: An attempt to access an analytic workspace conflicted with another // user's access, and no timeout was specified // *Action: Wait until the conflicting user is done. 33291, 00000, "(DBERRSYNC) Analytic workspace %s cannto be attached RW until a RESYNC command has brought it up to the current generation." // *Cause: Another session has updated the analytic workspace since it was // attached in the current session. // *Action: Execute a RESYNC AW command to bring the analytic workspace up to // the most recent version. 33292, 00000, "(DBERR18) Insufficient permissions to access analytic workspace %s using the specified access mode." // *Cause: You do not have sufficient permissions to access this // analytic workspace in the desired mode. // *Action: Ask the owner of the schema or OLAP DBA to grant you // sufficient permissions to access the {SCHEMA}.AW${AWNAME} // table (for example, SCOTT.AW$FOO table). 33293, 00000, "Please use the OLAP command AW TRUNCATE to truncate this table." // *Cause: This table is part of an analytic workspace, and the OLAP option // needs to control the truncation of the table. // *Action: use the OLAP option to truncate the table. 33294, 00000, "(DBERR19) Analytic workspace %s cannot be created, deleted, or renamed while flashback mode is in effect." // *Cause: // *Action: 33295, 00000, "(DBERR20) An attached analytic workspace is blocking this command." // *Cause: A table cannot be dropped because an analytic workspace based on this table is being attached. // *Action: Look up the session in question in GV$AW_OLAP and kill it. 33296, 00000, "(DBERR21) Analytic workspace %s can only be attached RO while tablespace %s is READONLY." // *Cause: The underlying tablespace of the analytic workspace is in READONLY status. // *Action: Attach the analytic workspace in RO mode or alter the tablespace. 33297, 00000, "(DBERR22) %a %s %s\nAnalytic workspace %1p cannot be opened because it was last modified by an incompatible version of %2p." // *Cause: The user attempted to attach an old OLAP Services analytic workspace that // cannot be converted by this version of OLAP Services. // *Action: Either create a new analytic workspace or try using a version of OLAP // Services compatible with the one that created this analytic workspace. 33298, 00000, "(AWUPG01) Analytic workspace %s is already in the newest format allowed by the current compatibility setting" // *Cause: User ran the DBMS_AW.CONVERT procedure on an analytic workspace // that was created in or previously upgraded to the current // compatibility mode. // *Action: If upgrading the analytic workspace is necessary, upgrade // the database instance and then re-run DBMS_AW.CONVERT. If the // new features offered by upgrading the analytic workspace // are not required, then no action is needed. 33299, 00000, "Please use DBMS_AW.AW_RENAME to rename this table." // *Cause: This table is part of an analytic workspace, and the OLAP option // needs to control the rename of the table. // *Action: use the OLAP option to rename the table. 33302, 00000, "(DBVALID01) SEVERE ERROR: Record %.0f multiply used." // *Cause: The AW VALIDATE command has detected an error in the structure // of the analytic workspace. This error will result in the // corruption of one or more objects // *Action: Export what you can of the analytic workspace. 33304, 00000, "(DBVALID02) Note: Record %.0f was allocated but not used. This can result in wasted space." // *Cause: This is a benign message. The AW VALIDATE command found an // analytic workspace has some inaccessible space. // *Action: Either nothing, or export and recreate the analytic workspace 33305, 00000, "(DBVALID06) Note: Record %.0f was allocated but not used. This can result in wasted space. (PS %ld)" // *Cause: This is a benign message. The AW VALIDATE command found an // analytic workspace has some inaccessible space. // *Action: Either nothing, or export and recreate the analytic workspace 33306, 00000, "(DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace %s." // *Cause: The AW VALIDATE command does not support read-only access. // *Action: Attach the analytic workspace read/write and try again. 33308, 00000, "(DBVALID04) SEVERE ERROR: Record %.0f used but not allocated" // *Cause: The AW VALIDATE command has detected a problem that will result // in corruption of the analytic workspace. There is no corruption // yet. // *Action: Export and recreate the analytic workspace. 33309, 00000, "(DBVALID05) SEVERE ERROR: Record %.0f used but not allocated (PS %ld)" // *Cause: The AW VALIDATE command has detected a problem that will result // in corruption of the analytic workspace. There is no corruption // yet. // *Action: Export and recreate the analytic workspace. 33310, 00000, "(DECIMAL) %a %d %d %d %d\nThe number of decimal places must be between %2p and %3p, or %4p. It cannot be %1p." // *Cause: // *Action: 33312, 00000, "(DELDENT01) %n cannot be deleted while there are objects dimensioned by it, or formulas, programs, valuesets, or relations that use it." // *Cause: // *Action: 33313, 00000, "(DELDENT05) %n cannot be deleted because it is the target of an external partition of a partitioned variable." // *Cause: User attempted to delete a variable, but some partitioned variable // was defined to use that variable as the target of one of its // external partitions. // *Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the // the external partition from the partitioned variable, then // delete the target variable. 33314, 00000, "(DELDENT02) %n cannot be deleted while it is executing." // *Cause: // *Action: 33315, 00000, "(XSDELDENTANON) %a %n %j\nYou cannot delete %1p while looping over unnamed composite %2p." // *Cause: While looping over the named anonymous composite, an attempt was // made to delete an object which is dimensioned by it. // *Action: Delete the object outside of a loop over the dimension. 33316, 00000, "(DELDENT03) You cannot delete %n because you do not have PERMIT permission for it or it is readonly." // *Cause: // *Action: 33318, 00000, "(DELDENT04) The variable %n cannot be deleted while its NA trigger is executing." // *Cause: // *Action: 33320, 00000, "(DNAMELEN00) %a %s %d\nThe object name %1p has more than %2p characters." // *Cause: // *Action: 33324, 00000, "(DOSCMD01) The current directory is %s." // *Cause: // *Action: 33325, 00000, "(DOSCMD02) Current directory alias is not set." // *Cause: // *Action: 33332, 00000, "(DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again." // *Cause: There is no currently active analytic workspace. The command // that generated the error requires an active analytic workspace // to operate on. // *Action: Execute an AW ATTACH or AW CREATE command to establish an active // workspace. 33334, 00000, "(DSSEXIST04) Analytic workspace %s is not attached." // *Cause: The specified analytic workspace is currently not attached to // the session, or the name is misspelled. // *Action: Attach the analytic workspace with the AW ATTACH command, or // correct the spelling of the name . 33336, 00000, "(DSSEXIST04A) Analytic workspace %t is not attached." // *Cause: The specified analytic workspace is currently not attached to // the session, or the name is misspelled. // *Action: Attach the analytic workspace with the AW ATTACH command, or // correct the spelling of the name . 33338, 00000, "(DSSEXIST05) You cannot specify the EXPTEMP analytic workspace." // *Cause: The command requires a non-temporary analytic workspace to // operate on. // *Action: Specify an analytic workspace other than EXPTEMP. 33339, 00000, "You cannot detach analytic workspace %s. It is in use by an API branch." // *Cause: The OLAP API is in a branch, and you are not allowed to detach // the AW while the branch is active. // *Action: End the branch before detaching the AW. 33340, 00000, "(DTINFRMT00) A format cannot be an empty string." // *Cause: // *Action: 33342, 00000, "(DTINFRMT01) %a %v %s\n'%1p' is not a valid format for a %2p value because it has a single angle bracket > that is not part of a field specification." // *Cause: // *Action: 33344, 00000, "(DTINFRMT02) %a %v %s\n'%1p' is not a valid format for a %2p value because an angle bracket < cannot be the last character." // *Cause: // *Action: 33346, 00000, "(DTINFRMT03) %a %v %s %i\n'%1p' is not a valid format for a %2p value because '%3p' is an unrecognized specification." // *Cause: // *Action: 33348, 00000, "(DTINFRMT04) %v is not a valid format because the B specifier cannot be used with a date." // *Cause: // *Action: 33350, 00000, "(DTINFRMT05) %a %v %i\n'%1p' is not a valid format because the '%2p' specification cannot be used with a date." // *Cause: // *Action: 33352, 00000, "(DTINFRMT06) %a %v %s\n'%1p' is not a valid format for a %2p value because the B specifier cannot be used with a period field." // *Cause: // *Action: 33354, 00000, "(DTINFRMT07) '%v' is not a valid format because the specification can only be used once." // *Cause: // *Action: 33356, 00000, "(DTINFRMT08) '%v' is not a valid VNF format because it contains an ordinal specification." // *Cause: // *Action: 33358, 00000, "(DTINFRMT09) %a %v %i\n'%1p' is an ambiguous VNF format. The '%2p' specification must be followed by a space or separation character." // *Cause: // *Action: 33360, 00000, "(DTINFRMT10) '%v' is not a valid VNF format because at least two of the specifications are of the same type." // *Cause: // *Action: 33362, 00000, "(DTINFRMT11) '%v' is not a valid VNF format because it does not contain enough fields to match one of the defined VNF templates." // *Cause: // *Action: 33364, 00000, "(DTINFRMT12) '%v' is not a valid VNF format because it contains more information than is allowed." // *Cause: // *Action: 33366, 00000, "(DTINFRMT13) %a %v %s %i\n'%1p' is not a valid format for a %2p value because the '%3p' specification has no closing angle bracket >." // *Cause: // *Action: 33368, 00000, "(DTINFRMT14) %a %v %s\n'%1p' is not a valid format for a %2p value because it contains more than one line of text." // *Cause: // *Action: 33370, 00000, "(DTTOVC01) Unable to print dates longer than %d characters." // *Cause: // *Action: 33372, 00000, "(DUPCLCHK01) %j appears more than once in the dimension list." // *Cause: // *Action: 33374, 00000, "(DUPCLCHK02) %a %j %j\n%1p appears more than once in the dimension list. (It is also a base dimension of %2p.)" // *Cause: // *Action: 33376, 00000, "(DUPCLCHK03) %a %j %j %j\n%1p and %2p cannot both appear in a dimension list because they share at least one base dimension (%3p)." // *Cause: // *Action: 33381, 00000, "(EIFEXPRT20) You cannot EXCLUDE bases from %j, because it is not a concat dimension." // *Cause: // *Action: 33382, 00000, "(EIFEXPRT01) You cannot export two objects with the same name (%s)." // *Cause: // *Action: 33383, 00000, "(EIFEXPRT21) %a %j %j\nYou cannot EXCLUDE %1p because it is not a base of %2p." // *Cause: // *Action: 33384, 00000, "(EIFEXPRT02) You cannot rename a dimension (%q) when you export it." // *Cause: // *Action: 33385, 00000, "(EIFEXPRT22) You cannot EXCLUDE %q, because it is not a dimension." // *Cause: // *Action: 33386, 00000, "(EIFEXPRT03) The expression beginning with %t has no data type." // *Cause: // *Action: 33387, 00000, "(EIFEXPRT23) EXCLUDE or EXCLUDING can only be used following the name of a concat dimension." // *Cause: // *Action: 33388, 00000, "(EIFEXPRT04) The expression beginning with %t has too many dimensions." // *Cause: // *Action: 33389, 00000, "(EIFEXPRT24) %a %j %d %d\nConcat dimension %1p has %2p bases. You cannot EXCLUDE more than %3p of them." // *Cause: // *Action: 33390, 00000, "(EIFEXPRT05) There are no objects to export." // *Cause: // *Action: 33391, 00000, "(EIFEXPRT25) concat dimension %j has only 1 base, which cannot be EXCLUDED." // *Cause: // *Action: 33392, 00000, "(EIFEXPRT07) SCATTER name %q must be a text variable of one dimension shared with the expression." // *Cause: // *Action: 33394, 00000, "(EIFEXPRT08) SCATTER type %q must be a text variable with the same dimension as the name." // *Cause: // *Action: 33396, 00000, "(EIFEXPRT09) The SCATTER expression must have at least two dimensions and be numeric if TYPE is given." // *Cause: // *Action: 33398, 00000, "(EIFEXPRT10) The SCATTER type value must be INTEGER, SHORTINTEGER, SHORT, or DECIMAL, not %v." // *Cause: // *Action: 33400, 00000, "(EIFEXPRT11) The scatter name value %v is not a valid EIF object name." // *Cause: // *Action: 33402, 00000, "(EIFEXPRT12) You cannot export an unnamed dimension composite by itself, but only with an object dimensioned by it." // *Cause: // *Action: 33404, 00000, "(EIFEXPRT13) The format for exporting an expression is:\n EXPORT expression AS name" // *Cause: // *Action: 33406, 00000, "(EIFEXPRT14) %q is not a legal name for an EIF file object." // *Cause: // *Action: 33408, 00000, "(EIFEXPRT15) You cannot use the SCATTER AS syntax because EIFVERSION is set to %d, and that version cannot import scattered objects." // *Cause: // *Action: 33413, 00000, "(EIFMAKEF01) You cannot export compressed composite %j because one of its bases has limited status or a PERMIT READ restriction." // *Cause: Export of a compressed composite to an EIF file or lob failed // because one or more of the bases had some values that were not // in the current status. This can be caused either by a LIMIT // command or a PERMIT READ restriction on the dimension. // *Action: Either set the base dimensions' statuses to ALL and remove their // PERMIT READ programs, or export using the NOAGGR keyword. 33414, 00000, "(EIFMAKEF02) %a %ld %d\n\" %1p bytes written in %2p seconds.\"" // *Document: NO // *Cause: Used in formatting output for the LIST option of EXPORT // *Action: None 33416, 00000, "(EIFPATHLIST) You tried to set EIFEXTENSIONPATH to one or more illegal path names." // *Cause: // *Action: 33420, 00000, "(EIFMAKEF03) The EXPORT command has terminated because of insufficient disk space. One or more files could not be created." // *Cause: // *Action: 33422, 00000, "(EIFMAKEF04) %a %s %d %s %s\nCAUTION: Due to insufficient disk space, the extension count of the EIF files(s) could not be recorded. To avoid any potential errors when the file is imported with the IMPORT command, please DO NOT move, delete, or rename any of the EIF extension files. These are files of the form %1p.%3p, where %4p is the extension number. Please note that there are %2p such files." // *Cause: // *Action: 33424, 00000, "(EIFMAKEF05) %a %n %d\n%1p cannot be exported because EIFVERSION is set to %2p, and objects cannot have more than 6 dimensions in that version." // *Cause: // *Action: 33425, 00000, "(EIFMAKEF15) CAUTION: Exporting NTEXT objects using %s for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file." // *Cause: The user exported an object with data type NTEXT, but the EIF file that // will result from the EXPORT command is not written in Unicode. Because no // non-Unicode file can represent all possible Unicode data, it is possible // that some data will be lost when converting from the Unicode NTEXT object // to the EIF file. The EIF file will be written in the character set // indicated by the "nls_charset" argument of the EXPORT command, or, if // no such argument is present, in the database character set. // *Action: If the user is certain that the contents of the NTEXT object can // be represented in the specified character set, then no action is necessary. // Otherwise, the user can add "nls_charset 'UTF8'" to the EXPORT command // string. This will result in the EIF file being written in UTF8 Unicode, // which can represent all the data contained in NTEXT objects. 33426, 00000, "(EIFMAKEF06) %a %s %d\nThe expression named %1p cannot be exported because EIFVERSION is set to %2p, and objects cannot have more than 6 dimensions in that version." // *Cause: // *Action: 33427, 00000, "(EIFMAKEF16) CAUTION: NTEXT object %n will be exported with type TEXT." // *Cause: User attempted to export an object whose data type is NTEXT, but // but the EIFVERSION option indicates a version of Express / Oracle OLAP // that does not support the NTEXT data type. The object will be exported as a // TEXT object instead. // *Action: No action needed. 33428, 00000, "(EIFMAKEF07) One or more SCATTER AS expressions cannot be exported because EIFVERSION is set to %d, and objects cannot have more than 6 dimensions in that version." // *Cause: // *Action: 33429, 00000, "(EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT." // *Cause: User attempted to export an expression whose data type is NTEXT, but // but the EIFVERSION option indicates a version of Express / Oracle OLAP // that does not support the NTEXT data type. The expression will be exported // as a TEXT object instead. // *Action: No action needed. 33430, 00000, "(EIFMAKEF08) %a %j %d %s\n%1p cannot be exported because EIFVERSION is set to %2p, and that version does not use %3p objects." // *Cause: // *Action: 33432, 00000, "(EIFMAKEF09) %a %s %d %d\nYou cannot use the name %1p, because EIFVERSION is set to %2p. That version does not allow object names longer than %3p bytes." // *Cause: // *Action: 33434, 00000, "(EIFMAKEF10) %a %n %s\nYou cannot export the AGGMAP object %1p from this version of %2p to version 6.3. The internal format of an AGGMAP has changed too much." // *Cause: // *Action: 33436, 00000, "(EIFMAKEF11) %a %s %d\nYou cannot write an EIF file using the %1p character set, because EIFVERSION is set to %2p. That version does not support that character set." // *Cause: // *Action: 33438, 00000, "(EIFSPARS00) %a %d %j\n%1p values of %2p will be exported as NA, because they are not in the current status of its base dimensions." // *Cause: // *Action: 33440, 00000, "(EQUPDATE01) The expression for formula %j contains invalid syntax." // *Cause: // *Action: 33442, 00000, "(ESDREAD01) Discarding compiled code for %j because there is no NAME dimension." // *Cause: // *Action: 33443, 00000, "(ESDREAD14) %a %j %s\nDiscarding compiled code for %1p because analytic workspace %2p is not attached." // *Cause: A program used an analytic workspace name in a qualified object // name. The named analytic workspace is not attached at program run time. // *Action: No action necessary. The program will be automatically // recompiled. It is likely that the recompile will fail with an appropriate // exception code, in which case the signaled condition should be // corrected and the program re-run. 33444, 00000, "(ESDREAD02) %a %j %v\nDiscarding compiled code for %1p because %2p could not be found." // *Cause: // *Action: 33445, 00000, "(ESDREAD15) %a %j %j %j\nDiscarding compiled code for %1p because %2p and %3p, which were not partition-dependent when the code was compiled, are now partition-dependent." // *Cause: Two variables are "partition-dependent" if they share any // external partition target variables, or if one is the target of // an external partition of the other. If object names referred to // non-partition-dependent variables at compile time but refer to // partition-dependent variables in the run-time context, the // OLAP DML program, formula, or model will be automatically // recompiled. // *Action: None needed. 33446, 00000, "(ESDREAD03) %a %j %v %s\nDiscarding compiled code for %1p because %2p is now a %3p. It was another kind of object when the code was compiled." // *Cause: // *Action: 33447, 00000, "(ESDREAD16) %a %j %j %j\nDiscarding compiled code for %1p because %2p and %3p, which were partition-dependent when the code was compiled, are now not partition-dependent." // *Cause: Two variables are "partition-dependent" if they share any // external partition target variables, or if one is the target of // an external partition of the other. If object names referred to // partition-dependent variables at compile time but refer to // non-partition-dependent variables in the run-time context, the // OLAP DML program, formula, or model will be automatically // recompiled. // *Action: None needed. 33448, 00000, "(ESDREAD04) %a %j %v %s %s\nDiscarding compiled code for %1p because %2p now has %3p data, whereas it had %4p data when the code was compiled." // *Cause: The datatype of the specified variable has changed. // *Action: None needed. 33449, 00000, "(ESDREAD17) %a %j %v\nDiscarding compiled code for %1p because the partition method or partition dimension of %2p has changed since it was compiled." // *Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition // dimension of the partition template is sufficiently different // from what it was when the code was compiled that the code must // be recompiled. // *Action: None needed. 33450, 00000, "(ESDREAD05) %a %j %v\nDiscarding compiled code for %1p because %2p now has more or fewer dimensions than it had when the code was compiled." // *Cause: The dimensionality of the specified object has changed. // *Action: None needed. 33452, 00000, "(ESDREAD06) %a %j %v %j %j\nDiscarding compiled code for %1p because %2p is now dimensioned by %3p. It was dimensioned by %4p when the code was compiled." // *Cause: The dimensionality of the specified object has changed. // *Action: None needed. 33454, 00000, "(ESDREAD07) %a %j %v %s %j %s %j\nDiscarding compiled code for %1p because %2p is now %3p %4p, whereas it was %5p %6p when the code was compiled." // *Cause: The specified object has changed. // *Action: None needed. 33456, 00000, "(ESDREAD08) %a %j %v %s %s\nDiscarding compiled code for %1p because %2p is a(n) %3p, which %4p did not expect to find in a compiled program." // *Cause: The type of the specified object has changed. // *Action: None needed. 33458, 00000, "(ESDREAD09) %a %j %v %s %s\nDiscarding compiled code for %1p because %2p is now type %3p, whereas it was type %4p when the code was compiled." // *Cause: The type of the specified object has changed. // *Action: None needed. 33460, 00000, "(ESDREAD10) %a %j %j %s\nDiscarding compiled code for %1p because object %2p is not in analytic workspace %3p." // *Cause: The specified object is not in the same analytic workspace it // was in when the compiled object was compiled. // *Action: None needed. 33462, 00000, "(ESDREAD10A) %a %j %v %s\nDiscarding compiled code for %1p because object %2p is not in analytic workspace %3p." // *Cause: The specified object was not in the same analytic workspace it // was when the compiled object was compiled // *Action: None needed. 33464, 00000, "(ESDREAD11) %a %j %j\nDiscarding compiled code for %1p because two external objects that were different at compile time are now the same object (%2p)." // *Cause: // *Action: 33466, 00000, "(ESDREAD12) %a %j %v %d\nDiscarding compiled code for %1p because model dimension %2p is not in the same analytic workspace as solution variable %3p." // *Cause: // *Action: 33468, 00000, "(ESDREAD13) %a %j %v %j\nDiscarding compiled code for %1p because %2p is no longer a surrogate of dimension %3p." // *Cause: When the compiled code was saved, the specified object was a // surrogate of a certain dimension. Now the specified object is a // surrogate of a different dimension. // *Action: No action needed; program automatically recompiles. 33472, 00000, "(EXPCHECK1) The %n formula cannot be edited or compiled while it is executing." // *Cause: // *Action: 33474, 00000, "(EXPCOMP01) The calculation expression in formula %n contains a format error." // *Cause: // *Action: 33475, 00000, "(EXPCOMP02) Invalid expression." // *Cause: // *Action: 33476, 00000, "(EXPORT00) Target file (%s) already exists. No data is being exported." // *Cause: // *Action: 33478, 00000, "(FCFINI02) Too many NA values exist in the input data; %s cannot fill them all." // *Cause: // *Action: 33480, 00000, "(FCFINI04) An error occurred while filling in the NA values in the input data." // *Cause: // *Action: 33482, 00000, "(FCFINI05) Calculation of starting values and handling of NA values in the input data require at least two cycles of input data." // *Cause: // *Action: 33484, 00000, "(FCFINI06) An error occurred while calculating starting values for the smooth, trend, and seasonal series." // *Cause: // *Action: 33486, 00000, "(FCFINI07) %s cannot calculate starting values from this input data." // *Cause: // *Action: 33488, 00000, "(FCFINI08) The forecast input has resulted in a divide-by-zero error in the calculation of the smoothed data series." // *Cause: // *Action: 33490, 00000, "(FCFINI09) The forecast input has resulted in a divide-by-zero error in the calculation of the seasonal index series." // *Cause: // *Action: 33492, 00000, "(FCINFO00) There is no saved forecast calculation for the INFO function to retrieve." // *Cause: // *Action: 33494, 00000, "(FCREATE01) %a %s %d\nFile %1p is already open on file unit number %2p." // *Cause: // *Action: 33508, 00000, "(FILEREAD01) Fileunit %d is invalid. FILEREAD and FILEVIEW can only access input files opened with the FILEOPEN function." // *Cause: // *Action: 33510, 00000, "(FILEREAD04) Unexpected EOF encountered in string while importing data." // *Cause: // *Action: 33512, 00000, "(FILESET01A) The value of the PAGESIZE option must be greater than the combined values of TMARGIN and BMARGIN." // *Cause: // *Action: 33514, 00000, "(FILESET02) The value of the TABEXPAND option must be between 0 and 100 inclusive. You specified %d." // *Cause: // *Action: 33516, 00000, "(FILESET04) You can set the %s attribute only if the fileunit is used exclusively for output." // *Cause: // *Action: 33520, 00000, "(FINENG01) %a %s %d\nThe number of periods specified in the %1p function must be greater then 0 and less than or equal to %2p." // *Cause: // *Action: 33522, 00000, "(FINENG02) The second argument of the %s function cannot be NA while the corresponding first argument is not NA." // *Cause: // *Action: 33524, 00000, "(FINENG03) Both the first and second arguments of the %s function must be nonnegative." // *Cause: // *Action: 33526, 00000, "(FINENG04) An asset value cannot be NA when the corresponding salvage value is not NA." // *Cause: // *Action: 33528, 00000, "(FINENG05) The asset value must be greater than the salvage value." // *Cause: // *Action: 33530, 00000, "(FINENG06) The first period depreciation strategy argument of the %s function cannot be NA." // *Cause: // *Action: 33532, 00000, "(FINENG07) The first period depreciation strategy argument of the %s function must evaluate to the word FULL or HALF." // *Cause: // *Action: 33534, 00000, "(FINENG08) The rate argument of payment or interest function cannot be NA while the corresponding principal argument is not NA." // *Cause: // *Action: 33536, 00000, "(FINENG09) Both the principal and rate arguments of the payment and interest functions must be nonnegative." // *Cause: // *Action: 33538, 00000, "(FINENG10) An internal error (%d) has occurred while evaluating an interest or payment function." // *Cause: // *Action: 33540, 00000, "(FINENG11) The decline-factor argument must be greater than 0." // *Cause: // *Action: 33542, 00000, "(FISOPEN01) A file identifier cannot exceed %d characters." // *Cause: // *Action: 33546, 00000, "(FNAMEQRY01) You must specify a file unit number for the %s option of FILEQUERY." // *Cause: // *Action: // 33554 to 33559 reserved for FORCHECK, MAINTCHK, LOCKCHECK 33554, 00000, "(FORCHECK01) While looping over %j, you cannot change its status or contents." // *Cause: // *Action: 33555, 00000, "(FORCHECK03) While looping over alias dimension %j, you cannot change the contents of its base %j." // *Cause: // *Action: 33556, 00000, "(FORCHECK51) While looping over concat dimension %j, you cannot change the contents of its leaves." // *Cause: // *Action: 33557, 00000, "(MAINTCHK01) %a %s %j\nYou cannot %1p values of dimension %2p during a loop over it." // *Cause: User tried to insert or delete a value of the specified dimension // while some loop over that dimension was active. The loop could // be an explicit FOR or ACROSS loop, or a natural expression // evaluation or OLAP_TABLE loop. Also, it could be a loop over the // dimension itself or over a derived dimension (like a composite // or partition template) or dimension alias that includes it. The // insert or delete could be explicitly caused by the MAINTAIN // command. It is also possible that the user attempted to assign // a value to a variable or partition dimensioned by a composite // during a loop over that composite using a qualified data // reference (QDR), and that the exception was generated by the // engine's attempt to insert a new position in the composite to // hold the new value. // *Action: Move the dimension maintenance or QDR-based variable assignment // outside the dimension loop. 33558, 00000, "(LOCKCHECK01) %a %j %k\nThe status or contents of the %1p dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to %2p." // *Cause: A LIMIT or MAINTAIN was attempted on the named language dimension // while the boolean option LOCK_LANGUAGE_DIMS was set to YES. // *Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or LIMIT. 33560, 00000, "(FORECAST00) The time dimension (%n) has no values in status. The forecast cannot be calculated." // *Cause: // *Action: 33562, 00000, "(FORECAST01) The forecast LENGTH must be an non-NA value that is greater than or equal to zero." // *Cause: // *Action: 33564, 00000, "(FORECAST02) %a %d %d\nSum of forecast LENGTH and number of time dimension values in status equals %1p. The maximum is %2p." // *Cause: // *Action: 33566, 00000, "(FORECAST03) The values of ALPHA, BETA, and GAMMA must be greater than zero and less than or equal to one." // *Cause: // *Action: 33568, 00000, "(FORECAST04) The forecast PERIODICITY must be greater than or equal to 2." // *Cause: // *Action: 33570, 00000, "(FORECAST05) The forecast PERIODICITY must be less than or equal to the number of historical observations in the input data." // *Cause: // *Action: 33572, 00000, "(FORECAST07) In a forecast calculation, the time dimension (%v) must have consecutive values in status." // *Cause: // *Action: 33574, 00000, "(FORECAST09) %a %v %d\nThe forecast length extends beyond the end of the time dimension (%1p). Only %2p values will be calculated." // *Cause: // *Action: 33576, 00000, "(FORECAST10) The number of non-NA observations must be greater than 1 to calculate a TREND forecast." // *Cause: // *Action: 33578, 00000, "(FORECAST11) The number of positive observations must be greater than 1 to calculate an EXPONENTIAL forecast." // *Cause: // *Action: 33580, 00000, "(FORECAST12) %a %d %n %d\nThe number of historical periods (%1p) exceeds the number of values in the current status of %2p (%3p)." // *Cause: // *Action: 33582, 00000, "(FORECAST13) The number of historical periods must be a non-NA value greater than zero." // *Cause: // *Action: 33584, 00000, "(FORECAST100) Forecasting Analysis" // *Cause: // *Action: 33586, 00000, "(FORECAST101) Variable to Forecast:" // *Cause: // *Action: 33588, 00000, "(FORECAST102) Forecast Dimension:" // *Cause: // *Action: 33590, 00000, "(FORECAST103) Forecast Method:" // *Cause: // *Action: 33592, 00000, "(FORECAST104) Mean Absolute Percent Error:" // *Cause: // *Action: 33594, 00000, "(FORECAST105) Forecast Equation: " // *Cause: // *Action: 33596, 00000, "(FORECAST106) No forecast values can be shown since no FCNAME variable was specified to hold the results of the forecast." // *Cause: // *Action: 33598, 00000, "(FORECAST107) Actual Value" // *Cause: // *Action: 33600, 00000, "(FORECAST108) Fitted Value" // *Cause: // *Action: 33602, 00000, "(FORECAST109) Alpha: " // *Cause: // *Action: 33604, 00000, "(FORECAST110) Beta: " // *Cause: // *Action: 33606, 00000, "(FORECAST111) Gamma: " // *Cause: // *Action: 33608, 00000, "(FORECAST112) Periodicity: " // *Cause: // *Action: 33610, 00000, "(FORSTEP01) Program control transferred into a FOR loop from outside the loop. This transfer is not allowed." // *Cause: // *Action: 33612, 00000, "(FPUTENG01) The file unit operand of the FILEPUT command does not have a value." // *Cause: // *Action: 33614, 00000, "(FPUTENG02) File %s was opened for input only." // *Cause: // *Action: 33616, 00000, "(FPUTENG04) The FROM file unit operand of the FILEPUT command does not have a value." // *Cause: // *Action: 33618, 00000, "(FPUTENG05) There is not sufficient room on the page to write data. Check your PAGESIZE, TMARGIN, BMARGIN and header values." // *Cause: // *Action: 33620, 00000, "(FRACRPOS01) %a %s %s\n%1p is not a valid field option for a record in %2p format." // *Cause: // *Action: 33622, 00000, "(FRAPPEND01) You cannot specify a position when appending to an INTEGER dimension." // *Cause: // *Action: 33624, 00000, "(FRASSIGN01) %q is a WORKSHEET. You cannot use the Data Reader to assign values to it." // *Cause: // *Action: 33625, 00000, "(FRASSIGN02) You cannot use the APPEND keyword with concat dimension %j." // *Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD, // SQL FETCH or SQL SELECT command. // *Action: APPENDing a value to one of the CONCATs leaves automatically appends to the CONCAT. 33626, 00000, "(FRATPUSH01) %a %s %s\n%1p is not a valid field option for a record in %2p format." // *Cause: // *Action: 33628, 00000, "(FRATPUSH02) Dimension maintenance attributes can only be specified on the left side of the equal sign." // *Cause: // *Action: 33630, 00000, "(FRCBCHEK01) Invalid file unit %d. Files read by FILEREAD or FILEVIEW must be input files opened via the FILEOPEN function." // *Cause: // *Action: 33632, 00000, "(FRCBCHEK02) No current record is available for file unit %d." // *Cause: // *Action: 33634, 00000, "(FRCBSET01) %a %i %s\n%1p is not a valid value for the ORIGIN option of FILESET. Valid values are: %2p." // *Cause: // *Action: 33636, 00000, "(FRERROR01) %a %d %s\n%1p is not a valid value for %2p. Values for this attribute cannot be less than 1." // *Cause: // *Action: 33638, 00000, "(FRERROR02) %a %d %s %d\n%1p is not a valid value for SPACE because it results in a %2p value of %3p." // *Cause: // *Action: 33640, 00000, "(FRERROR03) %a %d %d %d\nThere is no field of width %1p at column %2p. The current record is only %3p bytes long." // *Cause: // *Action: 33642, 00000, "(FRERROR04) %a %d %s %s\n%1p is not a valid width for %2p %3p data." // *Cause: // *Action: 33644, 00000, "(FRERROR05) %a %s %s\nNA is not a valid width for %1p %2p data. There is no default width for this data type." // *Cause: // *Action: 33646, 00000, "(FRERROR06) %a %s %s\nThe string '%1p' is not a valid %2p value." // *Cause: // *Action: 33648, 00000, "(FRERROR07) The current packed field contains the invalid hexadecimal digit \"%c\"." // *Cause: // *Action: 33650, 00000, "(FRERROR08) The current packed field contains the invalid sign digit \"%c\"." // *Cause: // *Action: 33652, 00000, "(FRERROR09) %a %k %j\n%1p is not a valid %2p." // *Cause: // *Action: 33654, 00000, "(FRERROR10) %a %j %d\nThe %1p dimension does not have a value numbered %2p." // *Cause: // *Action: 33656, 00000, "(FRERROR11) The time dimension %j is empty. You cannot append integer positions to it unless it has at least one value." // *Cause: // *Action: 33658, 00000, "(FRFILPUT01) File %s is invalid. Source files for FILEPUT must be input files opened via the FILEOPEN function." // *Cause: // *Action: 33660, 00000, "(FRFILPUT02) %a %s %s\nYou cannot write from file %1p to file %2p, because the output file was not opened with the BINARY option." // *Cause: // *Action: 33662, 00000, "(FRFILPUT03) %a %s %s\nYou cannot write from file %1p to file %2p, because the output file was opened with the BINARY option." // *Cause: // *Action: 33664, 00000, "(FRSPARSE01) You cannot specify a dimension list for %j because it is not a conjoint dimension." // *Cause: // *Action: 33666, 00000, "(FRSTRDLM01) The %s expression cannot have more than one line." // *Cause: // *Action: 33668, 00000, "(FRSTRDLM02) %a %v %s\n%1p is not a valid value for the %2p expression." // *Cause: // *Action: 33670, 00000, "(FRSTRDLM03) The %s and DELIMITER expressions cannot have the same value." // *Cause: // *Action: 33672, 00000, "(FRSTRDLM04) A CSV DELIMITER cannot be set to a double quote or NULL." // *Cause: // *Action: 33674, 00000, "(FTCODE00) %a %d %d\nData block size %2p exceeds the maximum size of %1p." // *Cause: // *Action: 33678, 00000, "(GETSCAL00) The text expression specifying a DIMENSION data type cannot evaluate to NA." // *Cause: // *Action: 33680, 00000, "(GETTIMER00) first" // *Cause: // *Action: 33682, 00000, "(GETTIMER01) %a %t %v\nThe %2p parameter to %1p is dimensioned by more than one time dimension." // *Cause: // *Action: 33684, 00000, "(GETTIMER02) %a %t %v\nThe %2p parameter to %1p must be dimensioned by a time dimension, or an explicit time dimension must be given." // *Cause: // *Action: 33686, 00000, "(GETTIMER03) %a %t %j %v\nThe %3p parameter to %1p is not dimensioned by %2p." // *Cause: // *Action: 33688, 00000, "(GETTIMER04) The dimension composite %j cannot be used as a time dimension." // *Cause: // *Action: 33690, 00000, "(GETXVAL01) The formula %n cannot be recursively evaluated because the RECURSIVE option is set to NO." // *Cause: // *Action: 33692, 00000, "(GROWENG01) The growrate of an expression must be calculated over a strictly increasing time interval." // *Cause: // *Action: 33694, 00000, "(GROWENG02) The expression in the GROWRATE function must have non-NA values at the beginning and end of the given time interval." // *Cause: // *Action: 33696, 00000, "(GROWENG03) The beginning and ending values of the expression in GROWRATE must both be positive or both be negative." // *Cause: // *Action: 33698, 00000, "(GROWENG04) Cannot calculate the growrate for the values given" // *Cause: // *Action: 33700, 00000, "(GROWENG05) The beginning value of the expression in the GROWRATE function must be non zero." // *Cause: // *Action: 33704, 00000, "(ILPCHECK01) %n is not a program." // *Cause: // *Action: 33706, 00000, "(ILPCHECK12) The %n program cannot be compiled because it contains structural errors." // *Cause: // *Action: 33708, 00000, "(ILPCHECK13) The %n program cannot be compiled while it is executing." // *Cause: // *Action: 33712, 00000, "(ILPCHECK22) The %n program cannot be executed because it contains structural errors." // *Cause: // *Action: 33720, 00000, "(ILPCHECK43) The %n program cannot be hidden or unhidden while it is executing." // *Cause: // *Action: 33722, 00000, "(ILPCOMP05) All %t statements must precede the first non-declarative statement." // *Cause: // *Action: 33724, 00000, "(ILPCOMP07) The %n program could not be compiled because of an unrecoverable error." // *Cause: // *Action: 33726, 00000, "(ILPENG02) %j cannot be used more than once in simultaneous or nested FOR statements or ACROSS commands." // *Cause: // *Action: 33728, 00000, "(ILPINIT01) You cannot initialize %j because it is currently running." // *Cause: // *Action: 33730, 00000, "(ILPLNK01) %a %j %d %d\nDiscarding compiled code for %1p because it was compiled with code version %2p. The current code version is %3p." // *Cause: // *Action: 33732, 00000, "(ILPONLY) The %s function can only be used in a program." // *Cause: // *Action: 33733, 00000, "(xsILPMLTPreOp01) The analytic workspace %s cannot be REVERTed or RESYNCed while the %s program is active." // *Cause: The AW REVERT and AW RESYNC commands cannot be used on an analytic // workspace that contains a running program. // *Action: Execute the command without running the specified program. 33734, 00000, "(ILPPUT01) %a %t %j\nLabel %1p conflicts with at least one other label in %2p. Labels must be unique for the first 8 characters." // *Cause: // *Action: 33736, 00000, "(ILPPUT02) The %j program contains unmatched DO or DOEND statements." // *Cause: // *Action: 33738, 00000, "(ILPPUT03) Program %j contains unmatched IF, WHILE, TEMPSTAT, FOR, or THEN/ELSE statement, or duplicate labels." // *Cause: // *Action: 33740, 00000, "(ILPPUT04) %a %t %j\nOn the line defining label %1p in the %2p program, text following the label has been ignored." // *Cause: // *Action: 33742, 00000, "(ILPPUT06) %a %j %d\nThe %1p program contains too many source lines. The limit is %2p lines. The program has been truncated." // *Cause: // *Action: 33744, 00000, "(ILPPUT07) IMPORTANT: Program %j contains text on the same line as a DO or DOEND statement, which will be ignored." // *Cause: // *Action: 33746, 00000, "(ILPPUT08) %v must be preceded by an IF clause." // *Cause: // *Action: 33748, 00000, "(ILPPUT09) %v must be preceded by a THEN clause." // *Cause: // *Action: 33750, 00000, "(ILPXEQ01) A referenced object can no longer be located. Execution will continue in interpreted mode." // *Cause: // *Action: 33756, 00000, "(ILTRK01) No data has been recorded by the TRACKPRG command." // *Cause: // *Action: 33758, 00000, "(IMPQUAF0) The EIF file %s does not have any objects in it." // *Cause: // *Action: 33760, 00000, "(IMPQUAF02) \nThere are %d objects in the EIF file:" 33762, 00000, "(XSCHGDIM01) Invalid LIMIT argument starting at %t." // *Cause: // *Action: 33766, 00000, "(INFOFC00) Invalid second argument to INFO(FORECAST %t)." // *Cause: // *Action: 33768, 00000, "(INFOMOD00) Invalid second argument to INFO(MODEL %t)." // *Cause: // *Action: 33770, 00000, "(INFOPARS01) Invalid second argument to INFO(PARSE %t)." // *Cause: // *Action: 33772, 00000, "(INFORG00) Invalid second argument to INFO(REGRESS %t)." // *Cause: // *Action: 33774, 00000, "(INTERP1) %t is not a command." // *Cause: // *Action: 33776, 00000, "(INTERP1A) %q is not a command." // *Cause: // *Action: 33778, 00000, "(INTERP2) There is not enough main memory to parse the %t command. Try reducing the number of arguments." // *Cause: // *Action: 33780, 00000, "(INTERP3) The %t command can only be used in a program." // *Cause: // *Action: 33782, 00000, "(INTERP4) The %t command cannot be executed by ampersand substitution." // *Cause: // *Action: 33784, 00000, "(INTERP5) Ampersand substitution is not permitted in a %t statement." // *Cause: // *Action: 33786, 00000, "(INTERP7) An internal array overflow occurred during the parsing of the %t command. Try reducing the number of arguments." // *Cause: // *Action: 33788, 00000, "(INTTOK01) %t is not composed solely of digits." // *Cause: // *Action: 33790, 00000, "(IOERROR01) %a %s %s\nI/O error on file %1p: %2p." // *Cause: // *Action: 33792, 00000, "(IOERROR02) I/O error on file %s: Error text not available." // *Cause: // *Action: 33796, 00000, "(IOEXECUT00) The file identifier argument of %s does not have a value." // *Cause: // *Action: 33798, 00000, "(IOEXECUT01) File %s is the current OUTFILE or LOG unit, and cannot be closed with the FILECLOSE command." // *Cause: // *Action: 33800, 00000, "(IOEXECUT02A) The LENGTH argument to the FILEGET function (%d) is negative." // *Cause: // *Action: 33802, 00000, "(IOEXECUT02B) File %s was opened for writing." // *Cause: // *Action: 33804, 00000, "(IOEXECUT02C) File %s was opened for binary input. You must use FILEREAD or FILENEXT to read data from this file." // *Cause: // *Action: 33806, 00000, "(IOEXECUT03A) %a %s %s\nThe %1p option of FILEQUERY is not supported in this version of %2p." // *Cause: // *Action: 33808, 00000, "(IOEXECUT03B) You have requested a FILEQUERY option that is not supported in this version of %s." // *Cause: // *Action: 33810, 00000, "(IOEXECUT04A) %a %s %s\nThe %1p option of FILESET is not supported in this version of %2p." // *Cause: // *Action: 33812, 00000, "(IOEXECUT04B) The %s option of a file cannot be changed by the FILESET command." // *Cause: // *Action: 33814, 00000, "(IOEXECUT04C) The value to be set for the %s option cannot be NA." // *Cause: // *Action: 33816, 00000, "(IOEXECUT04D) You have requested a FILESET option that is not supported in this version of %s." // *Cause: // *Action: 33818, 00000, "(IOEXECUT05) %a %d %s\nFile unit %1p is invalid. %2p can access only input files opened via the FILEOPEN function." // *Cause: // *Action: 33820, 00000, "(IOEXECUT06) The file name argument to %s cannot be null or blank." // *Cause: // *Action: 33822, 00000, "(IRR01) %a %j %d %d\nTime dimension %1p has a range in status of %2p periods. The maximum range allowed by the IRR function is %3p periods." // *Cause: // *Action: 33824, 00000, "(ISDBUILD01) A local scalar named %t already exists." // *Cause: // *Action: 33826, 00000, "(LINEDEL01) The number of the first line to remove must be between 1 and the expression's total number of lines. %d is out of range." // *Cause: // *Action: 33828, 00000, "(LINEDEL02) You must remove at least one line. You cannot remove %d lines." // *Cause: // *Action: 33830, 00000, "(LINEINS01) The line number after which inserting begins (%d) is negative." // *Cause: // *Action: 33832, 00000, "(LINEREP01) The number of the first line to replace must be between 1 and the expression's total number of lines. %d is out of range." // *Cause: // *Action: 33834, 00000, "(LINEXTR01) The line number of the first line to extract must be greater than 0. You cannot start extracting at line %d." // *Cause: // *Action: 33836, 00000, "(LINEXTR02) You must extract at least one line. You cannot extract %d lines." // *Cause: // *Action: 33838, 00000, "(LLPINIT05) You attempted to loop over the time dimension %j beyond the allowable range of dates." // *Cause: // *Action: 33840, 00000, "(LOOPCODE01) %a %j %j %j\nMultiple relations exist between %1p and the dimensions of the expression to be aggregated. One is %2p, and another is %3p." // *Cause: // *Action: 33842, 00000, "(LOOPCODE02) %j cannot be used for aggregation. It is unrelated to the data's dimensions, or it is less aggregate than one of them." // *Cause: // *Action: 33844, 00000, "(LOOPCODE03) %a %j %j\nTime dimensions %1p and %2p are both dimensions of the data. Breaking out the aggregation by time is ambiguous." // *Cause: // *Action: 33846, 00000, "(LXNXTREC00) The input line was terminated by an end-of-file that occurred sooner than expected. The line might be incomplete." // *Cause: // *Action: 33848, 00000, "(LXNXTREC01) The input line was truncated to the maximum allowable size of %d characters." // *Cause: // *Action: 33852, 00000, "(LXPARSE01) You provided extra input starting at '%t'." // *Cause: // *Action: 33854, 00000, "(LXTOKEN01) The statement cannot be parsed because it is too long or too complex." // *Cause: // *Action: 33856, 00000, "(LXSUBST01) %t is not a valid ampersand-substitution expression." // *Cause: // *Action: 33858, 00000, "(LXSUBST02) The value of the ampersand-substitution expression is NA." // *Cause: // *Action: 33860, 00000, "(MAKEDCL01) You have no current analytic workspace. You must attach or create an analytic workspace before defining a new object." // *Cause: // *Action: 33862, 00000, "(MAKEDCL02) You must specify a data type when you define a %s." // *Cause: // *Action: 33864, 00000, "(MAKEDCL03) You cannot use the data type attribute when you define a %s." // *Cause: // *Action: 33866, 00000, "(MAKEDCL04) Your current analytic workspace does not contain an object named %j." // *Cause: // *Action: 33868, 00000, "(MAKEDCL05) You must specify two or more dimensions when you supply a dimension list for a WORKSHEET." // *Cause: // *Action: 33870, 00000, "(MAKEDCL06) %a %s %s\nYou cannot use the %1p attribute when you define a %2p." // *Cause: // *Action: 33872, 00000, "(MAKEDCL07) The %s DIMENSION must have a data type (ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER), a time period, or a list of bases for a conjoint dimension." // *Cause: // *Action: 33874, 00000, "(MAKEDCL08) %s is not the name of a valid option." // *Cause: // *Action: 33876, 00000, "(MAKEDCL09) %s must be an INTEGER dimension." // *Cause: // *Action: 33878, 00000, "(MAKEDCL10) Nested composites are not supported when compatability is 11 or greater." // *Cause: // *Action: 33880, 00000, "(MAKEDCL11) Dimensions specified for a WORKSHEET must be INTEGER dimensions." // *Cause: // *Action: 33882, 00000, "(MAKEDCL12) %a %s %s %s\nYou cannot use the %1p attribute when you define a %2p of type %3p." // *Cause: // *Action: 33883, 00000, "(MAKEDCL36) You cannot use the %t attribute when you define an EXTERNAL partition with an existing target." // *Cause: User gave the TEMPORARY keyword in the definition of an external // partition whose target variable was previously defined. // *Action: Any storage characteristics of the external partition are // determined by the target variable. These attributes should be // set when the target is defined, not when the external partition // is defined. 33884, 00000, "(MAKEDCL13) You can specify the TEMPORARY attribute only for a variable, dimension, relation, valueset, or worksheet." // *Cause: // *Action: 33886, 00000, "(MAKEDCL14) You cannot define an object dimensioned by NAME, because it is a special reserved dimension used to organize your analytic workspace dictionary." // *Cause: // *Action: 33888, 00000, "(MAKEDCL15) %a %s %s\nYou cannot use the %1p attribute when you define a fixed-width TEXT %2p." // *Cause: // *Action: 33890, 00000, "(MAKEDCL16) You cannot use the dimension list attribute when you define a %s." // *Cause: // *Action: 33892, 00000, "(MAKEDCL17) %a %s %s\nYou cannot use the %1p attribute when you define a scalar %2p." // *Cause: // *Action: 33893, 00000, "(MAKEDCL18) The TEMPORARY attribute cannot be specified for this type of dimension" // *Cause: // *Action: 33894, 00000, "(MAKEDCL20) The WIDTH attribute can only be used with non-scalar TEXT and INTEGER variables, or with TEXT dimensions." // *Cause: // *Action: 33895, 00000, "(MAKEDCL19) You can specify the SHAREMAP attribute only for a multiply dimensioned variable, relation, valueset, or worksheet." // *Cause: // *Action: 33896, 00000, "(MAKEDCL21) The WIDTH attribute for TEXT data must be a number between 1 and 4000." // *Cause: // *Action: 33898, 00000, "(MAKEDCL22) The WIDTH attribute for INTEGER data must be 1." // *Cause: // *Action: 33900, 00000, "(MAKEDCL23) The NOHASH attribute is only valid for conjoint dimensions." // *Cause: // *Action: 33902, 00000, "(MAKEDCL24) The %s attribute is only valid for conjoint dimensions and dimension composites." // *Cause: // *Action: 33904, 00000, "(MAKEDCL25) %a %j %s\n%1p is a dimension composite or is dimensioned by a dimension composite. You cannot use it as the type of a %2p." // *Cause: // *Action: 33908, 00000, "(MAKEDCL27) You cannot use the %s attribute when you define a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE." // *Cause: // *Action: 33910, 00000, "(MAKEDCL28) You cannot specify a data type when you define a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE." // *Cause: // *Action: 33911, 00000, "(MAKEDCL29) %a %s %s %s\nYou cannot define a %1p in analytic workspace %2p because it has not been upgraded to version %3p." // *Cause: User attempted to define an object that requires a certain // compatibility setting in an AW that has not been upgraded to that // compatibility level. // *Action: Make sure that the database is running in the appropriate // compatibility mode, and upgrade the AW. 33912, 00000, "(MAKEDCL30) An AGGMAP cannot be dimensioned by a conjoint dimension." // *Cause: // *Action: 33914, 00000, "(MAKEDCL31) You cannot define a dimension alias of another dimension alias." // *Cause: // *Action: 33916, 00000, "(MAKEDCL32) The dimension alias target %j is not a simple dimension." // *Cause: // *Action: 33918, 00000, "(MAKEDCL33) %a %j %s\nYou cannot define a surrogate of dimension %1p because it is a %2p." // *Cause: Not all kinds of dimensions can have surrogates. The user // attempted to define a surrogate of a prohibited kind of dimension. // *Action: Do not attempt to define a surrogate on this dimension. 33920, 00000, "(MAKEDCL34) The %s SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER." // *Cause: The user attempted to define a surrogate without specifying a valid // data type. // *Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the // definition of the surrogate. 33922, 00000, "(MAKEDCL35) You cannot define a surrogate of dimension %j because it is a time dimension." // *Cause: The user attempted to define a surrogate on a dimension that has type // DAY, WEEK, MONTH, or YEAR. // *Action: Do not attempt to define a surrogate on this dimension. 33934, 00000, "(MISCOPTI01) OFF" // *Cause: // *Action: 33936, 00000, "(MISCOPTI04) NA" // *Cause: // *Action: 33938, 00000, "(MISCOPTI05) Press to continue." // *Cause: // *Action: 33940, 00000, "(MISCOPTI06)
" // *Cause: // *Action: 33942, 00000, "(MODCALL01) Model %n cannot be run because another model is already active." // *Cause: // *Action: 33944, 00000, "(MODCALL02) Model %n needs a solution variable; one was not provided." // *Cause: // *Action: 33946, 00000, "(MODCALL03) Model %n does not take a solution variable, because it has no model dimensions." // *Cause: // *Action: 33948, 00000, "(MODCALL04) %a %n %n\nA solution variable must be provided for model %1p; however, %2p is not a variable." // *Cause: // *Action: 33950, 00000, "(MODCALL05) %a %n %n %s\nThe solution variable specified for the model %1p must be numeric. Variable %2p is type %3p." // *Cause: // *Action: 33952, 00000, "(MODCALL08) %a %n %n\nA solution variable must be specified for model %1p; however, %2p has no dimensions." // *Cause: // *Action: 33954, 00000, "(MODCALL09) %a %n %j %n\nSolution variable %1p is not dimensioned by %2p, which is a dimension of model %3p." // *Cause: // *Action: 33956, 00000, "(MODCALL10) %a %j %d\nThe execution of model %1p cannot be completed due to an internal error (TYPE = %2p)." // *Cause: // *Action: 33958, 00000, "(MODCALL11) The syntax for invoking a model is:\n model-name [solution-variable] [NOWARN]" // *Cause: // *Action: 33960, 00000, "(MODCALL14) Model %n contains simultaneous equations." // *Cause: // *Action: 33962, 00000, "(MODCALL15) %a %j %d %d\nModel %1p failed to converge after %2p iterations in block %3p." // *Cause: // *Action: 33964, 00000, "(MODCALL16) %a %j %d %d %d %j\nModel %1p diverged during iteration %2p in block %3p while executing statement %4p of model %5p." // *Cause: // *Action: 33966, 00000, "(MODCALL17) %a %n %n\nThe solution variable %1p is referenced as a variable in model %2p." // *Cause: // *Action: 33968, 00000, "(MODCALL18) %a %n %j %n\nSolution variable %1p is dimensioned by %2p, which is not a dimension of model %3p but is a dimension of a model execution block." // *Cause: // *Action: 33970, 00000, "(MODCALL19) %a %n %j %n\nSolution variable %1p is not dimensioned by %2p, but model %3p contains dimension-based equations that reference its values." // *Cause: // *Action: 33972, 00000, "(MODCHECK01) %n is not a model." // *Cause: // *Action: 33973, 00000, "(MODCHECK02) The %n model cannot be compiled while it is executing." // *Cause: // *Action: 33974, 00000, "(MODCHECK12) The %n model cannot be compiled because it contains structural errors." // *Cause: // *Action: 33975, 00000, "(MODCHECK13) The %n model cannot be hidden or unhidden while it is executing." // *Cause: // *Action: 33976, 00000, "(MODCHECK22) The %n model cannot be executed because it contains structural errors." // *Cause: // *Action: 33978, 00000, "(MODCOMP01) %j has already been named in a DIMENSION statement in this model." // *Cause: // *Action: 33980, 00000, "(MODCOMP02) DIMENSION statements are not allowed after an equation has appeared." // *Cause: // *Action: 33982, 00000, "(MODCOMP03) DIMENSION statements are not allowed after an INCLUDE statement has appeared." // *Cause: // *Action: 33983, 00000, "(MODCOMP15) The DIMENSION statement must list the dimensions of any included models." // *Cause: // *Action: 33984, 00000, "(MODCOMP04) INCLUDE statements are not allowed after an equation has appeared." // *Cause: // *Action: 33986, 00000, "(MODCOMP05) Only one INCLUDE statement is allowed in a model." // *Cause: // *Action: 33988, 00000, "(MODCOMP06) An INCLUDE statement must refer to another model; %n is not a model." // *Cause: // *Action: 33990, 00000, "(MODCOMP08) Models cannot be included recursively; %j has already been included." // *Cause: // *Action: 33992, 00000, "(MODCOMP09) The format of the DIMENSION command is:\n DIMENSION dimension1 [dimension2...]" // *Cause: // *Action: 33994, 00000, "(MODCOMP10) The format of the INCLUDE command is:\n INCLUDE model" // *Cause: // *Action: 33996, 00000, "(MODCOMP11) %j is not named in a DIMENSION statement in this model." // *Cause: // *Action: 33998, 00000, "(MODCOMP12) %a %j %j %j %j\nYou cannot use both %1p and %2p as model dimensions, because %3p is a surrogate of %4p." // *Cause: The user attempted to include both a dimension and its surrogate in // the DIMENSION statement of a model. // *Action: Use either the dimension or the surrogate in the DIMENSION // statement of the model, but not both. 34000, 00000, "(MODCOMP13) %a %j %j %j\nYou cannot use both %1p and %2p as model dimensions, because they are both surrogates of dimension %3p." // *Cause: The user attempted to include two dimension surrogates of the same // dimension in the DIMENSION statement of a model. // *Action: Use either of the two surrogates in the DIMENSION statement of // the model, but not both. 34001, 00000, "(MODCOMP14) Concat leaf dimension %j already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension." // *Cause: Either two concat dimensions which share a common leaf dimension, // or a concat and one of its leaves where both specified in the DIMENSION statement(s). // *Action: Do not specify overlapping concat dimensions, or any leaves of specified concat dimensions. 34004, 00000, "(MODGRAPH01) %a %j %d\nThe model %1p cannot be compiled due to internal error %2p. Contact Oracle OLAP Technical support." // *Cause: // *Action: 34006, 00000, "(MODINFO00) There is no saved model information for the INFO function to retrieve." // *Cause: // *Action: 34008, 00000, "(MODINFO01) Model %j has not been compiled; the information requested is available only after compilation." // *Cause: // *Action: 34010, 00000, "(MODINFO02) Model %j has not been executed; the information requested is available only after execution." // *Cause: // *Action: 34012, 00000, "(MODPUT06) %a %j %d\nThe %1p model contains too many source lines. The limit is %2p lines. The model has been truncated." // *Cause: // *Action: 34014, 00000, "(MONITOR01) No data has been recorded by the MONITOR command." // *Cause: // *Action: 34016, 00000, "(MONITOR02) No program name has been supplied for the MONITOR command." // *Cause: // *Action: 34018, 00000, "(MSCGADD01) %j is an INTEGER dimension. Specify only the number of values to be added, not the specific values themselves." // *Cause: // *Action: 34019, 00000, "(MSCGADD03) %j is not a LIST PARTITION TEMPLATE." // *Cause: User attempted to MAINTAINT ADD or DELETE a list value from a // RANGE or CONCAT partition template. // *Action: Partitioning in a RANGE or CONCAT partition template cannot // be changed using the MAINTAIN command. 34020, 00000, "(MSCGADD02) %j is not a time dimension. You cannot add time periods to it." // *Cause: // *Action: 34021, 00000, "(MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE %j." // *Cause: User attempted to MAINTAINT ADD or DELETE a list value from a // LIST partition template, but didn't specify which partition // to add to or delete from. // *Action: Specify the partition: // maintain (template) add to partition (partitionname) (values) // or // maintain (template) delete from partition (partitionname) (values) 34022, 00000, "(MSCGDEL02) You can only delete time periods from a time dimension." // *Cause: // *Action: 34024, 00000, "(MSCGMRG01) The RELATE keyword cannot be specified when the MERGE expression has no dimensions." // *Cause: // *Action: 34026, 00000, "(MSCGMRG02) %a %q %j\n%1p is not a relationship between %2p and the dimensions of the source expression." // *Cause: // *Action: 34028, 00000, "(MSCGMRG03) %j, the value of the RELATE relation, is not one of the dimensions of the source expression." // *Cause: // *Action: 34030, 00000, "(MSCGPOS00) %j is a time dimension. You can add values to it only FIRST or LAST." // *Cause: // *Action: 34031, 00000, "(MSCGPOS02) %j is a datetime dimension. Dimension values are automatically maintained in sorted order." // *Cause: // *Action: 34032, 00000, "(MSCGPOS01) %j is a dimension composite. You cannot specify a position when adding values to it." // *Cause: // *Action: 34034, 00000, "(MSEXECUT00B) %a %k %j\n%1p is already a value of %2p." // *Cause: // *Action: 34036, 00000, "(MSEXECUT00C) %a %v %j\n%1p is already a value of %2p." // *Cause: // *Action: 34038, 00000, "(MSEXECUT01) The expression for the position to add, merge, or delete is NA." // *Cause: // *Action: 34039, 00000, "(TRGPRG02) %n cannot be deleted while its trigger is executing." // *Cause: // *Action: 34040, 00000, "(TRGSET01) The TRIGGERASSIGN command can only be used in an ASSIGN TRIGGER." // *Cause: // *Action: 34041, 00000, "(TRGPRG01) A TRIGGER cannot be called recursively for the same object and event." // *Cause: // *Action: 34042, 00000, "(MSEXECUT03A) The expression for the position to be renamed is NA." // *Cause: // *Action: 34044, 00000, "(MSEXECUT03B) The expression for the new dimension value is NA." // *Cause: // *Action: 34046, 00000, "(MSEXECUT03C) %a %k %j\n%1p is already a value of %2p." // *Cause: // *Action: 34048, 00000, "(MSEXECUT04) Time dimension %j is empty. You must give it a value before you can add periods to its beginning or end." // *Cause: // *Action: 34050, 00000, "(MSEXECUT05) The expression for the argument to BEFORE or AFTER is NA." // *Cause: // *Action: 34052, 00000, "(MSEXECUT06) All dimension values must be single line values." // *Cause: // *Action: 34054, 00000, "(MSEXECUT07) %a %v %j\n%1p is already a value of %2p." // *Cause: // *Action: 34056, 00000, "(MSEXECUT08) The number of periods to add cannot be negative, zero, or NA." // *Cause: // *Action: 34058, 00000, "(MSEXECUT09) The number of periods to delete cannot be negative, zero, or NA." // *Cause: // *Action: 34059, 00000, "(MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension %j." // *Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value. // *Action: Only use MAINTAIN DELETE to remove SESSION values from a concat dimension. 34060, 00000, "(MSEXECUT10) You do not have permission to maintain %j." // *Cause: // *Action: 34061, 00000, "(MSEXECUT11) Session-only values cannot be added to non-unique concat dimension %j, or any of its base dimensions." // *Cause: Only UNIQUE concat dimensions can have custom member values. // *Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry. 34062, 00000, "(MXARGS01) = Args:" // *Cause: // *Action: 34064, 00000, "(MXARGS02) (Relation)" // *Cause: // *Action: 34066, 00000, "(MXARGS03) values of" // *Cause: // *Action: 34068, 00000, "(MXBREAK01) The BREAK statement can only be used within a FOR or WHILE loop or within a SWITCH statement." // *Cause: // *Action: 34070, 00000, "(MXBREAK02) The CONTINUE statement can only be used within a FOR or WHILE loop." // *Cause: // *Action: 34072, 00000, "(MXCALL01) %q is not a PROGRAM." // *Cause: // *Action: 34074, 00000, "(MXCGAF01) %a %s %s\nThe %1p function cannot be used with %2p data." // *Cause: // *Action: 34076, 00000, "(MXCGAF02) %n is neither a dimension nor the name of a relationship array." // *Cause: // *Action: 34078, 00000, "(MXCGAF03) %a %j %s\nThe dimension %1p appears more than once as an argument to %2p." // *Cause: // *Action: 34082, 00000, "(MXCGAF05) Specify the STATUS keyword only if at least one of the breakout dimensions is not a dimension of the expression argument." // *Cause: // *Action: 34084, 00000, "(MXCGAF06) You cannot specify %j as a breakout dimension because it is a dimension composite." // *Cause: // *Action: 34086, 00000, "(MXCGAF07) You can only specify a qualified data reference to a breakout relation object. %n is not a relation." // *Cause: // *Action: 34088, 00000, "(MXCGCE04) The THEN and ELSE expressions must evaluate to values of the same dimension." // *Cause: // *Action: 34090, 00000, "(MXCGCHRL01) The expression argument to CHARLIST is not dimensioned by %j." // *Cause: // *Action: 34092, 00000, "(MXCGCON01) The use of a hexadecimal value (%t) is not supported." // *Cause: // *Action: 34094, 00000, "(MXCGCUM00) %a %n %j\nIn the CUMSUM function, the relation (%1p) must refer to the accumulation dimension (%2p)." // *Cause: // *Action: 34096, 00000, "(MXCGCUM01) The reset parameter '%n' is neither a RELATION nor a DIMENSION." // *Cause: // *Action: 34098, 00000, "(MXCGCUM02) The STATUS keyword has no effect unless the first argument has more than one dimension." // *Cause: // *Action: 34100, 00000, "(MXCGCVT01) Values of type %s are expected." // *Cause: // *Action: 34102, 00000, "(MXCGFIOF01) %a %t %s\nThe %1p option of FILEQUERY is not supported in this version of %2p." // *Cause: // *Action: 34104, 00000, "(MXCGGET01) %n is not a type of object that contains data values." // *Cause: // *Action: 34106, 00000, "(MXCGGET03) FILEREAD attributes can be specified only in the context of a FILEREAD or FILEVIEW command." // *Cause: // *Action: 34108, 00000, "(MXCGGET04) FILEREAD attributes cannot be specified for the NAME dimension." // *Cause: // *Action: 34110, 00000, "(MXCGGET05) FILEREAD attributes cannot be specified for a constant." // *Cause: // *Action: 34112, 00000, "(MXCGGT01) Values of type %s cannot be read with the MANY option." // *Cause: // *Action: 34114, 00000, "(MXCGGT02) The RAW attribute applies only to TEXT." // *Cause: // *Action: 34116, 00000, "(MXCGHCVT00) To convert TEXT to date use:\n CONVERT(expression DATE [dateorder])" // *Cause: // *Action: 34118, 00000, "(MXCGHCVT01) To convert date to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [dateformat])" // *Cause: // *Action: 34120, 00000, "(MXCGHCVT02) To convert time dimension periods to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [vnf-format])" // *Cause: // *Action: 34122, 00000, "(MXCGHCVT03) To convert NUMBER to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [output-format])" // *Cause: // *Action: 34124, 00000, "(MXCGHCVT04) %a %s %s %s\nTo convert %1p to %2p use:\n CONVERT(expression %3p [format])" // *Cause: // *Action: 34126, 00000, "(MXCGKEY01) The first argument to the KEY function must be an expression yielding a dimension value." // *Cause: // *Action: 34128, 00000, "(MXCGKEY02) You cannot apply the KEY function to %j because it is not a conjoint dimension or composite." // *Cause: // *Action: 34130, 00000, "(MXCGKEY03) %a %j %j\n%1p is not a component of conjoint dimension %2p." // *Cause: // *Action: 34132, 00000, "(MXCGKEY04) %a %j %j\n%1p is not a component of composite %2p." // *Cause: // *Action: 34134, 00000, "(MXCGLA01) You are trying to perform an invalid operation. Dates cannot be exponentiated." // *Cause: // *Action: 34136, 00000, "(MXCGMOVE00) %a %t %j\nThe first argument to the %1p function is not dimensioned by %2p." // *Cause: // *Action: 34138, 00000, "(MXCGNPV03) The interest rate expression in the NPV function cannot be dimensioned by %j." // *Cause: // *Action: 34140, 00000, "(MXCGPFC01) %a %d %n\nArgument number %1p in the call to %2p is not a simple expression." // *Cause: // *Action: 34141, 00000, "(MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION %j." // *Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD, // SQL FETCH or SQL SELECT command. // *Action: To create a new dimension value in a FILEREAD, SQL FETCH or // SQL SELECT command, use the APPEND keyword. 34142, 00000, "(MXCGPUT01) You cannot assign values to a %s." // *Cause: // *Action: 34143, 00000, "(MXCGPUT02) You cannot assign values to SURROGATE %n because it is type INTEGER." // *Cause: The user attempted to assign a value to a dimension surrogate whose // data type is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot // have values assigned to them. They can only be referenced by position. // *Action: Do not attempt to assign values to an INTEGER surrogate. Values // will automatically appear and disappear from the INTEGER surrogate as // positions are added to or removed from the underlying dimension. 34144, 00000, "(MXCGPUT04) A model cannot assign values to a %s." // *Cause: // *Action: 34145, 00000, "(MXCGPUT03) You cannot use the APPEND keyword with SURROGATE %n." // *Cause: User used the APPEND keyword on a SURROGATE target in a FILEREAD, // SQL FETCH or SQL SELECT command. // *Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or // SQL SELECT command, use the ASSIGN keyword. 34146, 00000, "(MXCGQDR01) A qualified data reference (QDR) has this format:\n name(dimension1 dimvalue1 [dimension2 dimvalue2...])" // *Cause: // *Action: 34148, 00000, "(MXCGQDR02) %j cannot be used as a qualifier because it is a COMPOSITE or PARTITION TEMPLATE. You can use its component dimensions instead." // *Cause: // *Action: 34150, 00000, "(MXCGQDR05) A dimension can be named only once in a qualified data reference. %j has been named more than once." // *Cause: // *Action: 34152, 00000, "(MXCGQDR06) %a %q %j\nThe dimensions named in a qualified data reference must be dimensions of the qualified object. %1p is not dimensioned by %2p." // *Cause: // *Action: 34154, 00000, "(MXCGQDR10) %q has no dimensions, so it cannot have a qualified data reference." // *Cause: // *Action: 34156, 00000, "(MXCGRA00) You cannot compare time periods of different lengths or phases." // *Cause: // *Action: 34158, 00000, "(MXCGRA01) You cannot subtract time periods of different lengths or phases." // *Cause: // *Action: 34160, 00000, "(MXCGRA02) The format of the IN operator is\n IN