/ / $Header: error.msg 09-apr-96.16:07:16 mdepledg Exp $ error.msg / / Copyright (c) 1987, 1996 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 / jcohen 05/07/96 - QKA Disable Bitmap And-EQuals / mdepledg 04/09/96 - add bitmap error for max number of columns / rherwadk 04/09/96 - add error message for max_dump_file_size parameter / hjakobss 02/08/96 - add misc events / jklein 01/12/96 - bitmap index dml / gswart 12/26/95 - New snapshot too old error message / nmacnaug 12/20/95 - correct parameter name / nmacnaug 12/12/95 - kcl parsing error / qtran 11/22/95 - recover modification history / jhyde 11/21/95 - add events 10711-10716 / qtran 10/30/95 - reserve trace events range for bitmap row sources / rherwadk 11/17/95 - add error messages for skgm / bhirano 11/17/95 - add init.ora parameter errors / rtaranto 10/26/95 - Update message 4062 / lwillis 11/14/95 - 10118 CBO enable hash costing / bhimatsi 10/16/95 - bug 313376, 1557 should take argument / rmirchan 10/15/95 - 12827 parallel min percent message / lwillis 11/09/95 - 10117 parallel cost model / lthieme 11/07/95 - add message text for simulated error ORA-07347 / wbridge 10/30/95 - flush buffer cache on redo corruption / wbridge 10/04/95 - do not automatically use a file name from the log / aho 10/11/95 - alter index allocate extent / jklein 10/20/95 - bitmap dml / hjakobss 10/27/95 - events 10107-10116 / achaudhr 10/19/95 - improve diction of some error msgs / slari 09/21/95 - b301008, add OER(24307) for osetpi / achaudhr 10/16/95 - UJV: new errors for updatable join views / arhee 10/17/95 - add event 10374 / lfeng 10/14/95 - Add Spatial Data Option messages / jcohen 10/10/95 - bitmap index checkin / jbellemo 10/05/95 - add event 10145 / rhari 10/02/95 - add event 10928 / pshah 09/25/95 - add error message #00124 for MTS / boki 09/13/95 - fix error messages 23430 - 23434 / pshah 09/12/95 - add error range for Advanced Queueing (25200-25699) / gngai 09/21/95 - Added cause and action to several msg / jtellez 09/21/95 - Add multi instance index create event 10709 / schandra 08/30/95 - modify error message for ORA-03296 / hbergh 09/18/95 - bug 274084: error when system rollback seg specifie / scorcora 09/12/95 - Bug #197210, OER(100) to 123, 100 for ansi not found / hasun 09/12/95 - Modify message #23375 / hasun 09/08/95 - Modify Cause and Action of 23309 / lthieme 08/23/95 - resolve standby database inspection issues / aborr 08/23/95 - bug 298769: stop kcvirv loop when kcvucp gets IO er / lwillis 09/01/95 - Add 10076 enable cp join costing / jbellemo 08/31/95 - merge changes from branch 1.564.720.43 / ksriniva 08/17/95 - add UNIX message 7444 for oradbx / dsdaniel 08/11/95 - reserve range 14000 to 14999 for PTI / ksriniva 08/04/95 - add errors for invalid heap dumps / hasun 08/03/95 - Modify replication error 23381 / schatter 08/03/95 - add event 10375 / mramache 08/01/95 - clarify error 4097 / bhimatsi 07/11/95 - merge changes from branch 1.564.720.42 / mramache 07/18/95 - modify meaning of error 4097 / hjakobss 07/26/95 - event 10106 / hjakobss 07/20/95 - event 10105 / lthieme 05/09/95 - fix #278985 do not allow || mnt with no lock mgr. / boki 07/13/95 - fix message for 23377 / boki 06/28/95 - modify for offline instantiation / 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 / jklein 03/22/95 - remove error 2474 / ajasuja 06/28/95 - change message 6575 / amozes 06/22/95 - add event for table queue statistics / usundara 05/31/95 - [merge changes from revision 1.564.720.44] / reserve event space 10925 through 10974 for PL/SQL / jbellemo 08/02/95 - fix up Cause phrasing / 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. / hasun 05/30/95 - Add error for invalid connection qualifier / svenkate 05/03/95 - events for direct read / hjakobss 05/11/95 - event 10103 / aho 05/12/95 - even more errors for recreate index / aho 05/02/95 - more errors for recreate index / thayes 05/02/95 - Add event to allow PERSISTENT DLM ops / rxgovind 05/05/95 - change error 6514 / lthieme 05/02/95 - fix #151892 check control file size on open / nmichael 05/04/95 - Event 10277 - New event for sharing cursors / boki 05/03/95 - bug 279979 -- add new error msg / dchatter 05/01/95 - reword message 3127 and add new message 3131 / slari 05/03/95 - change ORA-02391 / rxgovind 04/17/95 - add error 6514 / jwlee 04/17/95 - rewrite 1241 slightly / thayes 04/14/95 - Add releasable lock DLM error / gdoherty 04/10/95 - set transaction isolation level / hbergh 04/14/95 - add new cause/action to 1545 / dchatter 03/28/95 - new messages for piecewise / jwlee 04/10/95 - add external cache error 1241 / cozbutun 04/04/95 - add 6580 / lthieme 04/06/95 - fix consistant spelling errors / lthieme 04/06/95 - fix inconsistant spelling errors / wbridge 02/06/95 - standby database errors / nmichael 04/02/95 - merge changes from branch 1.564.720.39 / bhimatsi 03/27/95 - merge changes from branch 1.564.720.35 / jtellez 03/22/95 - 962 - New errors for skxf / hasun 03/20/95 - Fix checkin errors / aho 03/10/95 - fix ci - merge screwup / slari 03/16/95 - add thread safety changes / drady 03/10/95 - Oracle TRACE changes / atsukerm 02/16/95 - Sort Segment implementation / hjakobss 03/09/95 - event 10102 / rlim 03/08/95 - rewrite error 4043 / aho 12/01/94 - rci trace event 10610, 2095 / lchidamb 03/05/95 - add error code 24303 / hasun 01/25/95 - Modify and add errors for Rep3 - Object Groups / dchatter 03/06/95 - merge changes from branch 1.564.720.36 / mramache 02/22/95 - stored triggers / gngai 03/03/95 - Added errors esfor ALTER SYSTEM DUMP UNDO / jklein 02/27/95 - event for skip corrupted index / wbridge 03/01/95 - external cache / jcohen 02/16/95 - events 10804 and 10805 for ksxb and rso / 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 / 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 / boki 02/06/95 - add error codes for table comparison feature in 7.3 / jwlee 02/06/95 - error codes for resilvering testing OSDs / rhari 02/05/95 - merge changes from branch 1.564.720.32 / error messages for utl_pg / lthieme 02/02/95 - merge changes from branch 1.564.720.31 / jbellemo 05/12/95 - #221259: remove 1415 / add event 10069 / nmichael 03/04/95 - Bug 265643 - Error for binds in trigger when clause / rlim 02/28/95 - rewrite error 4043 / dchatter 02/13/95 - add new messages for upilog / lthieme 02/06/95 - issue 2495 error only for read-only tablespaces / 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 - 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 / 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 / ksriniva 12/14/94 - merge changes from branch 1.564.720.22 / lchidamb 12/14/94 - merge changes from branch 1.564.720.5 / msimon 12/13/94 - merge changes from branch 1.564.720.23 / 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 / msimon 12/12/94 - merge changes from branch 1.479.710.82 / msimon 12/12/94 - Fixes for bug 249693 - Add event 10320 / thayes 12/08/94 - Fix name of parameter in msg 406 / boki 12/01/94 - adding new error numbers for schema offline instant / jbellemo 11/30/94 - merge changes from branch 1.564.720.19 / jstamos 11/30/94 - add periods and capitalization: 23306 - 23320 / jstamos 11/30/94 - merge changes from branch 1.479.710.79 / hasun 11/29/94 - Change cause/action statements for (2094,23364) / jbellemo 11/23/94 - remove 1966 / ksriniva 11/23/94 - change 10090 to 10095 / hasun 11/22/94 - Add messages for Replication factoring (23364,2094) / jbellemo 11/22/94 - fix up 12495, again / jbellemo 11/14/94 - remove 1948 / jstamos 11/16/94 - add 23353 for repcat / thayes 11/14/94 - Change reference to compatible parameter / ksriniva 11/14/94 - add error codes for generic oradbx / dchatter 11/14/94 - merge changes from branch 1.564.720.14 / dchatter 11/14/94 - merge changes from branch 1.564.720.9 / rhari 11/13/94 - merge changes from branch 1.564.720.11 / rtaranto 11/10/94 - merge changes from branch 1.564.720.15 / boki 12/01/94 - adding new error numbers and msgs for schema offlin / dsdaniel 11/18/94 - execution of deferred RPC disabled / jstamos 11/16/94 - add 23353 for repcat / dsdaniel 11/17/94 - merge changes from branch 1.479.710.74 / jstamos 11/16/94 - merge changes from branch 1.479.710.75 / dsdaniel 11/15/94 - 23352 - deferred rpc error message / jstamos 11/11/94 - merge changes from branch 1.479.710.72 / rtaranto 11/10/94 - merge changes from branch 1.479.710.73 / rtaranto 11/10/94 - Update Cause and Action comments for event 04097 / jbellemo 11/02/94 - merge changes from branch 1.564.720.13 / rtaranto 11/02/94 - merge changes from branch 1.564.720.12 / dchatter 11/09/94 - merge changes from branch 1.479.710.70 / 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 / lchidamb 10/05/94 - changed error #3112 / 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) / rjenkins 10/04/94 - merge changes from branch 1.564.720.2 / dchatter 10/14/94 - change 3124 to an internal error and add 3128 / adowning 10/13/94 - merge changes from branch 1.479.710.65 / jstamos 10/13/94 - merge changes from branch 1.479.710.58 / dsdaniel 10/13/94 - add 1085 / lchidamb 10/12/94 - add 1084: invalid parameter to oci call. / dchatter 10/14/94 - messages of 3125, 3126, 3127 backported from 7.2 / hjakobss 10/05/94 - event 10076 / arhee 10/04/94 - add event 10377 / rjenkins 10/03/94 - merge changes from branch 1.479.710.60 / jbellemo 09/30/94 - fix up 12495 / 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 / msimon 09/27/94 - Sequence numbers rewrite (bug 239487) / rhari 09/27/94 - UTL_RAW & UTL_PG (8401 -- 8443) / 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 / atsukerm 08/31/94 - merge changes from branch 1.479.710.57 / ksriniva 08/31/94 - add WMON termination error message / atsukerm 08/18/94 - new space management events / abrumm 08/22/94 - Change 1854 due to max Julian date increase by CORE / 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 / 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/28/94 - 1085 preceding error in deferred rpc / 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 / ksriniva 07/08/94 - add trace event for kst / gpongrac 07/08/94 - merge changes from branch 1.479.710.50 / wbridge 07/08/94 - bug 150326: typo in error 66 / 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 / gpongrac 07/08/94 - parallel recovery factoring / 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 / cbarclay 06/29/94 - add 6504 - Result Sets type mismatch / wbridge 06/29/94 - #198847: report 1031 rather than 251 / 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 / jloaiza 06/16/94 - add compatibility for disable table lock / wbridge 06/16/94 - specify file number for forced checksum error / jloaiza 06/16/94 - add disable dml locks / 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 / wbridge 04/25/94 - checksum error events / ksriniva 05/16/94 - merge changes from branch 1.479.710.47 / wbridge 04/04/94 - allow end hot backup after crash / wbridge 01/20/94 - add ALTER DATABASE CLEAR LOGFILE command / ksudarsh 05/06/94 - relocate error msg / jtellez 04/06/94 - add io tracing event 10705 / 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 / abhide 04/07/94 - merge changes from branch 1.479.710.36 / (merge SQL*NET error codes) / dsdaniel 04/07/94 - merge changes from branch 1.479.710.34 / ltung 04/05/94 - merge changes from branch 1.479.710.41 / ajasuja 04/04/94 - merge changes from branch 1.479.710.32 / rlim 04/07/94 - merge changes from branch 1.479.710.44 / thayes 03/22/94 - merge changes from branch 1.479.710.38 / wmaimone 03/31/94 - cause/action for 1010 / rlim 03/21/94 - #206483 - reuse 1037 for maximum cursor memory / exceeded / dpawson 03/21/94 - merge changes from branch 1.479.710.42 / ltung 03/21/94 - add 12800, 12826 for parallel query execution / pgreenwa 03/14/94 - merge changes from branch 1.479.710.39 / dpawson 03/10/94 - Merge in nCube error msgs / Merge in correct Unix messages instead of obsolete / Unix trusted messages / ltung 03/10/94 - events 10378, 10379 / hrizvi 03/08/94 - add smon events 10510, 10511 / pgreenwa 03/08/94 - add trace event for ksq / dpawson 03/04/94 - merge changes from branch 1.479.710.29 / thayes 03/03/94 - Error for simulating block recovery / dpawson 03/02/94 - Reserve numbers for resizable data files / ltung 03/02/94 - merge changes from branch 1.479.710.37 / 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 / dsdaniel 02/02/94 - kkxp.c code change / ksriniva 01/27/94 - merge changes from branch 1.479.710.33 / ksriniva 01/27/94 - sigh... really fix ORA-30 message for bquigley / 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 / dsdaniel 01/20/94 - reassign dbms_sys_error range / jbellemo 01/20/94 - merge changes from branch 1.479.710.26 / ksriniva 01/19/94 - fix Cause part of ORA-30 / dpawson 01/19/94 - reserve osd message range / dpawson 01/19/94 - reserve osd message range / rjenkins 01/19/94 - merge changes from branch 1.479.710.19 / 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 / dleary 01/03/94 - make event 10383 level a bitfield / hrizvi 01/03/94 - bug 189557 - fix explanation of 1599 / gpongrac 12/30/93 - change comments for 12812 and 12813 / dsdaniel 12/27/93 - obsolete ICD error / dpawson 12/21/93 - merge changes from branch 1.479.710.7 / jbellemo 12/21/93 - merge changes from branch 1.479.710.18 / jbellemo 12/21/93 - merge changes from branch 1.479.710.14 / sjain 12/21/93 - merge changes from branch 1.479.710.17 / hjakobss 12/21/93 - trace event 10060 / 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 / pritto 11/04/93 - merge in SQL*Net 2.1.2 error messages / hkodaval 11/05/93 - merge changes from branch 1.479.710.4 / pritto 11/02/93 - add 122 / ksriniva 11/02/93 - merge changes from branch 1.417.312.18 / ltung 11/02/93 - fix parallel query messages / dsdaniel 10/30/93 - dbms_sys_error error range / 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 - add 10605 - debug trace kkri / 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/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 / ksudarsh 08/10/93 - parallel query option / aho 08/05/93 - add create index fastpath event / pritto 08/23/93 - re-insert Trusted Oracle messages / cozbutun 08/09/93 - add 6575 / 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 / agupta 06/29/93 - add event to prevent forward coalesce / glumpkin 07/07/93 - change 2256 / mmoore 07/07/93 - #(141926) trigger description too long / 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 / sjain 06/21/93 - add new messages for streaming / ajasuja 06/10/93 - connect internal messages / jwijaya 06/14/93 - add error / achaudhr 06/10/93 - errors for updatable joins / cozbutun 05/28/93 - add errors for pls_in_sql purity stuff / hjakobss 05/27/93 - fix line feed error in 6562 / hjakobss 05/27/93 - name changes in 6562, add 6566, 6567 / ajasuja 05/26/93 - merge changes from branch 1.417.312.16 / aho 05/18/93 - add event 10604 - trace parallel index creation / glumpkin 05/10/93 - Merge change for ora-2243 / gpongrac 05/06/93 - add block rcovery debugging event / thayes 05/06/93 - Fix 2249 error message and cause/action / 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 / pritto 04/12/93 - merge changes from branch 1.417.312.12 / pritto 03/17/93 - #(153641) remove 110 & add 960, 962 for rlim / tsaulys 04/12/93 - merge, change 7544 for #140423 to 7721 / dpawson 06/11/93 - Changed message 445 to take seconds as an argument / ajasuja 05/14/93 - expand message 12434 / 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 / rlim 04/06/93 - add msg 960 & 962 / hkodaval 04/07/93 - Bug 26632: give obj and tablespace names for error / add 1650, 1651, 1652, 1653, 1654 and remove 1547 / ltung 04/07/93 - add 10387-89, 12815 (cache partitions > 1) / 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) / wbridge 03/24/93 - read-only tablespaces / hkodaval 03/29/93 - Bug 123364: remove recursion and hence error 1596 / dsdaniel 03/24/93 - commitscn function for repliation / dpawson 03/15/93 - #(140423) Add msg 7544 - not enough OSD resource / ltung 03/15/93 - merge from dve$fox (parallel query msgs) / 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 / jbellemo 02/02/93 - merge changes from branch 1.417.312.5 / pritto 02/08/93 - #(149456) add 119, mts_listener_address syntax error / dleary 02/08/93 - merge changes from branch 1.286.12.1 / achaudhr 01/21/93 - add event 10058 / jwijaya 01/18/93 - merge changes from branch 1.417.312.3 / pritto 01/16/93 - merge changes from branch 1.417.312.1 / jklein 01/13/93 - merge changes from branch 1.417.312.2 / 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 / jwijaya 02/17/93 - renumber 4069 / jwijaya 02/17/93 - renumber 4069 and fix 4068 / jbellemo 01/22/93 - (#147335): add message 12444 / rkooi 01/20/93 - add 4069 / jwijaya 01/14/93 - bug 145876, add 4046 / jklein 01/13/93 - bug 146226 - add event to disable histograms / pritto 01/11/93 - #(144049) remove 481, 482 / glumpkin 12/16/92 - #(141079) add sqlnet error messages / wbridge 12/08/92 - snapshot refresh all error / agupta 12/11/92 - add 10292 - debug drop tablespace / mmoore 12/11/92 - disable set_role in stored procs / pritto 11/30/92 - merge in SQL*Net 2.0.12 errors / wbridge 12/03/92 - fix error handling for refresh all / ltan 12/03/92 - modify 1545 cause and action / epeeler 11/30/92 - modify enable constraint message / wbridge 11/30/92 - background process to refresh snapshots / sjain 11/25/92 - Add 1044 / rkooi 11/25/92 - fix 6563 error message / ajasuja 11/25/92 - new error 12354 / jloaiza 11/25/92 - fix error 57 / jcleland 11/24/92 - fix error 12354 / jcleland 11/24/92 - -madd error 12354 / rkooi 11/24/92 - A couple of changes for Brian / jloaiza 11/19/92 - second parameter to 4031 / 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 / maporter 11/18/92 - #139480 - remove 10700 event / bquigley 11/19/92 - msgs starting with %s changed / ajasuja 11/19/92 - error 12445 for analyze table / bquigley 11/18/92 - Trusted messages / bquigley 11/17/92 - ora-603 / ghallmar 11/12/92 - add events for 2PC tracing / jwijaya 11/14/92 - comment on event 10205 / rkooi 11/13/92 - add 655x for psdres / bquigley 11/13/92 - update ORA-2436 / ajasuja 11/11/92 - merge forward from 7.0.11 / thayes 11/10/92 - Add parameter range checking errors / ajasuja 11/09/92 - add MLS error 12447 / 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 / rkooi 11/06/92 - add 6513 for pl/sql / wbridge 11/02/92 - #(135186) robust lock mode inquiry / bquigley 11/05/92 - fix up merge diffs / bquigley 11/02/92 - add 2028 / jwijaya 11/04/92 - add 6561, 6562 / gpongrac 11/03/92 - add event 10291 for testing tbsadf / jbellemo 11/02/92 - add 12461 / glumpkin 10/30/92 - Merge unix error messages / rlim 10/30/92 - add 1040 / maporter 10/29/92 - Add 7531 vms error message for ssfccf $display / pritto 10/29/92 - add event 10258 for shared server selection / jklein 10/12/92 - new analyze parse options / 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 - 1484, 1486 clearer / bquigley 10/25/92 - add 1413 / pritto 10/20/92 - #(130911) move 7575,7576 to 1987,1988 / #(135660) add 7606 / aho 10/23/92 - add event to test truncate index undo (10603) / rkooi 10/22/92 - reduce length (for LMS) of error 21000 / ccongdon 10/21/92 - Add errors 7515, 7519, 7537, 7542, 7527, and 7533 / for bug 117453. / tsaulys 10/21/92 - Add error message 7709 for bug 33056 / rlim 10/21/92 - add 1039 / 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 / maporter 10/13/92 - Fill in archival errors that were never entered / thayes 10/08/92 - Add error #1639 / mmoore 10/13/92 - #(131686) change messages 2074,4092,0034 / ghallmar 10/10/92 - add ora-476: RECO died / maporter 10/12/92 - #132670 - report archiving osd errors (add 290) / thayes 09/23/92 - Fix error messages for log members / glumpkin 10/08/92 - fix typo in 02436 / mmoore 10/01/92 - remove trigger restrictions, remove error 4086 / wmaimone 10/01/92 - duplicate 12449 / wmaimone 09/16/92 - add 12400,12401,12448,12449 / jwijaya 09/28/92 - 4055 is obsolete / verbrug 09/23/92 - Remove 12704 / rlim 09/21/92 - add 1413 and 1463 / rkooi 09/19/92 - change error 6559 to standards / pritto 09/18/92 - update message 110 / pritto 09/08/92 - #(127459) update message 114 / glumpkin 09/07/92 - Add new snapshot error message: 12010 / bquigley 09/04/92 - Alter any msg beginning %s so the %s appears later / achaudhr 09/14/92 - 126559: rewording 1719 / gpongrac 08/10/92 - change Cause: for error 1610 / mmoore 08/31/92 - #(122494) add column name to error 4086 / ghallmar 09/05/92 - reuse 2043: must end current transaction before ... / rkooi 09/08/92 - backout 1.334 changes - postpone until 7.0.12 / bquigley 09/04/92 - Alter any msg beginning %s so the %s appears later / pritto 08/26/92 - clarify and extend cause/action on OER(23) / rkooi 08/26/92 - add 6503 for pl/sql / jklein 08/20/92 - parallel data load / pritto 07/30/92 - add dispatcher error messages / jbellemo 08/17/92 - fix label translation errors: 12450-12460,7610-7620 / jwijaya 08/13/92 - add 4069 / jwijaya 08/05/92 - add a new error / wbridge 07/15/92 - add compatibility checking calls / bquigley 07/29/92 - Add Message Standards Documentation. / pritto 07/10/92 - #(105280),#(105279) add more sz errors / hrizvi 07/28/92 - fix extreneous / before 2078 / hrizvi 07/21/92 - add 2093 / wmaimone 07/24/92 - MLS tech writing review / bquigley 07/24/92 - Update ORA-00568 & 00057 / jwijaya 07/20/92 - remove database link owner from name / thayes 07/20/92 - Add pec error number for MLS / hrizvi 07/16/92 - add 19, 35, 1985 / jklein 07/16/92 - remove message 983 - obsolete / ltan 07/14/92 - add error 8176 / hrizvi 07/15/92 - add 1636, 1637 / gpongrac 07/15/92 - use error 373 for online log incompat problem / thayes 06/04/92 - Add errors for KCK module / 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 / hrizvi 06/05/92 - add 2091, 2092 / mmoore 06/10/92 - add error message for create or replace trigger / glumpkin 06/09/92 - Add event 10053 -- optimizer stats / epeeler 06/08/92 - modify error message 1451 / mmoore 06/08/92 - #(111777) add error for lacking create session priv / jbellemo 06/05/92 - rollout 12458: obsolete / 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 / rkooi 05/27/92 - remove extra '/' lines to ease finding error ranges / reserve 3300-3499 for Meiko. / delete history prior to 01/01/92. / thayes 05/29/92 - Add error for 0 file size / maporter 05/29/92 - Add 475, 1380-1389 / jcleland 05/29/92 - add message for 12336 / agupta 05/21/92 - 60972 - dtsdrv - don't drop if users temp or defaul / jklein 05/29/92 - add kdn event / wbridge 05/21/92 - reword 285 / dleary 08/06/92 - reserve events for parallel query / pritto 05/19/92 - #(109437) add error msg for long mts_service / ajasuja 05/12/92 - new message 12407 / jloaiza 05/12/92 - add discrete transaction error / smartin 05/05/92 - Fix kcl 160? error messages / hrizvi 04/22/92 - fix wording of 1593, bug no. 99222, add 1556 / jklein 04/29/92 - fix bug 106913 - make message 4014 TRANSLATABLE / mmoore 04/28/92 - #(9647) fix granting on a view to check dependents / wmaimone 04/24/92 - merge changes from branch 1.270.300.4 / wmaimone 04/06/92 - add 12458 / rkooi 04/26/92 - add arg for 6557 / rkooi 04/26/92 - add errors for dbms_pipe icds / cheigham 04/23/92 - add loader out-of-memory message / wbridge 03/13/92 - fix create controlfile / mmoore 04/16/92 - add message for disallowing features in mts / mmoore 04/13/92 - add error 4093 / 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 / 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 / ltan 02/17/92 - change ora-1597 for system rollback segment / wbridge 02/17/92 - add error 1221 / jloaiza 02/13/92 - add oltp transaction failed error / jwijaya 02/13/92 - doesn't -> does not / mroberts 02/12/92 - remove quotes from 4043, 4052, 4053, 406x / jwijaya 02/07/92 - add an error / wmaimone 02/07/92 - add MAC dictionary reference errors / 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 / ltan 01/29/92 - modify cause and action of ora-1594 / smcadams 01/29/92 - add 1219, 1220, 34 / rkooi 01/29/92 - improve error 1011 / rlim 01/24/92 - 6.2->7.0 merge / wbridge 01/13/92 - add event 10300 to avoid undo compatibility check / wbridge 01/10/92 - reword 1040 / maporter 12/21/91 - Add err 50 for bug 48037, 79392 / jklein 01/16/92 - fix error 2170 / 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 / 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 / maporter 01/12/92 - merge changes from branch 1.191.51.3 / maporter 12/23/91 - add message for osnsoi failure. / rlim 01/10/92 - reword 1 and include violated index name / wbridge 01/08/92 - reword 1171 / wmaimone 01/08/92 - add 12438, change syshi/low to dbhi/lo / 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 / / List of ORACLE errors / / This file is converted to header/message files using lmsgen.c. / / The first col is the ORACLE error number. / The second column is reserved and must (for now) be x00000 / The remainder of the line is the error text / / Adding an error for V6: / Check out this file, add the error, and check it back in. Error numbers / should always be ordered. The second column should always be x00000. / Pseudo-error debugging events: / Error codes 10000 .. 10999 are reserved for debug event codes that are / not really errors. / / 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 required. 00018, 00000, "maximum number of sessions exceeded" // *Cause: All session state objects are in use // *Action: Increase maximum sessions - init.ora parameter "sessions" 00019, 00000, "maximum number of session licenses exceeded" // *Cause: All licenses are in use // *Action: Increase number of session licenses 00020, 00000, "maximum number of processes (%s) exceeded" // *Cause: All process state objects are in use // *Action: Increase maximum processes - init.ora parameter "processes" 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 // doesn't have to privilege to access it. // *Action: Specify a valid session id that you have privilege to access, ie, // either you owns it or you have CHANGE_USER privilege. 00023, 00000, "session references process's private memory; cannot detach session" // *Cause: An attempt was made to detach the current session when it contains // references to the process's 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 (e.g., 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's 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 which has this // disabled (by 'alter session disable commit in procedure') // *Action: enable commits from PL/SQL in this session, or don't 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: 00050, 00000, "O/S error occurred while obtaining an enqueue. See o/s error." // *Cause: Could not obtain the operating system resources necessary // to cover an oracle enqueue. This is normally the result // of an o/s 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 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 init.ora parameter "enqueue_resources" 00053, 00000, "maximum number of enqueues exceeded" // *Cause: Ran out of enqueue state objects // *Action: Increase the number of enqueues - init.ora parameter "enqueues" 00054, 00000, "resource busy and acquire with NOWAIT specified" // *Cause: Resource interested is busy // *Action: Retry if necessary 00055, 00000, "maximum number of DML locks exceeded" // *Cause: Ran out of DML lock state objects // *Action: Increase the "dml_locks" init.ora 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 "temporary_table_locks" init.ora parameter and // warm start. 00058, 00000, "DB_BLOCK_SIZE must be %s to mount this database (not %s)" // *Cause: DB_BLOCK_SIZE init.ora parameter is wrong for the database // being mounted. It does not match the value used to create the // database. // *Action: fix the DB_BLOCK_SIZE parameter or mount a database that matches 00059, 00000, "maximum number of DB_FILES exceeded" // *Cause: DB_FILE init.ora parameter exceeded // *Action: Increase the DB_FILES parameter and warm start. 00060, 00000, "deadlock detected while waiting for resource" // *Cause: Transactions deadlock one another 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 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 zero, and reexecute // the statement. 00063, 00000, "maximum number of LOG_FILES exceeded" // *Cause: LOG_FILES init.ora parameter exceeded // *Action: Increase the LOG_FILES parameter and warm start. The parameter // needs to be as large as the highest number log that currently // exists rather than just the count of logs that exist. 00064, 00000, "object is too large to allocate on this O/S (%s,%s)" // *Cause: An init.ora 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 init.ora parameter. 00065, 00000, "initialization of FIXED_DATE failed" // *Cause: fixed_date string not in date format yyyy-mm-dd:hh24:mi:ss // *Action: ensure the init.ora parameter is in correct date format 00066, 00000, "LOG_FILES is %s but needs to be %s to be compatible" // *Cause: The maximum number of log files supported by this instance // is not the same as for the other instances. All instances must // be able to open all the files any instance can open. // *Action: Change the value of the LOG_FILES parameter to be compatible 00067, 00000, "invalid value %s for parameter %s, must be at least %s" // *Cause: The value for the initialization parameter is invalid. // *Action: Choose a value as indicated by the message. 00068, 00000, "invalid value %s for parameter %s, must be between %s and %s" // *Cause: The value for the initialization parameter is invalid. // *Action: Choose a value as indicated by the message. 00069, 00000, "cannot acquire lock -- table locks disabled for %s" // *Cause: A command was issued that tried to lock the table indicated in // the message. Examples of commands that can lock tables are: // LOCK TABLE, ALTER TABLE ... ADD (...), and so on. // *Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry // the command. / / 70 .. 95 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 which doesn't 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 which // 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 which doesn't 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. 00097, 00000, "Use of Oracle SQL feature not in SQL92 %s Level" // *Cause: Usage of Oracle's SQL extensions. // *Action: 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 multi-threaded server errors / 00101, 00000, "invalid specification for system parameter mts_dispatchers" // *Cause: The syntax for the "mts_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 "mts_dispatchers" doesn't have the // functionalities 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 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 requires // 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 "mts_max_servers" // as the system will automaticaly start // up new servers to break the deadlock until the number of // servers reaches the value specified in "mts_max_servers". 00105, 00000, "dispatching mechanism not configured for network protocol %s" // *Cause: trying to alter the dispatcher's configuration for a network // protocol not specified in init.ora file. // *Action: Need to include the network protocol in the system parameter // "mts_dispatchers" in init.ora and re-start the system. 00106, 00000, "cannot startup/shutdown database when connected to a dispatcher" // *Cause: An attempt was made to startup/shutdown database when connected to // a shared server via a dispatcher. // *Action: Re-connect as user INTERNAL without going through the dispatcher. // For most cases, this can be done by connect to INTERNAL without // specifying a network connect string. 00107, 00000, "failed to connect to ORACLE listener process" // *Cause: Most likely due to the fact that ORACLE listener hasn't been // started up. // *Action: start up ORACLE listener if it hasn't been started up. 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 doesn't support aynchronous operations. // *Action: contact your ORACLE representative. 00111, 00000, "maximum number of servers is only %s; adding %s servers" // *Cause: An attempt was made to start up more servers than the maximum // number specified by the system parameter "mts_max_servers". // *Action: Increase the value of "mts_max_servers" in init.ora as needed. 00112, 00000, "only created up to %s (maximum specified) dispatchers" // *Cause: An attempt was made to start up more dispatchers than the maximum // number specified by the system parameter "mts_max_dispatchers". // *Action: Increase the value of "mts_max_dispatchers" in init.ora as needed. 00113, 00000, "protocol name %s is too long" // *Cause: A protocol name specified in the "mts_dispatchers" system parameter // is too long. // *Action: Use a valid protocol name for the "mts_dispatchers" value. 00114, 00000, "missing value for system parameter mts_service" // *Cause: There is no value for the "mts_service" system parameter, nor for // the "db_name" parameter. // *Action: Add an "mts_service" or "db_name" definition to the init.ora file. // By default, "mts_service" is the value of "db_name" unless // "mts_service" 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, "mts_service name is too long" // *Cause: The service name specified in the "mts_service"s system parameter // is too long. // *Action: Use a shorter name for the "mts_service" value (<= 255 chars). 00117, 00000, "value out of range for system parameter mts_servers" // *Cause: The value of the "mts_servers" parameter is incorrect. // *Action: "mts_servers" must be >= 0 and <= "mts_max_servers". 00118, 00000, "value out of range for system parameter mts_dispatchers" // *Cause: The value of the "mts_dispatchers" parameter is incorrect. // *Action: The sum of all "mts_dispatchers" values must be >= 0 and // <= "mts_max_dispatchers". 00119, 00000, "invalid specification for system parameter mts_listener_address" // *Cause: The syntax for the "mts_listener_address" parameter is incorrect. // *Action: refer to the manual for correct syntax. 00120, 00000, "dispatching mechanism not enabled or installed" // *Cause: Either that the dispatching mechanism is not enabled or the // ORACLE executable image is not installed with the dispatching // mechanism. // *Action: refer to manual on how to enable the dispatching mechanism using // system parameters in the init.ora file. Failing that, consult // your ORACLE representative. 00121, 00000, "mts_servers specified without mts_dispatchers" // *Cause: A definition for "mts_servers" was specified in the init.ora file, // but no definition for "mts_dispatchers" was specified. Without a // value for "mts_dispatchers", shared servers will never be used. // *Action: Add a definition for "mts_dispatchers" in the init.ora file // (or take out the definition for "mts_servers", if MTS is not // being used). 00122, 00000, "cannot initialize network configuration" // *Cause: ORACLE could not initialize SQL*NET version 2. // *Action: Check the error stack for detailed information. 00123, 00000, "idle public server terminating" // *Cause: Too many idle servers waiting on the common queue. // *Action: This is used internally, no action required. 00124, 00000, "mts_dispatchers specified without mts_max_servers" // *Cause: A definition for "mts_dispatchers" was specified in the init.ora // file, but "mts_max_servers" was specified as zero // *Action: Specify "mts_max_servers" to be greater than zero / / 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. / / 200 .. 220 control file management errors / 00200, 00000, "cannot create control file '%s'" // *Cause: It was not possible to create the control file // *Action: Check obvious things like disk space, quotas, etc. 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: Reporting file name for details of another error // *Action: See associated error messages 00203, 00000, "using the wrong control files" // *Cause: The mount id in the control file is 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 control file '%s' (block %s, # blocks %s)" // *Cause: Disk read failure of control file // *Action: Check if disk is online, if it is not, bring it online and try // warm start again. If it is, then need to recover disk. 00205, 00000, "error in identifying control file '%s'" // *Cause: The system cannot find a control file of the specified name and // size // *Action: Check that ALL control files are online and the same files that / the system created at cold start time. 00206, 00000, "error in writing control file '%s' (block %s, # blocks %s)" // *Cause: Disk write failure for control file // *Action: Check if disk is online, if it is not, bring it online and try // warm start again. If it is, then need to recover disk. 00207, 00000, "control files are not for the same database" // *Cause: The database id in the control file is 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 not // not an old version. 00208, 00000, "number of control file names exceeds limit of %s" // *Cause: The system does not support this many copies of control files // *Action: Reduce the number of control files 00209, 00000, "block size %s exceeds limit of %s bytes" // *Cause: Specified block size is larger than maximum block size for this // machine // *Action: Reduce the block size 00210, 00000, "cannot open control file '%s'" // *Cause: Cannot open the control file // *Action: Check to make sure the control file is there and not locked by // some other program 00211, 00000, "control file '%s' does not match previous control files" // *Cause: The specified control file is from 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 is too small - need space for the // system overhead // *Action: Specify larger block size 00213, 00000, "cannot reuse control file '%s'; old file size %s, %s required" // *Cause: In order to reuse a control file, it has to be the same size as // the old one // *Action: Either do not specify reuse or specify the same size in create // database statement 00214, 00000, "control file '%s' version %s inconsistent with file '%s' version %s" // *Cause: Versions of control files and datafiles/logfiles mismatch // *Action: Use same version of control files and datafiles/logfiles 00215, 00000, "must be at least one control file" // *Cause: No control file is specified or control file specified does // not exist // *Action: Specify at least one valid control file 00216, 00000, "unable to determine physical block size for control file '%s'" // *Cause: An error occurred while determining the physical block size of this // control file. // *Action: Check the error stack for detailed information. 00217, 00000, "control file '%s' physical block size %s inconsistent with %s" // *Cause: The physical block size of the system is inconsistent // with the block size of the control file // *Action: The system will NOT come up with invalid control files, // either restore a good copy of the control file or / cold start. 00218, 00000, "control file '%s' was created with block size %s now is %s" // *Cause: The physical block size as stored in the control file header is // different than the physical block size returned by the O/S. This // usually indicates that the control file has been corrupted. // *Action: You need to restore a good copy of the control file. 00219, 00000, "required control file size %s larger than maximum %s" // *Cause: Create database has specified a combination of parameters that // results in the control file exceeding the internal maximum // size. // *Action: Create the database, using "maxdatafiles" or "maxlogfiles" // clauses in the create database statement. 00220, 00000, "control file '%s' not mounted by first instance" // *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: One or more of the control files could not be written. // *Action: See accompanying errors. 00222, 00000, "control file may not be queried using dispatcher" // *Cause: Attempted to use client process connected to dispatcher. This is // not allowed for queries to control file fixed tables due to the // memory requirements. // *Action: Connect directly to the instance then execute query. 00223, 00000, "conversion data file is invalid or incorrect version" // *Cause: A V6->V7 conversion data file contains invalid data or was // created with an old version of the conversion utility. // *Action: Use a correct conversion file or regenerate it with a newer // conversion utility. 00224, 00000, "the specified file is not a control file" // *Cause: The control file specified in the init.ora file is not // a control file. // *Action: Edit the init.ora file and specify the correct control file name. 00225, 00000, "expected size %s of controlfile '%s' differs from actual size %s" // *Cause: The expected size of the control file as stored in its header // is different than the actual operating system file size of the // control file - this usually indicates that the control file has // been corrupted. // *Action: You need to restore a good copy of the control file. / / 250 .. 299 archival & media recovery errors / 00250, 00000, "archiver not started" // *Cause: Automatic archiver must be running in order to stop it. // *Action: Command not needed 00251, 00000, "unused error" // *Cause: // *Action: 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. // Most likely the log has not been used since it was added to the // database. However it is possible that instance death during a // log switch left the log empty. The log does not need archiving. // *Action: Do not archive the log. 00253, 00000, "limit of %s exceeded by length %s of archive string '%s' " // *Cause: The archive string specified is too long. // *Action: Use a shorter string. 00254, 00000, "error in archive control string '%s'" // *Cause: The archive string does not refer to a valid destination. // *Action: check the archive string used to make sure it refers to a valid // and on-line device. 00255, 00000, "error archiving log %s of thread %s, sequence # %s" // *Cause: An error occurred during archival. // *Action: Check the error stack for more detailed information. If it is not // possible to archive the log because 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, "error occurred in translating archive text string '%s'" // *Cause: An error occurred translating the archive control string. // *Action: Check the error stack for more detailed information. 00257, 00000, "archiver error. Connect internal only, until freed." // *Cause: The archiver process recieved an error while trying to archive // a log. Unless the problem is resolved soon, the database will // stop executing transactions. // *Action: By far the most likely cause of the error is the archive // destination device is out of space. Check archiver trace file // for detail description of the problem. 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 file name. // *Action: Specify log by file name, by group number or by thread and // sequence number. 00259, 00000, "log %s of open thread %s is the current log, cannot archive" // *Cause: The current log of an open thread cannot be archived because it // may still be in use for redo generation. // *Action: Force a log switch in the instance that has the thread open. // If there are no open instances it will be necessary to open the // database so that crash recovery can close 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 may // have been reused for another sequence number, it may have been // dropped, the sequence number may be greater than the current // log sequence number, or the thread may not have any logs. // *Action: 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. Clearing, adding a // member, droping a member, renaming a member, and dropping the // log are operations which modify the log. // *Action: Wait for the other operation to complete. 00262, 00000, "current log %s of closed thread %s cannot switch" // *Cause: The log can not 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: A command to manually archive unarchived logs found no logs // for this thread needing archival. // *Action: None. 00264, 00000, "no recovery required" // *Cause: Media recovery attempted on files which do not need any recovery. // The files do not even need crash recovery. // *Action: Do media recovery on other files or not at all. 00265, 00000, "Instance recovery required, cannot set ARCHIVELOG mode" // *Cause: Database was shutdown with the abort option or crashed. Media // recovery can not be enabled because the online logs may not // be sufficient to recover the current datafiles. // *Action: Open the database and then shutdown normal or immediate. 00266, 00000, "name of archived log file needed" // *Cause: Media recovery requested the name of an archived log file but // no name was entered. // *Action: Mount the correct log file and enter its name. 00267, 00000, "name of archived log file not needed" // *Cause: Media recovery did not requested the name of an archived log file // but a name was entered. // *Action: Continue media recovery without entering a new log name. 00268, 00000, "Specified logfile does not exist '%s'" // *Cause: The given logfile does not exist. // *Action: Check spelling and capitalization and resubmit. 00269, 00000, "Specified logfile is part of thread %s not %s" // *Cause: The given logfile is not part of the given thread // *Action: Resubmit the command after correcting error. 00270, 00000, "error creating archive log" // *Cause: An error was encountered either in creating or opening // the destination file for archiving. // *Action: Make sure that the archive destination is valid, and that // sufficient space is available to write the archive. 00271, 00000, "there are no logs that need archiving" // *Cause: A command to manually archive unarchived logs found no logs // needing archival. // *Action: None. 00272, 00000, "error writing archive log" // *Cause: An I/O error occurred while writing to the archive log. // *Action: Make sure that the output device is still available, or // correct any device-specific errors. Also make sure that // sufficient space is available on the output device. 00273, 00000, "media recovery of direct load data that was not logged" // *Cause: Media recovery encountered a table that was loaded by the direct // loader without logging redo. Some or all of the blocks in the // table are now marked as logically corrupt. // *Action: The table must be dropped or truncated so that the corrupted blocks // may be reused. If a more recent backup of the file is available, // it might be recoverable without getting this error. 00274, 00000, "Illegal recovery option %s" // *Cause: // *Action: 00275, 00000, "media recovery has already been started" // *Cause: Attempt to start a second media recovery in the same session. // *Action: Complete or cancel the first media recovery session. 00276, 00000, "CHANGE keyword specified but no change number given" // *Cause: // *Action: 00277, 00000, "Illegal option to the UNTIL recovery flag %s" // *Cause: The only legal UNTIL options are "CANCEL", "CHANGE" and "TIME" // *Action: Resubmit command with proper option 00278, 00000, "Logfile '%s' no longer needed for this recovery" // *Cause: The specified log file is no longer needed for the current // recovery. // *Action: None required, although the archived logfile may be removed // from its current location to conserve disk space. Be aware that // the logfile may still be required for some unforseen need for // another recovery in the future. 00279, 00000, "Change %s generated at %s needed for thread %s" // *Cause: To proceed with recovery the requested log is required. // *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 is an informational message to aid in locating the specified // change number. // *Action: (see error #279) 00281, 00000, "media recovery may not be preformed using dispatcher" // *Cause: Attempted to use client process connected to dispatcher. This is // not allowed for media recovery due to the memory requirements. // *Action: Connect directly to the instance then do 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: Refer to other errors on the error stack for 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: Refer to other errors on the error stack for 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 quotes 00286, 00000, "No members available, or no member contains valid data" // *Cause: None of the members of a logfile 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 file names are being used, especially // if the log 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 // logs for the given thread. // *Action: Correct statement. Suggest simply archiving the "NEXT" log. 00288, 00000, "To continue recovery type ALTER DATABASE RECOVER CONTINUE" // *Cause: During media recovery, a new log is not required but it was // necessary to do a checkpoint and report errors. // *Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume 00289, 00000, "Suggestion : %s" // *Cause: If the kernel were to archive the file now under the current // log_archive_dest, then the log file name would look as suggested. // If the log_archive_dest parameter was the same back when the log // log was archived, then that it where it was archived to. // *Action: Consider using this file name for the next log to give recovery. 00290, 00000, "Operating system archival error occurred. See error below" // *Cause: While attempting to archive a log file, the kernel encountered // an unexpected operating system error. // *Action: Correct the operating system error (given in the message) // and retry the operation 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 to specify the degree // of parallelism. // *Action: Re-enter the command with a numeric argument following the // PARALLEL keyword. / 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 initialization // file (the init.ora file). 00293, 00000, "control file out of sync with redolog" // *Cause: The redolog 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 // CONTROL FILE clause. // / 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 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 log file failed // *Action: Check: 1) there is enough space on the device // 2) the name of the file is valid // 3) the device is online // 4) an IO error occurred // consult associated errors for further information. 00302, 00000, "limit of %s logs exceeded" // *Cause: Maximum number of log files exceeded (this is set at cold start) // *Action: Delete one or more logs before adding this one. /0303 reserved for v2 compatibility // *Cause: none // *Action: none 00304, 00000, "requested instance_number is busy" // *Cause: The instance specified by the instance_number parameter is busy. // *Action: Either specify another instance_number, // or shut down the running instance with this number // or 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 log file does not match the database id // in the control file. // *Action: Restore the correct log file 00306, 00000, "limit of %s instances in this database" // *Cause: Starting this instance would exceed the maximum number // of instances allowed for this database. Occurs only // with STARTUP shared and multiple instances. // *Action: You cannot start more than the lower of // a) port-specific limit to 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 instance_number paramater specified an instance number // that was out of range // *Action: Change the parameter. The mimimum instance_number is one, // and the maximum instance_number is the lower of the port-specific // maximum or the user-specified maximum when the database // was created. 00308, 00000, "cannot open archived log '%s'" // *Cause: The system cannot open the specified archived redo log. // *Action: Restore access the log (check name, device, etc.) and retry. 00309, 00000, "log belongs to wrong database" // *Cause: The system cannot apply the redo log because it // belongs to another database // *Action: Restore the correct redo log 00310, 00000, "archived log contains sequence %s; sequence %s required" // *Cause: The archived log is not the correct log. // *Action: Restore the correct log file. 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. // *Action: See associated error messages 00312, 00000, "online log %s thread %s: '%s'" // *Cause: Reporting file name for details of another error // *Action: See associated error messages 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, "logfile '%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 recreate. 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 file name 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 file name 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 controlfile recovery to // make the control file current. Be sure to follow all restrictions // on doing a backup controlfile recovery. 00339, 00000, "archived log does not contain any redo" // *Cause: The archived log is not the correct log. It is a copy of a logfile // 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 on-line log file does not // match the control file. // *Action: Restore correct file or reset logs. 00342, 00000, "archived log was created before last RESETLOGS" // *Cause: Recovery was given a log that was created before the last // ALTER DATABASE OPEN RESETLOGS command. There should be another // log created since then that contains the correct redo. // *Action: Supply the correct log file. 00343, 00000, "too many errors, log member closed" // *Cause: The maximum number of errors on this log member has been exceeded. // *Action: Correct the underlying problem by referring to the other error // messages found with this one. 00344, 00000, "unable to recreate online log '%s'" // *Cause: An I/O failure occurred when attempting to recreate an online as // part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE // CLEAR LOGFILE command. // *Action: Correct the file/device as indicated by accompanying errors. 00345, 00000, "redo log write error block %s count %s" // *Cause: An IO error has occurred while writing the log // *Action: Correct the cause of the error, and then restart the system. // If the log is lost, apply media/incomplete recovery. 00346, 00000, "log member marked as STALE" // *Cause: A log file member no longer is complete. // *Action: Correct the underlying problem by referring to the other error // messages found with this one. 00347, 00000, "log %s of thread %s, expected block size %s doesn't match %s" // *Cause: On header read the blocksize indicated in the control // file did not match the blocksize contained in the log file. // *Action: Restore correct file or reset logs. 00348, 00000, "single-process redo failure. Must abort instance" // *Cause: A failure occurred during a critical portion of the log code // during single process operation. This error does not occur // during normal multi-process operation. // *Action: Shutdown abort and warmstart the database. 00349, 00000, "failure obtaining block size for '%s'" // *Cause: The operating system was unable to determine the blocksize // for the given file name. // *Action: Consult the accompanying error message, and correct the // device or specify another file name. 00350, 00000, "log %s of thread %s needs to be archived" // *Cause: The command cannot be done because the log has not been archived, // and media recovery has been enabled. // *Action: Archive the log or disable media recovery. If the command supports // an UNARCHIVED option then it can be used. However this may result // in making backups unuseable, and forcing the drop of some offline // files. 00351, 00000, "recover-to time invalid" // *Cause: The time specified in a recover-until statement must // be after January 1st 1988. // *Action: Specify a time after January 1st 1988. 00352, 00000, "all logs for thread %s need to be archived - cannot enable" // *Cause: Attempting to enable a thread with all logs needing to be // archived, and media recovery has been enabled. There is no log // that can be made the new current log for the thread. // *Action: Archive a log for the thread or disable media recovery. 00353, 00000, "log corruption near block %s change %s time %s" // *Cause: Some type of redo log corruption has been discovered. This error // describes the location of the corruption. Accompanying errors // describe the type of corruption. // *Action: Do recovery with a good version of the log or do incomplete // recovery up to the indicated change or time. 00354, 00000, "corrupt redo log block header" // *Cause: The block header on the redo block indicated by the accompanying // error, is not reasonable. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. If this happens when archiving, // archiving of the problem log can be skipped by clearing the log // with the UNARCHIVED option. This must be followed by a backup of // every datafile to insure recoverability of the database. 00355, 00000, "change numbers out of order" // *Cause: A change number found in the redo log is lower than a previously // encountered change number. The log is corrupted in some way. The // corruption may be at the earlier change or at this one. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. 00356, 00000, "inconsistent lengths in change description" // *Cause: A change record in the redo log contains lengths that do not add // up to a consistent value. The log is corrupted in some way. // *Action: Do recovery with a good version of the log or do time based // recovery up to the indicated time. 00357, 00000, "too many members specified for log file, the maximum is %s" // *Cause: A 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 logfiles and reissue the command. 00360, 00000, "not a logfile member: %s" // *Cause: A file name 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, "can not 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 accompaning 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, "no free buffer handles available" // *Cause: Init.ora parameter db_handles is too small // *Action: Increase the parameter value - default should be sufficient 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, valid range [%s..%s]" // *Cause: invalid value for db_block_size parameter // *Action: adjust parameter and restart 00375, 00000, "unable to get default db_block_size" // *Cause: the system was unable to determine the default db_block_size // *Action: see accompanying system specific error. As a workaround, // specify the blocksize in the init.ora file. 00376, 00000, "file %s cannot be read at this time" // *Cause: attempting to read from a file that is not readable. Most likely // the file is offline. // *Action: Check the state of the file. Bring it online / / 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. / / 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, "Conversion data file not found: '%s'" // *Cause: The file used for converting the database from V6 to V7 could // not be found. // *Action: Verify that the conversion process has been started on this // database and that the data file name is accessable. 00405, 00000, "compatibility type \"%s\"" // *Cause: Reporting a type associated with another error. // *Action: See accompaning error 00406, 00000, "COMPATIBLE parameter needs to be %s or greater" // *Cause: The COMPATIBLE initialization parameter is not high // enough to allow the operation. Allowing the command would make // the database incompatible with the release specified by the // current COMPATIBLE parameter. // *Action: Shutdown and startup with a higher compatibility setting. 00407, 00000, "rolling upgrade from release %s.%s to %s.%s is not allowed" // *Cause: Another instance executing software at a different point release // already has the database mounted. // *Action: Shutdown all instances then startup with the new software. 00408, 00000, "parameter %s is set to TRUE" // *Cause: Reporting the parameter that resulted in the compatibility error. // *Action: Shutdown and startup with a higher compatibility setting. / / 436, 437: 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. / / 440-460 Detached process startup errors / 00443, 00000, "background process \"%s\" did not start" // *Cause: The specified process did not start. // *Action: Ensure that the executable image is in the correct place with // the correct protections, and that there is enough memory. 00444, 00000, "background process \"%s\" failed while starting" // *Cause: Usually due to a bad (or non-existent) background process image. // *Action: Get a good background process image. 00445, 00000, "background process \"%s\" did not start after %s seconds" // *Cause: The specified process did not start after the specified time. // *Action: Ensure that the background did not die and leave a trace file. 00446, 00000, "background process started when not expected" // *Cause: The background process specified started up AFTER the RDBMS was // already running. // *Action: If nobody at your site started the process, then this is an // internal error. 00447, 00000, "fatal error in background process" // *Cause: One of the background processes died unexpectedly. // *Action: Warm start the system. 00448, 00000, "normal completion of background process" // *Cause: One of the background processes completed normally (i.e. exited). // The background process thinks that somebody asked it to exit. // *Action: Warm start the system. 00449, 00000, "background process '%s' unexpectedly terminated with error %s" // *Cause: A foreground process needing service from a background // process has discovered the process died. // *Action: Consult the error code, and the trace file for the process. / / 470-480 Detached process death errors (signaled in foreground) / 00470, 00000, "LGWR process terminated with error" // *Cause: The log writer process died // *Action: Warm start instance 00471, 00000, "DBWR process terminated with error" // *Cause: The database writer process died // *Action: Warm start instance 00472, 00000, "PMON process terminated with error" // *Cause: The process cleanup process died // *Action: Warm start instance 00473, 00000, "ARCH process terminated with error" // *Cause: The archive process died // *Action: Warm start instance 00474, 00000, "SMON process terminated with error" // *Cause: The system cleanup process died // *Action: Warm start instance 00475, 00000, "TRWR process terminated with error" // *Cause: The system tracing process died // *Action: Warm start instance 00476, 00000, "RECO process terminated with error" // *Cause: The distributed transaction (two-phase commit) recovery process // died. // *Action: Warm start instance 00477, 00000, "SNP* process terminated with error" // *Cause: A snapshot refresh process died // *Action: Warm start instance 00480, 00000, "LCK* process terminated with error" // *Cause: A system lock 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. / / 00486-00569 / 00568, 00000, "Maximum number of interrupt handlers exceeded" // *Cause: User specified too many ^c handlers // *Action: Remove some old handlers. / / 00570-00599 SQL*Connect Opening & Reading Files / 00574, 00000, "osndnt: $CANCEL failure (break)" // *Cause: // *Action: 00575, 00000, "osndnt: $QIO failure (send out-of-band break)" // *Cause: // *Action: 00576, 00000, "in-band break protocol error" // *Cause: // *Action: 00577, 00000, "out-of-band break protocol error" // *Cause: // *Action: 00578, 00000, "reset protocol error" // *Cause: // *Action: 00579, 00000, "osndnt: server received malformed connection request" // *Cause: // *Action: 00580, 00000, "protocol versions do not match" // *Cause: // *Action: 00581, 00000, "osndnt: cannot allocate context area" // *Cause: // *Action: 00582, 00000, "osndnt: cannot deallocate context area" // *Cause: // *Action: 00583, 00000, "osndnt: $TRNLOG failure" // *Cause: // *Action: 00584, 00000, "cannot close connection" // *Cause: // *Action: 00585, 00000, "host name has incorrect form" // *Cause: // *Action: 00586, 00000, "osndnt: LIB$ASN_WTH_MBX failure" // *Cause: // *Action: 00587, 00000, "cannot connect to remote host" // *Cause: // *Action: 00588, 00000, "message from host was too short" // *Cause: // *Action: 00589, 00000, "message from host had incorrect data length" // *Cause: // *Action: 00590, 00000, "message from host had incorrect message type" // *Cause: // *Action: 00591, 00000, "incorrect number of bytes written" // *Cause: // *Action: 00592, 00000, "osndnt: $QIO failure (mailbox queue)" // *Cause: // *Action: 00593, 00000, "osndnt: $DASSGN failure (network device)" // *Cause: // *Action: 00594, 00000, "osndnt: $DASSGN failure (mailbox)" // *Cause: // *Action: 00595, 00000, "osndnt: $QIO failure (receive)" // *Cause: // *Action: 00596, 00000, "osndnt: $QIO failure (send)" // *Cause: // *Action: 00597, 00000, "osndnt: $QIO failure (mailbox requeue)" // *Cause: // *Action: 00598, 00000, "osndnt: $QIO failure (mailbox read)" // *Cause: // *Action: 00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" // *Cause: This is the generic internal error number for Oracle program // exceptions. This indicates that a process has encountered an // exceptional condition. // *Action: Report as a bug - the first argument is the internal error number 00601, 00000, "cleanup lock conflict" // *Cause: PMON process runs into lock conflict trying to recovery processes // *Action: This is trapped internally, no action necessary 00602, 00000, "internal programming exception" // *Cause: Internal programming exception // *Action: Report as bug / Caution: following error code not relocatable 00603, 00000, "ORACLE server session terminated by fatal error" // *Cause: An ORACLE server session is in an unrecoverable state. // *Action: Login to ORACLE again so a new server session will be created / automatically. Examine the session trace file for more / information. 00604, 00000, "error occurred at recursive SQL level %s" // *Cause: An error occurred while processing a recursive SQL statement // (a statement applying to internal dictionary tables). // *Action: If the situation described in the next error on the stack // can be corrected, do so; otherwise contact Oracle Support. / /0605 reserved for v2 compatibility / 00606, 00000, "Internal error code" // *Cause: A call to deferred upi functions was made in non deferred mode // *Action: Report as a bug. 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 and the // definition of which is also stored in the bootstrap segment in // the control file. // *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 accompaning error. // *Action: Contact your customer support representative. 00816, 00000, "error message translation failed" // *Cause: // *Action: / / 900-999 parse errors - / carried over from V5 - desirable to add arguments wherever possible / 00900, 00000, "invalid SQL statement" // *Cause: // *Action: 00901, 00000, "invalid CREATE command" // *Cause: // *Action: 00902, 00000, "invalid datatype" // *Cause: // *Action: 00903, 00000, "invalid table name" // *Cause: // *Action: 00904, 00000, "invalid column name" // *Cause: // *Action: 00905, 00000, "missing keyword" // *Cause: // *Action: 00906, 00000, "missing left parenthesis" // *Cause: // *Action: 00907, 00000, "missing right parenthesis" // *Cause: // *Action: 00908, 00000, "missing NULL keyword" // *Cause: // *Action: 00909, 00000, "invalid number of arguments" // *Cause: // *Action: 00910, 00000, "specified length too long for its datatype" // *Cause: for datatypes CHAR and RAW, the length specified was > 255; // otherwise, the length specified was > 2000. // *Action: use a shorter length or switch to a datatype permitting a // longer length such as a VARCHAR2, LONG CHAR, or LONG RAW 00911, 00000, "invalid character" // *Cause: // *Action: 00913, 00000, "too many values" // *Cause: // *Action: 00914, 00000, "missing ADD keyword" // *Cause: // *Action: 00915, 00000, "network access of dictionary table not currently allowed" // *Cause: // *Action: 00917, 00000, "missing comma" // *Cause: // *Action: 00918, 00000, "column ambiguously defined" // *Cause: // *Action: 00919, 00000, "invalid function" // *Cause: // *Action: 00920, 00000, "invalid relational operator" // *Cause: // *Action: 00921, 00000, "unexpected end of SQL command" // *Cause: // *Action: 00922, 00000, "missing or invalid option" // *Cause: // *Action: 00923, 00000, "FROM keyword not found where expected" // *Cause: // *Action: 00924, 00000, "missing BY keyword" // *Cause: // *Action: 00925, 00000, "missing INTO keyword" // *Cause: // *Action: 00926, 00000, "missing VALUES keyword" // *Cause: // *Action: 00927, 00000, "missing equal sign" // *Cause: // *Action: 00928, 00000, "missing SELECT keyword" // *Cause: // *Action: 00929, 00000, "missing period" // *Cause: // *Action: 00930, 00000, "missing asterisk" // *Cause: // *Action: 00931, 00000, "missing identifier" // *Cause: // *Action: 00932, 00000, "inconsistent datatypes" // *Cause: // *Action: 00933, 00000, "SQL command not properly ended" // *Cause: // *Action: 00934, 00000, "group function is not allowed here" // *Cause: // *Action: 00935, 00000, "group function is nested too deeply" // *Cause: // *Action: 00936, 00000, "missing expression" // *Cause: // *Action: 00937, 00000, "not a single-group group function" // *Cause: // *Action: 00938, 00000, "not enough arguments for function" // *Cause: // *Action: 00939, 00000, "too many arguments for function" // *Cause: // *Action: 00940, 00000, "invalid ALTER command" // *Cause: // *Action: 00941, 00000, "missing cluster name" // *Cause: // *Action: 00942, 00000, "table or view does not exist" // *Cause: // *Action: 00943, 00000, "cluster does not exist" // *Cause: // *Action: 00944, 00000, "insufficient number of clustered columns" // *Cause: // *Action: 00945, 00000, "specified clustered column does not exist" // *Cause: // *Action: 00946, 00000, "missing TO keyword" // *Cause: // *Action: 00947, 00000, "not enough values" // *Cause: // *Action: 00948, 00000, "ALTER CLUSTER statement no longer supported" // *Cause: // *Action: 00949, 00000, "illegal reference to remote database" // *Cause: // *Action: 00950, 00000, "invalid DROP option" // *Cause: // *Action: 00951, 00000, "cluster not empty" // *Cause: // *Action: 00952, 00000, "missing GROUP keyword" // *Cause: // *Action: 00953, 00000, "invalid index name" // *Cause: An index name of the form [ . ] is // expected but not present. // *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. 00962, 00000, "too many group-by / order-by expressions" // *Cause: The group-by or order-by column list contain more than 255 // expressions. // *Action: Use 255 or less expressions in the group-by or order-by list. 00964, 00000, "table name not in FROM list" // *Cause: The table name referred in the select list is not specified in the // from list. // *Action: Make sure the name is correctly specified and matches one of the // names in the from list. 00965, 00000, "column aliases not allowed for '*'" // *Cause: The statement is trying to alias the * expression in the select // list which is not legal. // *Action: Remove the alias. 00966, 00000, "missing TABLE keyword" // *Cause: // *Action: 00967, 00000, "missing WHERE keyword" // *Cause: // *Action: 00968, 00000, "missing INDEX keyword" // *Cause: // *Action: 00969, 00000, "missing ON keyword" // *Cause: // *Action: 00970, 00000, "missing WITH keyword" // *Cause: // *Action: 00971, 00000, "missing SET keyword" // *Cause: // *Action: 00972, 00000, "identifier is too long" // *Cause: An identifier with more than 30 characters was specified. // *Action: Specify at most 30 characters. 00973, 00000, "invalid row count estimate" // *Cause: // *Action: 00974, 00000, "invalid PCTFREE value (percentage)" // *Cause: // *Action: 00975, 00000, "date + date not allowed" // *Cause: // *Action: 00976, 00000, "LEVEL, PRIOR, or ROWNUM not allowed here" // *Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location. // *Action: Remove LEVEL, PRIOR, or ROWNUM. 00977, 00000, "duplicate auditing option" // *Cause: AUDIT or NOAUDIT statement specifies an option more than once // *Action: Either use ALL with no other auditing options or make sure // no option is listed more than once. 00978, 00000, "nested group function without GROUP BY" // *Cause: // *Action: 00979, 00000, "not a GROUP BY expression" // *Cause: // *Action: 00980, 00000, "synonym translation is no longer valid" // *Cause: // *Action: 00981, 00000, "cannot mix table and system auditing options" // *Cause: Table and system-wide auditing options were specified in the // same AUDIT or NOAUDIT statement. // *Action: You must issue table and system options in separate // statements. 00982, 00000, "missing plus sign" // *Cause: // *Action: 00984, 00000, "column not allowed here" // *Cause: // *Action: 00985, 00000, "invalid program name" // *Cause: // *Action: 00986, 00000, "missing or invalid group name(s)" // *Cause: // *Action: 00987, 00000, "missing or invalid username(s)" // *Cause: // *Action: 00988, 00000, "missing or invalid password(s)" // *Cause: // *Action: 00989, 00000, "too many passwords for usernames given" // *Cause: // *Action: 00990, 00000, "missing or invalid privilege" // *Cause: // *Action: 00991, 00000, "only MAC privileges may be granted to procedures" // *Cause: Object privileges or non-MAC system privileges // were granted to the procedure. // *Action: Only grant MAC privileges using the PROCEDURE clause. 00992, 00000, "invalid format for REVOKE command" // *Cause: // *Action: 00993, 00000, "missing GRANT keyword" // *Cause: // *Action: 00994, 00000, "missing OPTION keyword" // *Cause: // *Action: 00995, 00000, "missing or invalid synonym identifier" // *Cause: // *Action: 00996, 00000, "the concatenate operator is ||, not |" // *Cause: // *Action: 00997, 00000, "illegal use of LONG datatype" // *Cause: // *Action: 00998, 00000, "must name this expression with a column alias" // *Cause: // *Action: 00999, 00000, "invalid view name" // *Cause: // *Action: / / parse errors continue at 1700 / / 1000-1099 program interface errors / 01000, 00000, "maximum open cursors exceeded" // *Cause: // *Action: 01001, 00000, "invalid cursor" // *Cause: // *Action: 01002, 00000, "fetch out of sequence" // *Cause: This may be caused by fetching from a 'select for update' cursor // after a commit. A PL/SQL cursor loop implicitly does fetches // and may also cause this error. // *Action: 01003, 00000, "no statement parsed" // *Cause: // *Action: 01004, 00000, "default username feature not supported; logon denied" // *Cause: // *Action: 01005, 00000, "null password given; logon denied" // *Cause: // *Action: 01006, 00000, "bind variable does not exist" // *Cause: // *Action: 01007, 00000, "variable not in select list" // *Cause: // *Action: 01008, 00000, "not all variables bound" // *Cause: // *Action: 01009, 00000, "missing mandatory parameter" // *Cause: // *Action: 01010, 00000, "invalid OCI operation" // *Cause: One of the following: // 1) You attempted an invalid OCI operation. // 2) You are using an Oracle client application linked with // version 7.1 (or higher) libraries, the environment variable // ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to // connect to a version 7.0 (or lower) Oracle Server. // 3) You are connected to a version 7.1 (or higher) Oracle Server, // the initialization parameter DBLINK_ENCRYPT_LOGIN is set to // TRUE, and you attempted to use a database link pointing to a // version 7.0 (or lower) Oracle Server. // *Action: For the above causes: // 1) Do not use the invalid OCI operation. // 2) If you do not wish to use encrypted connect passwords in your // distributed database, set ORA_ENCRYPT_LOGIN to FALSE. // If you wish to use encrypted connect passwords, you must upgrade // all Oracle Servers to version 7.1 (or higher). // 3) If you do not wish to use encrypted database links in your // distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. // If you wish to use encrypted database links, you must upgrade // all Oracle Servers to version 7.1 (or higher). 01011, 00000, "Cannot use v7 compatibility mode when talking to v6 server" // *Cause: // *Action: Use v6 sql language type. You may need to use the // 'SET COMPATIBILITY V6' command 01012, 00000, "not logged on" // *Cause: // *Action: 01013, 00000, "user requested cancel of current operation" // *Cause: // *Action: 01014, 00000, "ORACLE shutdown in progress" // *Cause: // *Action: 01015, 00000, "logon called recursively" // *Cause: // *Action: 01016, 00000, "This function can be called only after a fetch" // *Cause: Cursor in an invalid state. // *Action: Make sure that the oci/upi function is called after fetch. 01017, 00000, "invalid username/password; logon denied" // *Cause: // *Action: 01018, 00000, "column does not have a LONG datatype" // *Cause: // *Action: 01019, 00000, "unable to allocate memory in the user side" // *Cause: The user side memory allocator returned error. // *Action: Increase the processes heap size or switch to the old set of calls. 01020, 00000, "unknown context state" // *Cause: // *Action: 01021, 00000, "invalid context size specified" // *Cause: // *Action: 01022, 00000, "database operation not supported in this configuration" // *Cause: The attempted database operation does not conform to the user // programming interface (UPI) for the two communicating // ORACLE servers. // *Action: You may need to upgrade one or more of your ORACLE servers or // re-link your user side application with new libraries. Report // the problem to Worldwide Customer Support. 01023, 00000, "Cursor context not found (Invalid cursor number)" // *Cause: The cursor number is not a valid open cursor. // *Action: Make sure that the cursor is open. 01024, 00000, "invalid datatype in OCI call" // *Cause: // *Action: 01025, 00000, "UPI parameter out of range" // *Cause: An integer parameter to a upi function is out of range. // *Action: This usually indicates an error in a tool built on top // of the oracle dbms. Report the error to your customer // support representative. 01026, 00000, "multiple buffers of size > 2000 in the bind list" // *Cause: More than one long buffer in the bind list. // *Action: Change the buffer size to be less than 2000 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 %s 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. 01053, 00000, "user storage address cannot be read" // *Cause: // *Action: 01054, 00000, "user storage address cannot be written" // *Cause: // *Action: 01057, 00000, "invalid or ambiguous block.field reference in user exit" // *Cause: // *Action: 01058, 00000, "internal New Upi interface error" // *Cause: Attempt to delete non existant hstdef extension. // *Action: Report as a bug. 01059, 00000, "parse expected before a bind or execute" // *Cause: The client application attempted to bind a variable or execute // a cursor opened in a PL/SQL block before the statement was parsed. // *Action: Ensure the statement is parsed before a bind or execute. 01060, 00000, "array binds or executes not allowed" // *Cause: The client application attempted to bind an array of cursors or // attempted to repeatedly execute against a PL/SQL block with a bind // variable of type cursor. // *Action: Bind a single cursor or execute the PL/SQL block once. / 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 servers" // *Cause: The value of the given parameter is required to be the same for all // servers in the parallel configuration. ROW_LOCKING and // SERIALIZABLE are 2 examples. // *Action: Change the value of the parameter in INIT.ORA file to match // that of other parallel servers. 01084, 00000, "invalid argument in OCI call" // *Cause: The failing OCI call contains an argument with an invalid value. // *Action: Use valid argument values. For more information, see the // Programmer's Guide to the Oracle Call Interfaces and the // appropriate programming language supplement. 01085, 00000, "preceding errors in deferred rpc to \"%s.%s.%s\"" // *Cause: Errors were encountered when the named procedure was executed // as a deferred remoted procedure call. // *Action: Correct the cause of the preceding errors. 01086, 00000, "savepoint '%s' never established" // *Cause: Trying to roll back to a save point that was never established. // *Action: 01087, 00000, "cannot start up ORACLE - currently logged on" // *Cause: // *Action: Logoff and then issue the STARTUP command. 01088, 00000, "cannot shut down ORACLE while active processes exist" // *Cause: Users are still logged into the instance. // *Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE. 01089, 00000, "immediate shutdown in progress - no operations are permitted" // *Cause: The SHUTDOWN IMMEDIATE command was used to shut down // a running ORACLE instance, so your operations have been // terminated. // *Action: Wait for the instance to be restarted, or contact your DBA. 01090, 00000, "shutdown in progress - connection is not permitted" // *Cause: The SHUTDOWN command was used to shut down a running // ORACLE instance, so you cannot connect to ORACLE. // *Action: Wait for the instance to be restarted, or contact your DBA. 01091, 00000, "failure during startup force" // *Cause: Unable to destroy the old SGA. // *Action: Manually remove the old SGA and reissue the STARTUP command 01092, 00000, "ORACLE instance terminated. Disconnection forced" // *Cause: The instance this process was connected to was terminated // abnormally, probably via a shutdown abort. This process // was forced to disconnect from the instance. // *Action: When 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 1250: db file errors / 01100, 00000, "database already mounted" // *Cause: A database is already mounted in this instance. // *Action: 01101, 00000, "database being created currently mounted by some other instance" // *Cause: Some other instance has the database of same name currently mounted // and you are trying to create it. // *Action: Either change the database name or shutdown the other instance. 01102, 00000, "cannot mount database in EXCLUSIVE mode" // *Cause: Some other instance has the database mounted exclusive or shared. // *Action: Shutdown other instance or mount in a compatible mode. 01103, 00000, "database name '%s' in 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 media recovery" // *Cause: Media recovery is activly being applied to the file. It cannot // be used for normal database access or crash recovery. // *Action: Complete or cancel the media recovery session. 01109, 00000, "database not open" // *Cause: A command was attempted that requires the database to be open. // *Action: Open the database and try the command again 01110, 00000, "data file %s: '%s'" // *Cause: Reporting file name for details of another error // *Action: See associated error message 01111, 00000, "name for data file %s is unknown - rename to correct file" // *Cause: The data file was missing from a CREATE CONTROLFILE command or // backup 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: Device on which the file resides is probably offline // *Action: Restore access to the device 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: Obvious // *Action: 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 EXCLUSIVE and not open for this operation" // *Cause: Obvious // *Action: 01127, 00000, "database name '%s' exceeds size limit of %s characters" // *Cause: Obvious // *Action: 01128, 00000, "cannot start online backup - file %s is offline" // *Cause: An attempt to start an online backup found that one of the files is // offline. // *Action: Bring the offending files online and retry this command or do a // cold backup. 01129, 00000, "user's default or temporary tablespace does not exist" // *Cause: The user's default or temporary tablespace was dropped. // *Action: Reassign the default or temporary tablespace. 01130, 00000, "database file version %s incompatible with ORACLE version %s" // *Cause: // *Action: 01131, 00000, "DB_FILES system parameter value %s exceeds limit of %s" // *Cause: // *Action: 01132, 00000, "length of database file name '%s' exceeds limit of %s characters" // *Cause: // *Action: 01133, 00000, "length of log file name '%s' exceeds limit of %s characters" // *Cause: // *Action: 01134, 00000, "database mounted exclusive by another instance" // *Cause: // *Action: 01135, 00000, "file %s accessed for DML/query is offline" // *Cause: Attempted to access a data file that is offline // *Action: Bring the data file back online 01136, 00000, "specified size of file %s (%s blocks) is less than original size of %s blocks" // *Cause: A file size was specified in the AS clause of ALTER DATABASE // CREATE DATAFILE, and the size was smaller the the size needed // *Action: Create the file with a larger size. 01137, 00000, "data file %s is still in the middle of going offline" // *Cause: It was not possible to get the lock for a file that is offline when // attempting to bring it online. The most likely cause is that the // lock is still held by the instance that is took it offline. // *Action: Wait a bit and try to online the file again. 01138, 00000, "database must either be open in this instance or not at all" // *Cause: The requested operation can not be done when the database is // mounted but not open in this instance, and another instance has // the database open. // *Action: Execute the operation in an open instance, open the datbase in // this instance, or close the database in the other instances. 01139, 00000, "RESETLOGS option only valid after an incomplete database recovery" // *Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there // has been no incomplete recovery session. // *Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS 01140, 00000, "cannot end online backup - all files are offline" // *Cause: All the files were found to be offline when attempting to end an // online backup. // *Action: None. Online backup does not need to be ended for this tablespace. 01141, 00000, "error renaming data file %s - new file '%s' not found" // *Cause: An attempt to change a data file's name in the 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. // *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 onlin 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, "database must be mounted EXCLUSIVE for this operation" // *Cause: An attempt was made to mount the database PARALLEL without the // the existence of a lock manager. // *Action: Mount the database in EXCLUSIVE mode. 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: Attempt to start an incompatible media recovery or open resetlogs // during media recovery. 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. // *Action: Complete or cancel the other media recovery session. 01154, 00000, "database busy. Open, close, mount, and dismount not allowed now" // *Cause: Some operation is in progress that expects the opened/mounted state // of this instance to remain the same. // *Action: Wait for the operation to complete then retry. If attempting to // do a shutdown, SHUTDOWN ABORT will work. 01155, 00000, "the database is being opened, closed, mounted or dismounted" // *Cause: The requested operation needs the instance to be in a particular // state but the state is being changed. // *Action: Wait for the open, close, mount, or dismount to complete then // retry the operation. If necessary, a SHUTDOWN ABORT will always // work. 01156, 00000, "recovery in progress may need access to files" // *Cause: Either media recovery or instance recovery is in progress. It may // need the files this operation is being applied to. // *Action: Wait for recovery to complete. 01157, 00000, "cannot identify data file %s - file not found" // *Cause: The background process was not able to find one of the data files. // 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 file was not found. // *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 DB_BLOCK_SIZE (%s)" // *Cause: CREATE CONTROLFILE discovered that the block size for this file // is incompatible with the init.ora parameter DB_BLOCK_SIZE used to // allocate cache buffers. If not the first file then there are a // mixture of block sizes, or the file is corrupt. // *Action:If this is the first file in the command then correct DB_BLOCK_SIZE // to match the file and restart the instance. If not the first file // find the correct version of the file. 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 mention 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. // *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. 01168, 00000, "physical block size %s does not match size %s of other members" // *Cause: The file is located on a device with a different physical block // size than the other members in the group // *Action: Use a physical device with matching block size. 01169, 00000, "DATAFILE number 1 not found. Must be present" // *Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command. // *Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE // command. 01170, 00000, "file not found '%s'" // *Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be // accessible by the process for CREATE CONTROLFILE. // *Action: The file specified probably contains a typing error. Double // check command and the existance of all files and then resubmit. 01171, 00000, "datafile %s going offline due to error advancing checkpoint" // *Cause: The checkpoint in the file header could not be advanced. See // accompanying errors for the reason. The datafile will be taken // offline the same as for a write error of a data block. // *Action: See accompanying errors for details. Restore access to the file, // do media recovery, and bring it back online. 01172, 00000, "recovery of thread %s stuck at block %s of file %s" // *Cause: Crash recovery or instance recovery could not apply a change to a // block because it was not the next change. This can happen if the // block was corrupted and then repaired during recovery. // *Action: Do a RECOVER DATAFILE for the file containing the block. If this // does not resolve the problem then restore the file from a backup // and recover it. 01173, 00000, "data dictionary indicates missing data file from system tablespace" // *Cause: Either the database has been recovered to a point in time in the // future of the controlfile or a datafile from the system tablespace was // omitted from the create controlfile command previously issued. // *Action: For the former problem you need to recover the database from a // more recent controlfile. For the latter problem, simply recreate the // controlfile checking to be sure that you include all the datafiles in // the system tablespace. 01174, 00000, "DB_FILES is %s buts needs to be %s to be compatible" // *Cause: The maximum number of database files supported by this instance // is not the same as for the other instances. All instances must // be able to open all the files any instance can open. // *Action: Change the value of the DB_FILES parameter to be compatible 01175, 00000, "data dictionary has more than the %s files allowed by the instance" // *Cause: The data dictionary is found to have more files than that which can // be supported by this instance. // *Action: Shutdown the instance and restart with a larger number of db_files 01176, 00000, "data dictionary has more than the %s files allowed by the controlfie" // *Cause: After a CREATE CONTROLFILE, the data dictionary was found to have // more datafiles than that supported by the controlfile. // *Action: Recreate the controlfile with a larger MAXDATAFILES. 01177, 00000, "data file does not match dictionary - probably old incarnation" // *Cause: When comparing the 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 CONTROL file 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 RESETLOGS, cannot recreate" // *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a // datafile that existed at the last RESETLOGS database open. // *Action: Find a backup of the file, and recover it. Do incomplete recovery // to time before file was originally created. 01182, 00000, "cannot create database file %s - file is in use or recovery" // *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a // datafile that is online in an open instance or is being recovered. // *Action: Close database in all instances and end all recovery sessions 01183, 00000, "cannot mount database in SHARED mode" // *Cause: Some other instance has the database mounted exclusive. // *Action: Shutdown other instance then mount shared. 01184, 00000, "logfile group %s already exists" // *Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for // the new log which is already in use. // *Action: Specify a different logfile number, or let the database choose // an unused value. 01185, 00000, "logfile group number %s is invalid" // *Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for // the new log which is too large. // *Action: Specify a correct logfile number. 01186, 00000, "file %s failed verification tests" // *Cause: The data file did not pass the checks to insure it is part of the // database. See the accompanying error messages for the reason the // verification did not succeed. // *Action: Have operating system make the correct file available to database. // Then either open the database or do ALTER DATABASE CHECK. 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: Have operating system make the correct file available to database. // Then either open the database or do ALTER DATABASE CHECK. 01188, 00000, "Block size %s in header does not match physical block size %s" // *Cause: A log file member given to CREATE CONTROLFILE is on a physical // device that has a different block size than the device originally // used to create the log. // *Action: Move the file to a device with the correct block size or use the // RESETLOGS option to CREATE CONTROLFILE. 01189, 00000, "file is from a different RESETLOGS than previous files" // *Cause: In a CREATE CONTROLFILE command either this file or all previous // files were backups from before the last RESETLOGS. This may also // occur if this is a file that is offline and has been offline since // before the last RESETLOGS. // *Action: If the file was taken offline normal before the last RESETLOGS, // and is still offline, omit it from the CREATE CONTROLFILE command. // Rename and online the file after the database is open. Otherwise // find the version of the mentioned file consistent with the rest // of the datafiles and resubmit the command. 01190, 00000, "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 size %s in header does not match size %s in control file" // *Cause: The file sizes in the control file and in the file header do not // match. One of them is probably a corrupted value. // *Action: Replace the corrupted file with a good one and do recovery as // 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. // *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 controlfile recovery to // make the control file current. Be sure to follow all restrictions // on doing a backup controlfile recovery. 01208, 00000, "data file is an old version - not accessing current version" // *Cause: The checkpoint in the file header is less recent than in the // control file. If opening a database that is already open by another // instance, or if another instance just onlined this file, then // we are probably looking at a different version of the file. // Otherwise a backup of the file was probably restored while the // file was in use. // *Action: Have operating system make correct file available to database. // Then either open the database or do ALTER DATABASE CHECK. 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 // this is an old backup that was taken before the last ALTER // DATABASE OPEN RESETLOGS command. If opening a database that is // already open by another instance, or if another instance just // onlined this file, then we are probably looking at a different // version of the file. Otherwise a backup of the file was probably // restored while the file was in use. // *Action: Have operating system make correct file available to database. // Then either open the database or do ALTER DATABASE CHECK. 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, "version 6 data file is not from conversion to version 7" // *Cause: The file is not a copy of the file last used under version 6. When // converting a database from version 6 to version 7 the conversion // utility must be run the last time the database is opened under // version 6. Only the datafiles that were current when the conversion // was done may be accessed by version 7. This datafile is either // a backup taken from before the conversion, or the database was // opened by version 6 after the conversion. // *Action: Have operating system make correct data file available to database, // or repeat the version 6 to version 7 conversion. 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 // sort_area_size init.ora parameter 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 accompaning 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 accompaning 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 accompaning error is inconsistent with the // contents of the logs given in the CREATE CONTROLFILE command. // The most likely cause is that one or more of the online logs // was missing from the command. It is also possible that one or // more of the logs is an old copy rather than the current version. // All online log files must be listed in the command and must be the // current versions of the online logs. //*Action: Find the correct online logs or use the RESETLOGS option. 01230, 00000, "cannot make read only - file %s is offline" // *Cause: An attempt to make a tablespace read only found that one of its // files is offline. // *Action: Bring the file online and retry this command. 01231, 00000, "cannot make read write - file %s is offline" // *Cause: An attempt to make a tablespace read write found that one of its // files is offline. // *Action: Bring the file online and retry this command. 01232, 00000, "cannot start online backup - file %s is read only" // *Cause: An attempt to start an online backup found that one of the files is // marked read only. Read only files do not need to be set into // online backup mode. // *Action: Make the backup without the begin backup command. 01233, 00000, "file %s is read only - cannot recover using backup controlfile" // *Cause: An attempt to do media recovery using a backup controlfile found // that one of the files is marked read only. Read only files do not // normally need to be recovered, but recovery with a backup // controlfile must recover all online files. // *Action: If the file really is read only, take it offline before the // recovery, and bring the read only tablespace online after the // database is open. If the file does need recovery use a controlfile // from the time the file was read-write. If the correct controlfile // is not available, use CREATE CONTROLFILE to make one. 01234, 00000, "cannot end backup of file %s - file is in use or recovery" // *Cause: Attempted to end an online backup of file when the file is busy. // Some operation such as recovery or rename may be active, or there // may still be some instance that has the database open with this // file online. // *Action: If there is an instance with the database open then the backup // can be ended there by using the ALTER TABLESPACE command. Otherwise // wait for the completion of the other operation. 01235, 00000, "END BACKUP failed for %s file(s) and succeeded for %s" // *Cause: One or more of the files in an end backup command failed. Some other // files given in the same command may have succeeded. // *Action: See the accompanying error messages for the reason the backups // could not be ended. Any files not listed in the error messages were // successful. 01237, 00000, "cannot extend datafile %s" // *Cause: An operating system error occurred during the resize. // *Action: Fix the cause of the operating system error and retry the command. 01238, 00000, "cannot shrink datafile %s" // *Cause: An operating system error occurred during the resize. // *Action: The error is ignored, operation continues normally. 01239, 00000, "database must be in ARCHIVELOG mode to use external cache" // *Cause: An online file uses an external cache, but the database is in // NOARCHIVELOG mode. Since an external cache may require media // recovery this can not be allowed. // *Action: Change database to be in ARCHIVELOG mode or do not use an // external cache. 01240, 00000, "too many data files to add in one command" // *Cause: The command specifies adding more data files than can be done in // one command. It is necessary to fit all the file names into one // log entry, but that would make the entry too large. // *Action: If this is a CREATE TABLESPACE command, create with fewer files // then add the other files later. If this is an ADD DATAFILE command, // break it up into multiple commands. 01241, 00000, "an external cache has died" // *Cause: The external cache may have been restarted. // *Action: Take the file mentioned in the error stack offline, perform media // recovery, bring the file online, and retry the attempted // operation. You may also restart all instances to make sure // they access all data files through consistent external caches. 01242, 00000, "data file suffered media failure: database in NOARCHIVELOG mode" // *Cause: The database is in NOARCHIVELOG mode and a database file was // detected as inaccessible due to media failure. // *Action: Restore accessibility to the file mentioned in the error stack // and restart the instance. 01243, 00000, "system tablespace file suffered media failure" // *Cause: A system tablespace file was detected as inaccessible due to // media failure. // *Action: Restore accessibility to the file mentioned in the error stack // and restart the instance. 01244, 00000, "unnamed datafile(s) added to controlfile by media recovery" // *Cause: Media recovery with a backup controlfile or a controlfile that // was rebuilt, encountered the creation of a datafile that was not // in the controlfile. An entry has been added to the controlfile // for the new datafiles, but with the file name UNNAMEDnnnn, where // nnnn is the file number. Attached errors describe the file names // that were originally used to create the files. // *Action: Rename the files to valid file names and resume recovery. If // necessary the command ALTER DATABASE CREATE DATAFILE may be used // to create a file suitable for recovery and do the rename. If the // file is not going to be recovered then take it offline with the // 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 // DROP option. // *Action: Either bring the file online and recover it, or take it offline // with the DROP option. / / 1380-1399 KST tracing errors renumbered at 2480-2499 for MERGE / / 1400-1499 SQL execute phase errors / 01400, 00000, "mandatory (NOT NULL) column is missing or NULL during insert" // *Cause: // *Action: 01401, 00000, "inserted value too large for column" // *Cause: // *Action: 01402, 00000, "view WITH CHECK OPTION where-clause violation" // *Cause: // *Action: 01403, 00000, "no data found" // *Cause: // *Action: 01404, 00000, "ALTER COLUMN will make an index too large" // *Cause: // *Action: 01405, 00000, "fetched column value is NULL" // *Cause: // *Action: 01406, 00000, "fetched column value was truncated" // *Cause: // *Action: 01407, 00000, "cannot update mandatory (NOT NULL) column 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. 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: 01430, 00000, "column being added already exists in table" // *Cause: // *Action: 01431, 00000, "internal inconsistency in GRANT command" // *Cause: // *Action: 01432, 00000, "public synonym to be dropped does not exist" // *Cause: // *Action: 01433, 00000, "synonym to be created is already defined" // *Cause: // *Action: 01434, 00000, "private synonym to be dropped does not exist" // *Cause: // *Action: 01435, 00000, "user does not exist" // *Cause: // *Action: 01436, 00000, "CONNECT BY loop in user data" // *Cause: // *Action: 01437, 00000, "cannot have join with CONNECT BY" // *Cause: // *Action: 01438, 00000, "value larger than specified precision allows for this column" // *Cause: // *Action: 01439, 00000, "column to be modified must be empty to change datatype" // *Cause: // *Action: 01440, 00000, "column to be modified must be empty to decrease precision or scale" // *Cause: // *Action: 01441, 00000, "column to be modified must be empty to decrease column length" // *Cause: // *Action: 01442, 00000, "column to be modified to NOT NULL is already NOT NULL" // *Cause: // *Action: 01443, 00000, "internal inconsistency; illegal datatype in resultant view column" // *Cause: // *Action: 01444, 00000, "internal inconsistency; internal datatype maps to invalid external type" // *Cause: // *Action: 01445, 00000, "cannot select ROWID from a join view without a key-preserved table" // *Cause: // *Action: 01446, 00000, "cannot select ROWID from view with DISTINCT, GROUP BY, etc." // *Cause: // *Action: 01447, 00000, "ALTER TABLE does not operate on clustered columns" // *Cause: // *Action: 01448, 00000, "index must be dropped before changing to desired type" // *Cause: // *Action: 01449, 00000, "column contains NULL values; cannot alter to NOT NULL" // *Cause: // *Action: 01450, 00000, "maximum key length (%s) exceeded" // *Cause: // *Action: 01451, 00000, "column to be modified to NULL cannot be modified to NULL" // *Cause: the column may already allow NULL values, the NOT NULL constraint // is part of a primary key or check constraint. // *Action: if a primary key or check constraint is enforcing the NOT NULL // constraint, then drop that constraint. 01452, 00000, "cannot CREATE UNIQUE INDEX; duplicate keys found" // *Cause: // *Action: 01453, 00000, "SET TRANSACTION must be first statement of transaction" // *Cause: self-evident // *Action: commit (or rollback) transaction, and re-execute 01454, 00000, "cannot convert column into numeric datatype" // *Cause: // *Action: 01455, 00000, "converting column overflows integer datatype" // *Cause: // *Action: 01456, 00000, "may not perform insert/delete/update operation inside a READ ONLY transaction" // *Cause: A non-DDL insert/delete/update or select for update operation // was attempted // *Action: commit (or rollback) transaction, and re-execute 01457, 00000, "converting column overflows decimal datatype" // *Cause: // *Action: 01458, 00000, "invalid length inside variable character string" // *Cause: // *Action: 01459, 00000, "invalid length for variable character string" // *Cause: // *Action: 01460, 00000, "unimplemented or unreasonable conversion requested" // *Cause: // *Action: 01461, 00000, "can bind a LONG value only for insert into a LONG column" // *Cause: // *Action: 01462, 00000, "cannot insert string literals longer than 2000 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. 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 second or third parameter to 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 2000 bytes // (for example, VARCHAR or LONG). // *Action: 01487, 00000, "packed decimal number too large for supplied buffer" // *Cause: An impossible request for decimal to oracle number conversion was // made // *Action: This conversion cannot be performed 01488, 00000, "invalid nibble or byte in the input data" // *Cause: An impossible request for decimal to oracle number conversion was // made // *Action: This conversion cannot be performed 01489, 00000, "result of string concatenation is too long" // *Cause: String concatenation result is more than the maximum size. // *Action: Make sure that the result is less than the maximum size. / / 1490 - 1499 Analyze Parse and Execution Errors / 01490, 00000, "invalid ANALYZE command" // *Cause: Incorrect syntax specified // *Action: Retry the command 01491, 00000, "CASCADE option not valid" // *Cause: The CASCADE option is only valid for tables or clusters. // *Action: Do not specify CASCADE 01492, 00000, "LIST option not valid" // *Cause: The LIST option is only valid for tables or clusters. // *Action: Do not specify LIST 01493, 00000, "invalid SAMPLE size specified" // *Cause: The specified SAMPLE size is out of range // *Action: Specify a value within the proper range. 01494, 00000, "invalid SIZE specified" // *Cause: The specified histogram SIZE value was out of range. // *Action: Specify a value within the proper range. 01495, 00000, "specified chain row table not found" // *Cause: The specified table either does not exist or user does not have // the proper privleges. // *Action: Specify the correct table to use. 01496, 00000, "specified chain row table form incorrect" // *Cause: The specified table does not have the proper field definitions. // *Action: Specify the correct table to use. 01497, 000000, "illegal option for ANALYZE CLUSTER" // *Cause: The FOR COLUMNS clause may not be used with // ANALYZE CLUSTER. // *Action: Retry with a legal syntax. 01498, 00000, "block check failure - see trace file" // *Cause: // *Action: 01499, 00000, "table/index cross reference failure - see trace file" // *Cause: // *Action: / / 1500 - 1699 V6 Execution errors / 01500, 00000, "failure in getting date/time" // *Cause: During create database or alter tablespace, there was a failure // in getting the date and time. // *Action: Contact your customer support representative. 01501, 00000, "CREATE DATABASE failed" // *Cause: An error occurred during create database // *Action: See accompanying errors. 01502, 00000, "index '%s.%s' is in direct load state" // MERGE: 1489 RENUMBERED TO 1502 // *Cause: The specified index has been marked invalid by a direct load" // *Action: Drop the specified index" 01503, 00000, "CREATE CONTROLFILE failed" // *Cause: An error occurred during CREATE CONTROLFILE // *Action: See accompanying errors. 01504, 00000, "database name '%s' does not match parameter db_name '%s'" // *Cause: The name in a database create or mount does not match the name // given in the init.ora parameter db_name. // *Action: correct or omit one of the two names. 01505, 00000, "error in adding log files" // *Cause: During create or alter database, error(s) occurred when // adding new log files. // *Action: Check error stack for detailed error information. 01506, 00000, "missing or illegal database name" // *Cause: No database name was specified in the CREATE/ALTER DATABASE // statement, and no db_name init.ora parameter was specified. // *Action: Either the database name must be given in the // statement or in the db_name init.ora parameter. // Note that the SQLDBA STARTUP command issues an ALTER // DATABASE statement using the database name specified as // part of STARTUP (if any). 01507, 00000, "database not mounted" // *Cause: ALTER DATABASE specifies the name of a database to alter, but // no database is currently 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. 01508, 00000, "cannot create database; error in file '%s' at line %s" // *Cause: CREATE DATABASE was unable to process the specified file. // *Action: Check the offending line in the specified file. 01509, 00000, "specified name '%s' does not match actual '%s'" // *Cause: The database name specified in ALTER DATABASE does not // match the name of the currently mounted database. // *Action: Correct the database name spelling or DISMOUNT the mounted // database. 01510, 00000, "error in deleting log files" // *Cause: During ALTER DATABASE, an error occurred while dropping // log files. // *Action: Check the error stack for detailed error information. 01511, 00000, "error in renaming log/data files" // *Cause: During ALTER DATABASE, an error occurred while renaming // log or data files. // *Action: Check the error stack for detailed error information. 01512, 00000, "error renaming log file %s - new file %s not found" // *Cause: An attempt to change a log file's name in the 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/data file '%s'" // *Cause: ALTER DATABASE is attempting to rename/create a log or a data // file which is not known to the database control file. // *Action: Specify the name of an existing log file. 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" // *Cause: Specified rollback segment already exists. // *Action: Use a different name. 01536, 00000, "space quota exceeded for tablespace '%s'" // *Cause: The user is attempting to perform an operation which // requires the creation of a new extent in a tablespace. // The user has already reached his quota of space in the tablespace. // *Action: The owner of the tablespace or a privileged user must grant // additional resource quota on the tablespace to the user. 01537, 00000, "cannot add data file '%s' - file already part of database" // *Cause: During CREATE or ALTER TABLESPACE, a file being added is already // part of the database. // *Action: Use a different file name. 01538, 00000, "failed to acquire any rollback segment" // *Cause: Failed to acquire any rollback segment during startup in shared mode // *Action: Startup in exclusive mode to create one more public segment or // specify available private segments in the init.ora parameter // rollback_segments_required, then startup in shared mode 01539, 00000, "tablespace '%s' is not online" // *Cause: Failed to either make a tablespace read only or offline because // it is not online. A tblespace must be online before it can // become read only or offline normal. // *Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY // options to force all files offline. Bring the tablespace online // before making it read only. 01540, 00000, "tablespace '%s' is not offline" // *Cause: Failed to bring a tablespace online because it is not offline // *Action: Check the status of the tablespace 01541, 00000, "system tablespace cannot be brought offline; shut down if necessary" // *Cause: Tried to bring system tablespace offline // *Action: Shutdown if necessary to do recovery 01542, 00000, "tablespace '%s' is offline, cannot allocate space in it" // *Cause: Tried to allocate space in an offline tablespace // *Action: Bring the tablespace online or create the object in other // tablespace 01543, 00000, "tablespace '%s' already exists" // *Cause: Tried to create a tablespace which already exists // *Action: Use a different name for the new tablespace 01544, 00000, "cannot drop system rollback segment" // *Cause: Tried to drop system rollback segment // *Action: None 01545, 00000, "rollback segment '%s' specified not available" // *Cause: Either: // 1) An attempt was made to bring a rollback segment online that is // unavailable during startup; for example, the rollback segment // is in an offline tablespace. // 2) An attempt was made to bring a rollback segment online that is // already online. This is because the rollback segment is // specified twice in the ROLLBACK_SEGMENTS parameter in the // initialization parameter file or the rollback segment is already // online by another instance. // 3) An attempt was made to drop a rollback segment that is // currently online. // 4) An attempt was made to alter a rollback segment that is // currently online to use unlimited extents. // *Action: Either: // 1) Make the rollback segment available; for example, bring an // offline tablespace online. // 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name // is a duplicate or if another instance has already acquired the // rollback segment. // 3) Bring the rollback segment offline first. This may involve // waiting for the active transactions to finish, or, if the // rollback segment needs recovery, discover which errors are // holding up the rolling back of the transactions and take // appropriate actions. // 4) Same as 3). 01546, 00000, "tablespace contains active rollback segment '%s'" // *Cause: Tried to make a tablespace that contains active rollback segment(s) // offline or read only // *Action: Shutdown instances that use the active rollback segments in the // tablespace and then make the tablespace offline or read only 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 // *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 01553, 00000, "MAXEXTENTS must be no smaller than the %s extents currently allocated" // *Cause: The number of extents allocated is greater than the MAXEXTENTS // specified. // *Action: Specify a larger MAXEXTENTS value. 01554, 00000, "out of transaction slots in transaction tables" // *Cause: Too many concurrent transactions // *Action: Shutdown the system, modify the init.ora parameters transactions, // rollback_segments or rollback_segments_required, then // startup again 01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small" // *Cause: rollback records needed by a reader for consistent read are // overwritten by other writers // *Action: 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, "global hash table size mismatch for %s (%s != %s)" // *Cause: The specified "gc_" init.ora parameter has an incompatible // with that of another instance which already has the database // mounted. // *Action: Fix the "gc_" parameter and restart. 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. Shutdown, restart and then take appropriate action for // the error the caused the failure. If starting up the system // again doesn't solve the problem, it is possible that there is // an active transaction in the rollback segment and the system // can't roll it back for some reasons. Check the trace file // generated by the PMON process for more information. 01563, 00000, "rollback segment is PUBLIC, need to use the keyword PUBLIC" // *Cause: Did not use the keyword PUBLIC to identified public rollback segment // *Action: Use the keyword PUBLIC when identifying public rollback segment 01564, 00000, "rollback segment is not PUBLIC" // *Cause: The rollback segment segment identified is not public // *Action: Do not use the keyword PUBLIC when identifying private rollback // segment 01565, 00000, "error in identifying file '%s'" // *Cause: An error occurred while trying to identify a file. // *Action: Check the error stack for detailed information. 01566, 00000, "file specified more than once in DROP LOGFILE" // *Cause: The list of files supplied to DROP LOGFILE contains at least one // duplicate. // *Action: Remove the duplicate file specification and retry. 01567, 00000, "dropping log %s would leave less than 2 log files in thread %s" // *Cause: Dropping all the logs specified would leave fewer than the required // two log files per enabled thread. // *Action: Either drop fewer logs or disable the thread before deleting the // logs. It may be possible to clear the log rather than drop it. 01568, 00000, "cannot set space quota on PUBLIC" // MERGE: 1568 PROBABLY OBSOLETE // *Cause: Trying to set space quota on a tablespace for PUBLIC. // *Action: If trying to grant system-wide or tablespace-wide space priviledges // to all users, use GRANT RESOURCE [ON ] TO PUBLIC. 01569, 00000, "data file too small for system dictionary tables" // *Cause: The datafile specified during creation of the database is too // small to hold the system dictionary tables. // *Action: Recreate the database by specifying a larger file or more files. 01570, 00000, "MINEXTENTS must be no larger than the %s extents currently allocated" // *Cause: The number of extents allocated is smaller than the MINEXTENTS // specified. // *Action: Specify a smaller MINEXTENTS value. 01571, 00000, "redo version %s incompatible with ORACLE version %s" // *Cause: This software version can not read the current redo logs, and // either crash recovery is required or there are offline database // files that need media recovery. If a file name is listed then // it needs media recovery. // *Action: Shutdown and startup using the compatible software. Do any required // media recovery, and open the database. Shutdown and then startup // using current software. If the file is going to be dropped then // take it offline with the DROP option to skip this check. 01572, 00000, "global hash table size %s for rollback segments is too small for rollback segment ID %s" // *Cause: obvious // *Action: shutdown the instance, increase the init.ora parameter // 'gc_rollback_segments' to a number greater than the // id of the rollback segment involved. Then warmstart the instance. 01573, 00000, "shutting down instance, no further change allowed" // *Cause: Some process tries to make changes while the db is being shutdown // *Action: None 01574, 00000, "maximum number of concurrent transactions exceeded" // *Cause: the limit on the number of concurrent transactions has been hit // *Action: shutdown the system, increase the init.ora parameter 'transactions' // , and then restart the system. 01575, 00000, "timeout waiting for space management resource" // *Cause: failed to acquire necessary resource to do space management. // *Action: Retry the operation. 01576, 00000, "instance locking protocol version %s incompatible with ORACLE version %s" // *Cause: Current software uses incompatible locking protocol. // *Action: Upgrade software used to start up instances so that they use // compatible locking protocol. 01577, 00000, "cannot add log file '%s' - file already part of database" // *Cause: During CREATE or ALTER DATABASE, a file being added is already // part of the database. // *Action: Use a different file name. 01578, 00000, "ORACLE data block corrupted (file # %s, block # %s)" // *Cause: The data block indicated was corrupted, mostly due to software // errors. // *Action: Try to restore the segment containing the block indicated. This // may involve dropping the segment and recreating it. If there // is a trace file, report the errors in it to your ORACLE // representative. 01579, 00000, "write error occurred during recovery" // *Cause: A write error occurred during recovery // *Action: Consult trace files for the nature of the write error, and // correct error. 01580, 00000, "error creating control backup file %s" // *Cause: An operating system error occurred while attempting to create a // 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, "unable to open destination file %s 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 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. // *Action: Use the RESETLOGS option when opening the database. 01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open" // *Cause: Either incomplete or backup controlfile recovery has been // performed. After these types of recovery you must specify either // the RESETLOGS option or the NORESETLOGS option to open your // database. // *Action: Specify the appropriate option. 01590, 00000, "number of segment free list (%s) exceeds maximum of %s" // *Cause: storage parameter FREELIST GROUPS is too large. // *Action: Reduce storage parameters FREELIST GROUPS 01591, 00000, "lock held by in-doubt distributed transaction %s" // *Cause: Trying to access resource that is locked by a dead two-phase commit // transaction that is in prepared state. // *Action: DBA should query the pending_trans$ and related tables, and attempt // to repair network connection(s) to coordinator and commit point. // If timely repair is not possible, DBA should contact DBA at commit // point if known or end user for correct outcome, or use heuristic // default if given to issue a heuristic commit or abort command to // finalize the local portion of the distributed transaction. 01592, 00000, "error converting Version 6 rollback segment (%s) to Oracle7 format" // *Cause: Look at the accompanying internal error; Version 6 database may not // have shutdown cleanly. // *Action: Investigate the internal error; may have to reload the Version 6 // 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 (currently has (%s) entries)" // *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 gc_files_to_locks" // *Cause: init.ora parameter gc_files_to_locks mis-specified // *Action: 01601, 00000, "illegal bucket size in clause \"%s\" of gc_files_to_locks" // *Cause: // *Action: 01602, 00000, "more locks in gc_files_to_locks than reserved in gc_db_locks" // *Cause: // *Action: 01603, 00000, "illegal grouping size in clause \"%s\" of gc_files_to_locks" // *Cause: // *Action: 01604, 00000, "illegal file number range in clause \"%s\" of gc_files_to_locks" // *Cause: // *Action: 01605, 00000, "missing file numbers in clause \"%s\" of gc_files_to_locks" // *Cause: // *Action: 01606, 00000, "gc_files_to_locks not identical to that of another mounted instance" // *Cause: // *Action: Modify the init.ora parameter gc_files_to_locks and restart 01607, 00000, "gc_lck_procs (%s) is not the same as other instances (%s)" // *Cause: The gc_lck_procs init.ora parameter is not the same as in other // instances that already have the database open. // *Action: Modify the gc_lck_procs parameter and restart the instance. 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 01612, 00000, "thread %s is already enabled" // *Cause: An attempt was made to enable a thread that is already enabled. // *Action: Either use this thread or enable another thread. 01613, 00000, "thread %s only has %s logs - at least 2 logs required to enable" // *Cause: The thread cannot be enabled because it only has two online log // files associated with it. // *Action: Add logs to the thread or pick another thread to enable 01614, 00000, "thread %s is busy - cannot enable" // *Cause: The mount enqueue for the thread could not be acquired when // attempting to enable the thread. This probably means that another // process has already started enabling this thread. // *Action: Wait and try again, or find another thread to enable. 01615, 00000, "thread %s is mounted - cannot disable" // *Cause: Some instance, possibly this one, has allocated the thread for its // use. The thread may not be disabled while in use. // *Action: Shutdown cleanly the instance using the thread. 01616, 00000, "thread %s is open - cannot disable" // *Cause: The thread is not closed. The last instance to use the thread died // leaving the thread open. A thread cannot be disabled until it is // closed. It is still required for crash or instance recovery. // *Action: If the database is open, instance recovery should close the thread // soon - wait a few minutes. Otherwise open the database - crash // recovery will close the thread. 01617, 00000, "cannot mount: %s is not a valid thread number" // *Cause: The init.ora parameter "thread" is not between 1 and the number // of threads allowed when the database was created. // *Action: Shutdown the instance, change the init.ora parameter and startup 01618, 00000, "thread %s is not enabled - cannot mount" // *Cause: The init.ora parameter "thread" requests a thread that is not // enabled. A thread must be enabled before it can be mounted. // *Action: Shutdown the instance, change the init.ora parameter and startup // mounting a different thread. If the database is open in another // instance then the thread may be enabled. 01619, 00000, "thread %s is mounted by another instance" // *Cause: The init.ora parameter "thread" requests a thread that has been // mounted by another instance. Only one instance may use a thread. // *Action: Shutdown the instance, change the init.ora parameter and startup // mounting a different thread. 01620, 00000, "no public threads are available for mounting" // *Cause: The init.ora parameter "thread" is zero, its default value. // There are no threads which have been publicly enabled, and not // mounted. // *Action: Shutdown the instance, change the init.ora parameter to a thread // which is privately enabled and not mounted. If the database is // open in another instance, then a thread may be publicly enabled. 01621, 00000, "cannot rename member of current log if database is open" // *Cause: This is a rename command for a member of the current log for // an open thread. If the database is open anywhere, the log may be // in use, so the rename cannot be done. // *Action: Wait until the log is not current, or mount the database // exclusively. 01622, 00000, "thread number must be specified - default not specific" // *Cause: The thread was not specified when adding a log, and the currently // mounted thread was chosen by default at mount time. Since the // current thread was not specified explicitly the user cannot know // which thread the log will be added to. // *Action: Explicitly specify the thread number either in the init.ora // parameter "thread", or in the add command. 01623, 00000, "log %s is current log for thread %s - cannot drop" // *Cause: A thread's current log cannot be dropped even if the thread is // closed. A disabled thread usually does not have a current log, // but a half completed disable may need to be disabled again. // *Action: If the database is not open then disable the thread. If the // database is open and an instance has the thread open, then the // instance can be requested to switch logs. If the database is // closed the log can be archived or cleared to force a switch. 01624, 00000, "log %s needed for crash recovery of thread %s" // *Cause: A log cannot be dropped or cleared until the thread's checkpoint // has advanced out of the log. // *Action: If the database is not open then open it. Crash recovery will // advance the checkpoint. If the database is open force a global // checkpoint. If the log is corrupted so that the database cannot // be opened, it may be necessary to do incomplete recovery until // cancel at this log. 01625, 00000, "rollback segment '%s' does not belong to this instance" // *Cause: Trying to shrink or take a rollback segment offline that does not // belong to this instance. // *Action: 01626, 00000, "rollback segment number '%s' cannot handle more transactions" // *Cause: Too many transactions in this segment. // *Action: Choose a different rollback segment, or reduce the number // of concurrent transactions. 01627, 00000, "rollback segment number '%s' is not online" // *Cause: Could have been taken offline before by DBA or cleaned up // by SMON. // *Action: Check the status of rollback segment in undo$ or dba_rollback_segs // to make sure the rollback segment is actually online. 01628, 00000, "max # extents (%s) reached for rollback segment %s" // *Cause: Tried to extend rollback segment already at maxexents value // *Action: If maxextents storage parameter less than system allowable max, // raise this value. Consider upping the pctincrease value as well. 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, "parallel Server Option needed for this operation" // *Cause: System doesn't have parallel server configured // *Action: Obtain parallel server 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 parallel" // *Cause: The recovery compatible parameter is set too low to allow this // software version to do a parallel mount. // *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, "database cannot be mounted parallel with no lock processes" // *Cause: The value of gc_lck_procs is 0, and the database is being mounted // in parallel mode. // *Action: Change gc_lck_procs to a value between 1 and 10, or leave it // it undefined to use the builtin default. 01640, 00000, "cannot make tablespace read only with active transactions" // *Cause: Attempting to make a tablespace read only while there are active // transactions in the database. All transactions must commit or // rollback to insure that there is no undo for a tablespace before // it can be made read only. This includes in doubt distributed // transactions. // *Action: Prevent any more transactions from being started. Putting the // database in restricted mode usually helps. If there are any in // doubt transactions they must also be resolved. 01641, 00000, "tablespace '%s' is not online - cannot add data file" // *Cause: Attempting to add a datafile to a tablespace that has been set // to read only or offline. // *Action: Make the tablespace online and read write then add the datafile. 01642, 00000, "begin backup not needed for read only tablespace '%s'" // *Cause: Attempting to begin or end a backup for a tablespace that has // been set to read only. // *Action: Take the backup without any begin or end commands. The files // are not being modified so the backup will be consistent. 01643, 00000, "system tablespace can not be made read only" // *Cause: Attempting to set the system tablespace to read only. The system // tablespace must remain read write for database operation. // *Action: Leave system tablespace read write. 01644, 00000, "tablespace '%s' is already read only" // *Cause: Attempting to make tablespace read only that is already read only. // *Action: Leave tablespace read only, or make read write then make // read only again. 01645, 00000, "previous attempt to make read write is half complete" // *Cause: A failure while making the tablespace read write left it read // only, but the checkpoint was advanced. The tablespace will not // be useable after a resetlogs if its files are offline. // *Action: Repeat the command to make the tablespace read write. 01646, 00000, "tablespace '%s' is not read only - cannot make read write" // *Cause: Attempting to make a tablespace read write that is not read only. // It may be either online or offline. // *Action: Leave tablespace read write. 01647, 00000, "tablespace '%s' is read only, cannot allocate space in it" // *Cause: Tried to allocate space in a read only tablespace // *Action: Create the object in another tablespace 01648, 00000, "log %s is the current log of disabled thread %s" // *Casue: An attempt to enable the thread failed after it was half completed. // This log was left as the current log even though the thread is still // disabled. Since a log switch cannot be done until the thread is // enabled, the log can not be cleared or archived. // *Action:Complete the thread enable by issuing the enable command again. 01649, 00000, "operation not allowed with a backup control file" // *Cause: An attempt is being made to preform 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 for rollback segment in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01651, 00000, "unable to extend save undo segment by %s for tablespace %s" // *Cause: Failed to allocate an extent for saving undo entries for // the indicated offline tablespace. // *Action: Check the storage parameters for the SYSTEM tablespace. The // tablespace needs to be brought back online so the undo can be // applied. 01652, 00000, "unable to extend temp segment by %s in tablespace %s" // *Cause: Failed to allocate an extent for temp segment in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01653, 00000, "unable to extend table %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent for table segment in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01654, 00000, "unable to extend index %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent for index segment in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01655, 00000, "unable to extend cluster %s.%s by %s in tablespace %s" // *Cause: Failed to allocate an extent for cluster segment in tablespace. // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more // files to the tablespace indicated. 01656, 00000, "max # extents (%s) reached in cluster %s.%s" // *Cause: A cluster tried to extend past maxextents // *Action: If maxextents is less than the system maximum, raise it. Otherwise, // you must recreate with larger initial, next or pctincrease params 01657, 00000, "invalid SHRINK option value" // *Cause: The specified value must be an integer. // *Action: Choose an appropriate integer value. 01658, 00000, "unable to create INITIAL extent for segment in tablespace %s" // *Cause: Failed to find sufficient contiguous space to allocate INITIAL // extent for segment being created. // *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the // tablespace or retry with a smaller value for INITIAL 01659, 00000, "unable to allocate MINEXTENTS beyond %s in tablespace %s" // *Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS // for the segment being created. // *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the // tablespace or retry with smaller value for MINEXTENTS, NEXT or // PCTINCREASE 01660, 00000, "tablespace '%s' is already permanent" // *Cause: Attempting to make tablespace permanent that is already permanent. // *Action: Leave tablespace permanent. 01661, 00000, "tablespace '%s' is already temporary" // *Cause: Attempting to make tablespace temporary that is already temporary. // *Action: Leave tablespace permanent. 01662, 00000, "tablespace '%s' is non-empty and cannot be made temporary" // *Cause: Tried to convert a non-empty tablespace to a temporary tablespace // *Action: To drop all the objects in the tablespace. 01663, 00000, "the contents of tablespace '%s' is constantly changing" // *Cause: The contents of the tablespace is always changing between PERMANENT // and TEMPORARY. // *Action: To decide what the tablespace contents should be and stay with it. 01664, 00000, "Transaction which has expanded the Sort Segment has aborted" // *Cause: Internal Error. // *Action: Contact Oracle Support. 01665, 00000, "controlfile is not a standby controlfile" // *Cause: Attempting to mount, recover or activate a standby database // without a standby controlfile. // *Action: Create a standby controlfile before attempting to use the database // as a standby database. 01666, 00000, "controlfile is for a standby database" // *Cause: Attempting to mount, recover, or open a standby database without // the appropriate command option to designate a standby database. // *Action: Use the standby option or appropriate commands, or mount with // the primary controlfile. 01667, 00000, "redo log is incompatible with standby database" // *Cause: Recovery of a standby database has encountered redo from the // primary database that does not support the standby database option. // *Action: Change the compatible initialization parameter for the primary // database to be 7.3.0 or greater, open the primary database, and // rebuild the standby database. 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, "controlfile is a backup, cannot make a standby controlfile" // *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, "controlfile may be missing files or have extra ones" // *Cause: Attempting to create a standby control file, but the controlfile // was either recently created via CREATE CONTROLFILE or an incomplete // recovery has been done. Thus the datafiles in the controlfile // and the ones in the data dictionary may not match. // *Action: Open the database, then retry the operation. 01673, 00000, "data file %s has not been identified" // *Cause: This data file was not in the 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 controlfile. // *Action: Find the file and bring it online. If desired it may be taken // offline again. If you intend to drop this file, then taking it // offline with the DROP option will avoid this error. 01674, 00000, "data file %s is an old incarnation rather than current file" // *Cause: Recovery encountered redo that indicates this file was dropped // from the database and another file was added using the same file // number. This implies that a CREATE CONTROLFILE command was given // the old file which was dropped rather than the latest file. // *Action: Rebuild the controlfile using CREATE CONTROLFILE, and give the // correct file. /01675, 00000, UNUSED: please recycle! // *Cause: // *Action: 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 two strings, a pattern and a replacement" // *Cause: The initialization parameter does not have 2 strings for its value. // The first string it a pattern to be found in file names. The second // string is used to replace the pattern when found in file names. // *Action:Specify two strings for the parameter, or omit the parameter. 01679, 00000, "database must be mounted EXCLUSIVE and not open to activate" // *Cause: An attempt to activate a standby database was made when the // database was not mounted EXCLUSIVE or was already open. // *Action: Mount the database EXCLUSIVE and retry the ACTIVATE command. 01680, 00000, "gc_db_locks cannot be zero if gc_files_to_locks is used" // *Cause: Setting gc_db_locks to zero makes data blocks in all files // releasable, so specifying gc_files_to_locks is redundant. // *Action: Remove either gc_db_locks or gc_files_to_locks. / / 1700 - 1799 Parse errors continued from 900 - 999 / 01700, 00000, "duplicate username in list" // *Cause: // *Action: 01701, 00000, "a cluster is not appropriate here" // *Cause: // *Action: 01702, 00000, "a view is not appropriate here" // *Cause: // *Action: 01703, 00000, "missing SYNONYM keyword" // *Cause: // *Action: 01704, 00000, "string literal too long" // *Cause: The string literal is longer than 2000 characters. // *Action: Use a string literal of at most 2000 characters. // Longer values may only be entered using bind variables. 01705, 00000, "an outer join cannot be specified on a correlation column" // *Cause: // *Action: 01706, 00000, "user function result value was too large" // *Cause: // *Action: 01707, 00000, "missing LIST keyword" // *Cause: // *Action: 01708, 00000, "ACCESS or SESSION expected" // *Cause: // *Action: 01709, 00000, "program does not exist" // *Cause: // *Action: 01710, 00000, "missing OF keyword" // *Cause: // *Action: 01711, 00000, "duplicate privilege listed" // *Cause: // *Action: 01712, 00000, "you cannot grant a privilege which you do not have" // *Cause: // *Action: 01713, 00000, "GRANT OPTION does not exist for that privilege" // *Cause: // *Action: 01714, 00000, "error in execution of user function" // *Cause: // *Action: 01715, 00000, "UNIQUE may not be used with a cluster index" // *Cause: An attempt was made to create a cluster index with the // UNIQUE attribute. // *Action: Remove UNIQUE from the CREATE INDEX statement. 01716, 00000, "NOSORT may not be used with a cluster index" // *Cause: An attempt was made to create a cluster index using // the NOSORT option. // *Action: Remove NOSORT from the CREATE INDEX statement. 01717, 00000, "seccta: invalid access mode token passed" // *Cause: // *Action: 01718, 00000, "BY ACCESS | SESSION clause not allowed for NOAUDIT" // *Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement. // *Action: Remove BY ACCESS | SESSION. 01719, 00000, "outer join operator (+) not allowed in operand of OR or IN" // *Cause: An outer join appears in an or clause. // *Action: If A and B are predicates, to get the effect of (A(+) or B), // try (select where (A(+) and not B)) union all (select where (B)). 01720, 00000, "grant option does not exist for '%s.%s'" // *Cause: A grant was being performed on a view and the grant option was // not present for an underlying object. // *Action: Obtain the grant option on all underlying objects of the view. 01721, 00000, "USERENV(COMMITSCN) invoked more than once in a transaction" // *Cause: The USERENV('COMMITSCN') function can only be used once in a // transaction. // *Action: Re-write the transactioin to use USERENV('COMMITSCN') only once 01722, 00000, "invalid number" // *Cause: // *Action: 01723, 00000, "zero-length columns are not allowed" // *Cause: // *Action: 01724, 00000, "floating point precision is out of range (1 to 126)" // *Cause: Self-evident. // *Action: Self-evident. 01725, 00000, "USERENV('COMMITSCN') not allowed here" // *Cause: The function USERNEV('COMMMITSCN') is only allowed as a top-level // expression in the VALUES clause of an INSERT statements, and on // the right hand side of an assignment in an UPDATE statement. // *Action: Correct the use of the function. 01726, 00000, "a table is not appropriate here" // *Cause: // *Action: 01727, 00000, "numeric precision specifier is out of range (1 to 38)" // *Cause: // *Action: 01728, 00000, "numeric scale specifier is out of range (-84 to 127)" // *Cause: // *Action: 01729, 00000, "database link name expected" // *Cause: // *Action: 01730, 00000, "invalid number of column names specified" // *Cause: // *Action: 01731, 00000, "circular view definition encountered" // *Cause: // *Action: 01732, 00000, "data manipulation operation not legal on this view" // *Cause: // *Action: 01733, 00000, "virtual column not allowed here" // *Cause: // *Action: 01734, 00000, "illegal parameters - EXTENT MIN higher than EXTENT MAX" // *Cause: A wrong value is specified for the parameter. // *Action: Correct the parameter and reissue the statement. 01735, 00000, "invalid ALTER TABLE option" // *Cause: // *Action: 01736, 00000, "[NOT] SUCCESSFUL expected" // *Cause: // *Action: 01737, 00000, "valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE" // *Cause: // *Action: Valid lock modes are SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, // SHARE ROW EXCLUSIVE, and SHARE UPDATE. 01738, 00000, "missing IN keyword" // *Cause: // *Action: 01739, 00000, "missing MODE keyword" // *Cause: // *Action: 01740, 00000, "missing double quote in identifier" // *Cause: // *Action: 01741, 00000, "illegal zero-length identifier" // *Cause: // *Action: 01742, 00000, "comment not terminated properly" // *Cause: The indicated comment or hint begun with the /* token did not // have the terminating */. // *Action: Properly terminate the comment or hint with a */. 01743, 00000, "internal inconsistency; illegal user function index" // *Cause: // *Action: 01744, 00000, "inappropriate INTO" // *Cause: // *Action: 01745, 00000, "invalid host/bind variable name" // *Cause: // *Action: 01746, 00000, "indicator variable not permitted here" // *Cause: // *Action: 01747, 00000, "invalid user.table.column, table.column, or column specification" // *Cause: // *Action: 01748, 00000, "only simple column names allowed here" // *Cause: // *Action: 01749, 00000, "you may not GRANT/REVOKE privileges to/from yourself" // *Cause: // *Action: 01750, 00000, "UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column" // *Cause: // *Action: 01751, 00000, "Invalid dump undo option" // *Cause: An invalid option is specified in the ALTER DUMP UNDO command. // *Action: Correct and reissue the command. 01752, 00000, "cannot delete from view without exactly one key-preserved table" // *Cause: The deleted table either had no key perserved tables, // had more than one key-preserved table, or the key-preserved // table was an unmerged view or a table from a read-only view. // *Action: Redefine the view or delete it from the underlying base tables. 01753, 00000, "column definition incompatible with clustered column definition" // *Cause: // *Action: 01754, 00000, "a table may contain only one column of type LONG" // *Cause: // *Action: 01755, 00000, "Must specify an extent number or block number" // *Cause: Expecting an extent or block number but something else was // specified. // *Action: Correct the error and reissue the command. 01756, 00000, "quoted string not properly terminated" // *Cause: // *Action: 01757, 00000, "Must specify an object number" // *Cause: Expecting an object number but something else was specified. // *Action: Correct the error and reissue the command. 01758, 00000, "table must be empty to add mandatory (NOT NULL) column" // *Cause: // *Action: 01759, 00000, "user function is incorrectly defined" // *Cause: // *Action: 01760, 00000, "illegal argument for function" // *Cause: // *Action: 01761, 00000, "DML operation does not map to a unique table in the join" // *Cause: The primary table is the base table against which the update, // insert or delete operation is finally being done. For delete // either there is no primary table in the join query or there is // more than one. For update or insert the columns specified map // to more than one base table. // *Action: Change the join specification. 01762, 00000, "vopdrv: view query block not in FROM" // *Cause: // *Action: 01763, 00000, "update or delete involves outer joined table" // *Cause: For deletes, the table being deleted from is outer joined to some // other table. For updates, either the table being updated is outer- // joined to some other table, or some table reachable from the primary // table is being outer joined to a table not reachable from the // primary table. // *Action: Change the join specification. 01764, 00000, "new update value of join is not guaranteed to be unique" // *Cause: A row of a join query table is being updated using a row of a // table that is not guaranteed to have exactly one value for the // row being updated. // *Action: Change the join specification. 01765, 00000, "specifying table's owner name is not allowed" // *Cause: // *Action: 01766, 00000, "dictionary table not allowed in this context" // *Cause: // *Action: 01767, 00000, "UPDATE ... SET expression must be a subquery" // *Cause: // *Action: 01768, 00000, "number string too long" // *Cause: // *Action: 01769, 00000, "duplicate CLUSTER option specifications" // *Cause: During a CREATE of a clustered table, the user attempted to specify // more than one CLUSTER option. // *Action: Remove the extra CLUSTER option. 01770, 00000, "CLUSTER option not allowed in CREATE CLUSTER command" // *Cause: // *Action: 01771, 00000, "illegal option for a clustered table" // *Cause: During a CREATE or ALTER of a clustered table, the user attempted // to enter one or more of the following options: // INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE. // These options may only be specified for the cluster itself. // *Action: Remove the illegal option(s). 01772, 00000, "Must specify a value for LEVEL" // *Cause: Expecting the value of LEVEL but something else was specified. // *Action: Correct the error and reissue the command. 01773, 00000, "may not specify column datatypes in this CREATE TABLE" // *Cause: // *Action: 01774, 00000, "Dump undo option specified more than once" // *Cause: The same option for ALTER DUMP UNDO was specified twice. // *Action: Remove the redundant options and reissue the command. 01775, 00000, "looping chain of synonyms" // *Cause: // *Action: 01776, 00000, "cannot modify more than one base table through a join view" // *Cause: Columns belonging to more than one underlying table were either // inserted into or updated. // *Action: Phrase the statement as two or more separate statements. 01777, 00000, "WITH GRANT OPTION not allowed in this system" // *Cause: // *Action: 01778, 00000, "maximum subquery nesting level exceeded" // *Cause: // *Action: 01779, 00000, "cannot modify a column which maps to a non key-preserved table" // *Cause: An attempt was made to insert or update columns of a join view which // map to a non-key-preserved table. // *Action: Modify the underlying base tables directly. 01780, 00000, "string literal required" // *Cause: // *Action: / 01781, 00000, "UNRECOVERABLE cannot be specified without AS SELECT" // *Cause: UNRECOVERABLE was specified in a CREATE TABLE statement // without also specifying a populating subquery with an AS clause. // *Action: Do not specify UNRECOVERABLE. / 01782, 00000, "UNRECOVERABLE cannot be specified for a cluster or clustered table" // *Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement // specified UNRECOVERABLE. // *Action: Do not specify UNRECOVERABLE. / 01783, 00000, "only one RECOVERABLE or UNRECOVERABLE clause may be specified" // *Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified // more than once, or both RECOVERABLE and UNRECOVERABLE were specified // in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement. // *Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and // reissue the statement. / 01784, 00000, "RECOVERABLE cannot be specified with database media recovery disabled" // *Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE // when the database was running in NOARCHIVELOG mode. Since logs // are not being archived, they will be overwritten and the object // being created cannot be recovered from a backup taken before the // object was created. // *Action: Do not specify RECOVERABLE, or restart the database with media // recovery enabled. / 01785, 00000, "ORDER BY item must be the number of a SELECT-list expression" // *Cause: // *Action: 01786, 00000, "FOR UPDATE of this query expression is not allowed" // *Cause: // *Action: 01787, 00000, "only one clause allowed per query block" // *Cause: // *Action: 01788, 00000, "CONNECT BY clause required in this query block" // *Cause: // *Action: 01789, 00000, "query block has incorrect number of result columns" // *Cause: // *Action: 01790, 00000, "expression must have same datatype as corresponding expression" // *Cause: // *Action: 01791, 00000, "not a SELECTed expression" // *Cause: // *Action: 01792, 00000, "maximum number of columns in a table or view is 254" // *Cause: // *Action: 01793, 00000, "maximum number of index columns is 16" // *Cause: // *Action: 01794, 00000, "maximum number of cluster columns is 16" // *Cause: // *Action: 01795, 00000, "maximum number of expressions in a list is 254" // *Cause: // *Action: 01796, 00000, "this operator cannot be used with lists" // *Cause: // *Action: 01797, 00000, "this operator must be followed by ANY or ALL" // *Cause: // *Action: 01798, 00000, "missing EXCEPTION keyword" // *Cause: // *Action: 01799, 00000, "a column may not be outer-joined to a subquery" // *Cause: (+) () is not allowed. // *Action: Either remove the (+) or make a view out of the subquery. // In V6 and before, the (+) was just ignored in this case. / / parse errors continued at 2000 / / 1800 - 1899 Date function errors / 1800 - 1809 Overflow conditions / 01800, 00000, "a literal in the date format was too large to process" // *Cause: // *Action: 01801, 00000, "date format is too long for internal buffer" // *Cause: // *Action: 01802, 00000, "Julian date is out of range" // *Cause: // *Action: 01803, 00000, "failure in getting date/time" // *Cause: // *Action: / / 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: / / 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 +4713" // *Cause: // *Action: 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, "wrong number of digits for this format item" // *Cause: The number of digits used for this format item is not equal // to the number necessary for this format when specifying // Format eXact ("FX") for this item. // *Action: Fill out this format item with leading zeros to the number // necessary for this format. (This is generally the number of // characters in the format code--DD needs 2 digits, for // example. The exceptions are HH24 & HH12, which // both need 2, and J, which needs 9.) 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 expected" // *Cause: An expected keyword was not used. // *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. 01931, 00000, "cannot grant %s to a role" // *Cause: UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER // privilege cannot be granted to a role. // *Action: Grant privilege directly to the user. 01932, 00000, "ADMIN option not granted for role '%s'" // *Cause: The operation requires the admin option on the role. // *Action: Obtain the grant option and re-try. 01933, 00000, "cannot create a stored object using privileges from a role" // *Cause: An attempt was made to create a stored object using privileges // from a role. Stored objects cannot use privileges from roles. // *Action: Grant the privileges required to the user directly. 01934, 00000, "circular role grant detected" // *Cause: Roles cannot be granted circularly. Also, a role cannot be // granted to itself. // *Action: Do not perform the grant. 01935, 00000, "missing user or role name" // *Cause: A user or role name was expected. // *Action: Specify a user or role name. 01936, 00000, "cannot specify owner when creating users or roles" // *Cause: Users and roles do not have owners. // *Action: Don't specify an owner. 01937, 00000, "missing or invalid role name" // *Cause: A valid role name was expected. // *Action: Specify a valid role name. 01938, 00000, "IDENTIFIED BY must be specified for CREATE USER" // *Cause: Cannot create a user without specifying a password or // "IDENTIFIED EXTERNALLY". // *Action: Specify one of the password clauses. 01939, 00000, "only the ADMIN OPTION can be specified" // *Cause: System privileges and Roles can only be granted with the admin // option. The grant option cannot be used with these privileges. // *Action: Specify the admin option. 01940, 00000, "cannot drop a user that is currently connected" // *Cause: Attempt was made to drop a user that is currently logged in. // *Action: Make sure user is logged off, then repeat command. 01941, 00000, "SEQUENCE keyword expected" // MERGE: 1917 RENUMBERED TO 1941 // *Cause: keyword missing // *Action: supply missing keyword 01942, 00000, "IDENTIFIED BY and EXTERNALLY cannot both be specified" // *Cause: A user cannot be specified to have and not have a password. // *Action: Specify only one of the options. 01943, 00000, "IDENTIFIED BY already specified" // *Cause: The identified clause has been given twice. // *Action: Use only one identified by clause. 01944, 00000, "IDENTIFIED EXTERNALLY already specified" // *Cause: The identified externaly clause has been given twice. // *Action: Use only one identified clause. 01945, 00000, "DEFAULT ROLE[S] already specified" // *Cause: The default roles clause has been given twice. // *Action: Use only on default role clause. 01946, 00000, "DEFAULT TABLESPACE already specified" // *Cause: The default tablespace clause has been given twice. // *Action: Use only one default tablespace clause. 01947, 00000, "TEMPORARY TABLESPACE already specified" // *Cause: The temporary tablespace clause has been given twice. // *Action: Use only one temporary tablespace clause. 01949, 00000, "ROLE keyword expected" // *Cause: The role keyword is required here. // *Action: Specify the role keyword. 01950, 00000, "no privileges on tablespace '%s'" // *Cause: User does not have privileges to allocate an extent in the // specified tablespace. // *Action: Grant the user the appropriate system privileges or grant the user // space resource on the tablespace. 01951, 00000, "ROLE '%s' not granted to '%s'" // *Cause: The role you tried to revoke was not granted to the user. // *Action: Don't try to revoke a privilege which is not granted. 01952, 00000, "system privileges not granted to '%s'" // *Cause: A system privilege you tried to revoke was not granted to the user. // *Action: Make sure the privileges you are trying to revoke are granted. 01953, 00000, "command no longer valid, see ALTER USER" // *Cause: The syntax for assigning quotas on tablespaces has changed. The // ALTER USER command is now used to perform the functionality // *Action: Use the alter user command instead. 01954, 00000, "DEFAULT ROLE clause not valid for CREATE USER" // *Cause: Default roles cannot be specified for create user. // *Action: Grant and alter the user's default roles after creating the user. 01955, 00000, "DEFAULT ROLE '%s' not granted to user" // *Cause: The user being altered does not have the specified role granted // directly to the user. Note, sub-roles cannot be used in the // default role clause. // *Action: Grant the role to the user. 01956, 00000, "invalid command when OS_ROLES are being used" // *Cause: This command cannot be used when the init.ora parameter OS_ROLES // is TRUE. // *Action: Grant the role to the user in the operating system. 01957, 00000, "Keyword MIN or MAX expected, not found" // *Cause: // *Action: 01958, 00000, "Must supply an integer for the LAYER option" // *Cause: // *Action: 01959, 00000, "Must supply an integer for the OPCODE option" // *Cause: // *Action: 01960, 00000, "Invalid dump logfile option" // *Cause: // *Action: 01961, 00000, "Invalid dump option" // *Cause: // *Action: 01962, 00000, "Must specify a file number or log sequence number" // *Cause: // *Action: 01963, 00000, "Must specify a block number" // *Cause: // *Action: 01964, 00000, "Must specify a time for the TIME option" // *Cause: // *Action: 01965, 00000, "Must specify a PERIOD" // *Cause: // *Action: 01967, 00000, "invalid option for CREATE CONTROLFILE" // *Cause: An invalid CREATE CONTROLFILE option is present. // *Action: Specify only valid CREATE CONTROLFILE options. 01968, 00000, "Only specify RESETLOGS or NORESETLOGS once" // *Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once // *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. 01969, 00000, "You must specify RESETLOGS or NORESETLOGS" // *Cause: Missing a RESETLOGS or a NORESETLOGS // *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. 01970, 00000, "You must specify a database name for CREATE CONTROLFILE" // *Cause: Missing a database name // *Action: Retype CREATE CONTROLFILE command with the DATABASE keyword. 01971, 00000, "Illegal ALTER TRACING option" // *Cause: // *Action: 01972, 00000, "Must specify a string for ALTER TRACING ENABLE or DISABLE" // *Cause: // *Action: 01973, 00000, "Missing change number" // *Cause: Keyword "CHANGE" found but change number not specified. // *Action: Fix command line and resubmit 01974, 00000, "Illegal archive option" // *Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command // *Action: 01975, 00000, "Illegal character in change number %s" // *Cause: // *Action: 01976, 00000, "Missing change number" // *Cause: // *Action: 01977, 00000, "Missing thread number" // *Cause: Keyword "THREAD" found but thread number not specified. // *Action: Fix command line and resubmit 01978, 00000, "Missing sequence number" // *Cause: Keyword "SEQUENCE" found but sequence number not specified. // *Action: Fix command line and resubmit 01979, 00000, "missing or invalid password for role '%s'" // *Cause: An attempt was made to enable a role without giving / the proper password. // *Action: Use the "identified by" clause in set role to specify // the correct password. 01980, 00000, "error during OS ROLE initialization" // *Cause: An OS error occurred while loading a users OS ROLES. // *Action: Check the OS error. 01981, 00000, "CASCADE CONSTRAINTS must be specified to perform this revoke" // *Cause: During this revoke some foreign key contraints will be removed. // In order to perform this automatically, CASCADE CONSTRAINTS must // be specified. // *Action: Remove the constraints or specify CASCADE CONSTRAINTS. 01982, 00000, "invalid auditing option for tables" // *Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is // not legal for tables. // *Action: The following options may not be used for tables // and should be removed: REFERENCES, EXECUTE 01983, 00000, "invalid auditing option for DEFAULT" // *Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is // not legal for DEFAULT. // *Action: The following options may not be used for DEFAULT // and should be removed: REFERENCES 01984, 00000, "invalid auditing option for procedures/packages/functions" // *Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is // not legal for procedures, packages, or functions. // *Action: The following options may not be used for procedures, packages, // and functions and should be removed: all but EXECUTE 01985, 00000, "cannot create user as LICENSE_MAX_USERS parameter exceeded" // *Cause: Maximum users in the database license limit exceeded. // *Action: Increase license limit. 01986, 00000, "invalid option for OPTIMIZER_GOAL" // *Cause: An invalid OPTIMIZER_GOAL option is present. // *Action: Check the syntax for OPTIMIZER_GOAL, specify a valid option and // re-execute the statement. 01987, 00000, "client os username is too long" // *Cause: A client's os username is too long for the os logon to succeed. // *Action: Use a shorter os username. 01988, 00000, "remote os logon is not allowed" // *Cause: Remote os login attempted when not allowed. // *Action: Use a local client, or use the remote_os_authent system parameter // to turn on remote os logon. 01989, 00000, "role '%s' not authorized by operating system" // *Cause: The os role does not exist, is not granted to you, or you did not // provide the correct password. // *Action: Re-attempt the SET ROLE with a valid os role and password, if // necessary. 01990, 00000, "error opening password file '%s'" // *Cause: // *Action: 01991, 00000, "invalid password file '%s'" // *Cause: // *Action: 01992, 00000, "error closing password file '%s'" // *Cause: // *Action: 01993, 00000, "error writing password file '%s'" // *Cause: // *Action: 01994, 00000, "GRANT failed: cannot add users to public password file" // *Cause: // *Action: 01995, 00000, "error reading password file '%s'" // *Cause: // *Action: 01996, 00000, "GRANT failed: password file '%s' is full" // *Cause: // *Action: 01997, 00000, "GRANT failed: user '%s' is identified externally" // *Cause: // *Action: 01998, 00000, "REVOKE failed: user SYS always has SYSOPER and SYSDBA" // *Cause: // *Action: 01999, 00000, "password file mode has changed from '%s' to '%s'" // *Cause: // *Action: / / 2000 - 2099 Parse errors continued from 1700 - 1799 / 02000, 00000, "missing %s keyword" 02001, 00000, "user SYS is not permitted to create indexes with freelist groups" // *Cause: user tried to create an index while running with sys authorization. // *Action: 02002, 00000, "error while writing to audit trail" // *Cause: // *Action: 02003, 00000, "invalid USERENV parameter" // *Cause: // *Action: 02004, 00000, "security violation" // *Cause: This error code is never returned to a user. It is used // as a value for column, audit_trail.returncode, to signal that a // security violation occurred. // *Action: None. 02005, 00000, "implicit (-1) length not valid for this bind or define datatype" // *Cause: // *Action: 02006, 00000, "invalid packed decimal format string" // *Cause: // *Action: 02007, 00000, "can't use ALLOCATE or DEALLOCATE options with REBUILD" // *Cause: Allocate or deallocate storage and rebuild index are not compatible. // *Action: Choose one or the other. 02008, 00000, "non-zero scale specified for nonnumeric column" // *Cause: // *Action: 02009, 00000, "the size specified for a file must not be zero" // *Cause: A value of zero was specified in a SIZE or RESIZE clause // of a file specification. // *Action: Use correct syntax, or, if allowed, omit the SIZE or // RESIZE clause. 02010, 00000, "missing host connect string" // *Cause: // *Action: 02011, 00000, "duplicate database link name" // *Cause: // *Action: 02012, 00000, "missing USING keyword" // *Cause: // *Action: 02013, 00000, "missing CONNECT keyword" // *Cause: // *Action: 02014, 00000, "cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc." 02015, 00000, "cannot select FOR UPDATE from remote table" // *Cause: // *Action: 02016, 00000, "cannot use a subquery ina 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 2000 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" // *Cause: An attempt is being made to fetch the rowid pseudo-column from // a fixed table. // *Action: Do not select ROWID from a fixed 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 / 02040, 00000, "remote database %s does not support two-phase commit" // *Cause: the database was potentially updated but does not support prepare // to commit (as determined by its logon transaction traits). The // transaction was rolled back. // *Action: Do not attempt to update the remote database unless it is the // only database updated in one transaction. 02041, 00000, "client database did not begin a transaction" // *Cause: internal error // *Action: contact support 02042, 00000, "too many distributed transactions" // *Cause: the distributed transaction table is full, because too many // distributed transactions are active. // *Action: increase the init.ora "distributed_transactions" or run fewer // transactions. If you are sure you don't have too many concurrent // distributed transactions, this indicates an internal error and support // should be notified. Instance shutdown/restart would be a work-around. 02043, 00000, "must end current transaction before executing %s" // *Cause: a transaction is in progress and one of the following commands // commands is issued: COMMIT FORCE, ROLLBACK FORCE, or // ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode. // *Action: COMMIT or ROLLBACK the current transaction and resubmit // command. 02044, 00000, "transaction manager login denied: transaction in progress" // *Cause: a remote transaction manager tried to log in while a distributed // transaction is in progress. // *Action: end the current transaction (this is a protocol error from a // remote transaction manager) 02045, 00000, "too many local sessions participating in global transaction" // *Cause: too many sessions at this site for this transaction. // *Action: use an existing link so another session need not be created. 02046, 00000, "distributed transaction already begun" // *Cause: internal error or error in external transaction manager. // A server session received a begin_tran RPC before finishing // with a previous distributed tran. 02047, 00000, "cannot join the distributed transaction in progress" // *Cause: Either a transaction is in progress against a remote database // that does not fully support two phase commit, and an update // is attempted on another database, or updates are pending and // and an attempt is made to update a different database that // does not fully support two phase commit. // *Action: complete the current transaction and then resubmit the // update request. 02048, 00000, "attempt to begin distributed transaction without logging on" // *Cause: client program must issue a distributed transaction login. // *Action: contact support. 02049, 00000, "timeout: distributed transaction waiting for lock" // *Cause: exceeded init.ora distributed_lock_timeout seconds waiting for lock. // *Action: treat as a deadlock 02050, 00000, "transaction %s rolled back, some remote DBs may be in-doubt" // *Cause: network or remote failure in 2PC. // *Action: Notify operations; remote DBs will automatically re-sync when the // failure is repaired. 02051, 00000, "another session in same transaction failed" // *Cause: a session at the same site with same global transaction id failed. // *Action: none necessary, transaction automatically recovered. 02052, 00000, "remote transaction failure at %s" // *Cause: error in remote transaction at given DBLINK // *Action: retry 02053, 00000, "transaction %s committed, some remote DBs may be in-doubt" // *Cause: network or remote failure in 2PC. // *Action: Notify operations; remote DBs will automatically re-sync when the // failure is repaired. 02054, 00000, "transaction %s in-doubt" // *Cause: network or remote failure in 2PC. // *Action: Notify operations; DBs will automatically re-sync when the // failure is repaired. Monitor pending_trans$ for final outcome. 02055, 00000, "distributed update operation failed; rollback required" // *Cause: a failure during distributed update operation may not have // rolled back all effects of the operation. Since // some sites may be inconsistent, the transaction must roll back to // a savepoint or entirely // *Action: rollback to a savepoint or rollback transaction and resubmit 02056, 00000, "2PC: %s: bad two-phase command number %s from %s" // *Cause: two-phase commit protocol error. // *Action: recovery of transaction attempted. Monitor pending_trans$ table to // ensure correct resolution. Contact support. 02057, 00000, "2PC: %s: bad two-phase recovery state number %s from %s" // *Cause: internal error in two-phase recovery protocol // *Action: contact support 02058, 00000, "no prepared transaction found with ID %s" // *Cause: no transaction with local_tran_id or global_tran_id found in the // pending_trans$ table in prepared state. // *Action: check the pending_trans$ table. 02059, 00000, "ORA-2PC-CRASH-TEST-%s in commit comment" // *Cause: This is a special comment used to test the two phase commit. // *Action: Don't use this special comment (%s a number 1-10) 02060, 00000, "select for update specified a join of distributed tables" // *Cause: tables in a join with the for update clause must reside at the // same DB. 02061, 00000, "lock table specified list of distributed tables" // *Cause: tables in a lock table statement must reside at the same DB. // *Action: issue multiple lock table commands. 02062, 00000, "distributed recovery received DBID %s, expected %s" // *Cause: a database link at a coordinator no longer points to the expected // database. Link may have been redefined, or a different DB mounted. // *Action: restore link definition or remote database. 02063, 00000, "preceding %s%s from %s%s" // *Cause: an Oracle error was received from a remote database link. // *Action: refer to the preceding error message(s) 02064, 00000, "distributed operation not supported" // *Cause: One of the following unsupported operations was attempted: // 1. array execute of a remote update with a subquery that references // a dblink, or // 2. an update of a long column with bind variable and an update of // a second column with a subquery that both references a dblink // and a bind variable, or // 3. a commit is issued in a coordinated session from an RPC with // OUT parameters. // *Action: simplify remote update statement 02065, 00000, "illegal option for ALTER SYSTEM" // *Cause: The option specified for ALTER SYSTEM is not supported // *Action: refer to the user manual for option supported 02066, 00000, "missing or invalid MTS_DISPATCHERS text" // *Cause: A character string literal was expected, but not found, following // ALTER SYSTEM SET MTS_DISPATCHERS // *Action: place the string literal containing the dispatcher's specification // after ALTER SYSTEM SET MTS_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, "unused error" // *Cause: // *Action: 02076, 00000, "sequence not co-located with updated table or long column" // *Cause: all referenced sequences must be co-located with the table // with the long column. // 02077, 00000, "selects of long columns must be from co-located tables" // *Cause: if a select returns long columns from multiple tables, all the // tables must be co-located // 02078, 00000, "invalid setting for ALTER SYSTEM FIXED_DATE" // *Cause: // *Action: // 02079, 00000, "no new sessions may join a committing distributed transaction" // *Cause: A call to UPI2BG was issued in a session for a transaction that // has begun to commit in a different branch; that is, a call to // upi2en was issued for a branch of the same transaction in another // session. This can only happen when using an external transaction // manager. // *Action: Contact support. // 02080, 00000, "database link is in use" // *Cause: a transaction is active or a cursor is open on the database link // given in the alter session close database link command. // *Action: commit or rollback, and close all cursors // 02081, 00000, "database link is not open" // *Cause: dblink given is not currently open. // 02082, 00000, "a loopback database link must have a connection qualifier" // *Cause: attempt to create a database link with the same name as the // current database. // *Action: a loopback database link needs a trailing qualifier, e.g. // MYDB.DEV.US.ORACLE.COM@INST1 - the '@INST1' is the qualifier // 02083, 00000, "database name has illegal character '%s'" // *Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' // '.' and '@' characters. // 02084, 00000, "database name is missing a component" // *Cause: supplied database name cannot contain a leading '.', // trailing '.' or '@', or two '.' or '@' in a row. // 02085, 00000, "database link %s connects to %s" // *Cause: a database link connected to a database with a different name. // The connection is rejected. // *Action: create a database link with the same name as the database it // connects to, or set global_names=false. // 02086, 00000, "database (link) name is too long" // *Cause: database/database link name can have at most 128 characters. 02087, 00000, "object locked by another process in same transaction" // *Cause: A database link is being used in the parallel server 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 // snapshots, deferred RPCs, and other replication features were, // therefore, unavailable. // *Action: Install the replication option. The replication option is not // part of the Oracle7 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, "unable to modify specified parameter" // *Cause: Though the initialization parameter is modifiable, it could not // use the supplied value. // *Action: Validate the supplied value and make sure it falls withing the // range of values accepted by 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" // / / 2100 .. 2139 - Reserved for precompiler runtime (SQLLIB) / 02100, 00000, "PCC: out of memory (i.e., could not allocate)" 02101, 00000, "PCC: inconsistent cursor cache (uce/cuc mismatch)" 02102, 00000, "PCC: inconsistent cursor cache (no cuc entry for this uce)" 02103, 00000, "PCC: inconsistent cursor cache (out-of-range cuc ref)" 02104, 00000, "PCC: inconsistent host cache (no cuc available)" 02105, 00000, "PCC: inconsistent cursor cache (no cuc entry in cache)" 02106, 00000, "PCC: inconsistent cursor cache (OraCursor nr is bad)" 02107, 00000, "PCC: this pgm too old for run-time library: please re-PCC it" 02108, 00000, "PCC: invalid descriptor passed to run-time library" 02109, 00000, "PCC: inconsistent host cache (out-of-range sit ref)" 02110, 00000, "PCC: inconsistent host cache (invalid sqi type)" 02111, 00000, "PCC: heap consistency error" 02112, 00000, "PCC: SELECT..INTO returns too many rows" / / 2140 .. 2499 - V6 parser errors continued / parser errors continued at 25000 / 02140, 00000, "invalid tablespace name" // *Cause: An identifier does not follow ALTER TABLESPACE. // *Action: Specify a tablespace name following ALTER TABLESPACE. 02141, 00000, "invalid OFFLINE option" // *Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE. // *Action: The user must either specify no option following OFFLINE or // one of the options NORMAL or IMMEDIATE. 02142, 00000, "missing or invalid ALTER TABLESPACE option" // *Cause: A valid option is not present. // *Action: Use one of the valid options: add, rename, default, online, // offline, read only, read write, begin, and end. 02143, 00000, "invalid STORAGE option" // *Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or // PCTINCREASE was specified in the STORAGE clause. // *Action: Specify only valid options. 02144, 00000, "no option specified for ALTER CLUSTER" // *Cause: No ALTER CLUSTER options are specified. // *Action: Specify one or more of the following options: pctfree, // pctused, size, storage. 02145, 00000, "missing STORAGE option" // *Cause: No STORAGE options were specified following STORAGE ( // *Action: Specify one or more STORAGE option between the // parentheses. 02146, 00000, "SHARED specified multiple times" // *Cause: The SHARED option was specified in a CREATE DATABASE // statement multiple times. // *Action: Only specify the SHARED option once. 02147, 00000, "conflicting SHARED/EXCLUSIVE options" // *Cause: Both the SHARED and EXCLUSIVE options were specified in a // CREATE DATABASE statement. // *Action: Specify SHARED or EXCLUSIVE, but not both. 02148, 00000, "EXCLUSIVE specified multiple times" // *Cause: The EXCLUSIVE option was specified in a CREATE DATABASE // statement multiple times. // *Action: Only specify the EXCLUSIVE option once. 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, or TABLESPACE 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. 02161, 00000, "invalid value for MAXLOGFILES" // *Cause: A number does not follow MAXLOGFILES. // *Action: Specify a number after MAXLOGFILES. 02162, 00000, "invalid value for MAXDATAFILES" // *Cause: A number does not follow MAXDATAFILES. // *Action: Specify a number after MAXDATAFILES. 02163, 00000, "invalid value for FREELIST GROUPS" // *Cause: A number does not follow FREELIST GROUPS. // *Action: Specify a number after FREELIST GROUPS. 02164, 00000, "DATAFILE clause specified more than once" // *Cause: The CREATE DATABASE command contains more than one DATAFILE clause. // *Action: Specify at most one DATAFILE clause. 02165, 00000, "invalid option for CREATE DATABASE" // *Cause: An invalid CREATE DATABASE option is present. // *Action: Specify only valid CREATE DATABASE options. 02166, 00000, "ARCHIVELOG and NOARCHIVELOG specified" // *Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a // CREATE DATABASE statement. // *Action: Specify at most one of these two options. 02167, 00000, "LOGFILE clause specified more than once" // *Cause: The CREATE DATABASE command contains more than one LOGFILE clause. // *Action: Specify at most one LOGFILE clause. 02168, 00000, "invalid value for FREELISTS" // *Cause: A number does not follow FREELISTS // *Action: Specify a number after FREELISTS 02169, 00000, "FREELISTS storage option not allowed" // *Cause: The user attempted to specify the FREELISTS storage // option. This option may only be specified during // create table or create index. // *Action: Remove these options and retry the statement. 02170, 00000, "FREELIST GROUPS storage option not allowed" // *Cause: The user attempted to specify the FREELIST GROUPS storage // option. This option may only be specified during create // table and when allow_freelist_groups init.ora is specified. // *Action: Remove this option and retry the statement or set the // allow_freelist_groups init.ora parameter. 02171, 00000, "invalid value for MAXLOGHISTORY" // *Cause: A number does not follow MAXLOGHISTORY // *Action: Specify a number after MAXLOGHISTORY 02172, 00000, "The PUBLIC keyword is not appropriate for a disable thread" // *Cause: The PUBLIC keyword was specified for a disable. // *Action: Remove the keyword and resubmit. 02173, 00000, "invalid option for DROP TABLESPACE" // *Cause: Either a token other than INCLUDING was found following the // tablespace name or some text was found following INCLUDING CONTENTS. // *Action: Place nothing or only INCLUDING CONTENTS after the tablespace name. 02174, 00000, "Missing required thread number" // *Cause: Must specify thread number after THREAD keyword // *Action: 02175, 00000, "invalid rollback segment name" // *Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier // was not found following ROLLBACK SEGMENT. // *Action: Place the segment name following ROLLBACK SEGMENT. 02176, 00000, "invalid option for CREATE ROLLBACK SEGMENT" // *Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement. // *Action: Specify one of the valid options: TABLESPACE and STORAGE. 02177, 00000, "Missing required group number" // *Cause: Must specify group number after GROUP keyword // *Action: 02178, 00000, "correct syntax is: SET TRANSACTION READ { ONLY | WRITE }" // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02179, 00000, "valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }" // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02180, 00000, "invalid option for CREATE TABLESPACE" // *Cause: An invalid option appears. // *Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, // ONLINE, OFFLINE. 02181, 00000, "invalid option to ROLLBACK WORK" // *Cause: A token other than TO follows ROLLBACK [WORK]. // *Action: Place nothing or TO SAVEPOINT after ROLLBACK [WORK]. 02182, 00000, "savepoint name expected" // *Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT]. // *Action: Place a savepoint name following TO [SAVEPOINT]. 02183, 00000, "valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }" // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02184, 00000, "resource quotas are not allowed in REVOKE" // *Cause: In a revoke statement, a resource quota was specified. // *Action: Specify resource privilege without the quota. 02185, 00000, "a token other than WORK follows COMMIT" // *Cause: A token other than WORK follows COMMIT. // *Action: Place either nothing or WORK after COMMIT. 02186, 00000, "tablespace resource privilege may not appear with other privileges" // *Cause: An attempt was made to grant or revoke a resource quota in the // same statement in which other privileges are granted or revoked. // *Action: Use a separate grant or revoke statement for the resource // quota privilege. 02187, 00000, "invalid quota specification" // *Cause: In a grant or revoke statement, the user attempted to grant // a tablespace quota above the upper limit. // *Action: Grant a smaller tablespace quota. 02189, 00000, "ON required" // *Cause: In a grant or revoke statement, the user specified a tablespace // quota but did not follow it with the ON clause. // *Action: Specify the tablespace on which the quota is to be applied // with the ON clause. 02190, 00000, "keyword TABLES expected" // *Cause: The keyword TABLES is expected following DROP CLUSTER // INCLUDING. // *Action: Place TABLES after INCLUDING. 02191, 00000, "correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT " // *Cause: There is a syntax error in the user's statement. // *Action: Correct the syntax as indicated. 02192, 00000, "PCTINCREASE not allowed for rollback segment storage clauses" // *Cause: pctincrease was specified in a create or alter rollback segment // *Action: reissue statement without the pctincrease clause 02194, 00000, "event specification syntax error %s (minor error %s) near '%s'" // *Cause: There is a syntax error in an event specification. // *Action: Fix the error. 02195, 00000, "Attempt to create %s object in a %s tablespace" // *Cause: The object type is inconsistent with a tablespace contents" // *Action: Create an object in a different tablespace, or change the user // defaults. 02196, 00000, "PERMANENT/TEMPORARY option already specified" // *Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were // specified more than once. 02197, 00000, "file list already specified" // *Cause: In CREATE TABLESPACE, more than one DATAFILE clause was specified. // *Action: Merge the DATAFILE 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 clause" // *Cause: A CREATE TABLESPACE statement has no DATAFILE clause. // *Action: Specify a DATAFILE 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, REFERENCE 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 // REFERENCES 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 privilege is 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 // 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. // *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 SNAPSHOT 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 SNAPSHOT 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, type and size 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, or the // datatype or size of at least one referencing columns is not equal // to the datatype or size of the its referenced column. // *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-%05d 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 drop or truncate a table with unique or // primary keys referenced by foreign keys enabled in another table. // *Action: Before dropping or truncating 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: attempted to insert or update values that do not have corresponding // Parent key values. // *Action: obvious. 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 enable (%s.%s) - check constraint violated" // *Cause: an alter table operation tried to add a check constraint to // a populated table that had nocomplying values. // *Action: Obvious 02294, 00000,"cannot add referential constraint - parent keys not found" // *Cause: an alter table tried to add a referential constraint to a // populated table that had no mathing parent values. // *Action: Obvious 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 enable (%s.%s) - parent keys not found" // *Cause: an alter table enable constraint fialed because the table has // orphaned child records. // *Action: Obvious 02299, 00000,"cannot enable (%s.%s) - duplicate keys found" // *Cause: an alter table enable constraint failed because the table has // duplicate key values. // *Action: Obvious / / 2300 - 2350 Object Database Errors / / / 2351 - 2375 Direct Loader errors / see also range 2476 - 2479 for Parallel Direct Loader errors / 02351, 00000, "Record %s: Rejected - Error on table %s, column %s" // *Cause: The record indicated caused an oracle error on insert. // *Action: Determine the oracle error and correct the record. 02352, 00000, "Direct path connection must be homogeneous" // *Cause: The user-side to kernel-side connection is heterogenous. // *Action: Make the connection be between identical hardware and O/S's. 02353, 00000, "Multibyte character error" // *Cause: Text specified by POSITION or terminated by newlines is invalid. // *Action: Edit the control file or the data file to fix alignment of column. 02354, 00000, "Conversion initialization error occurred on field %s" // *Cause: An error occurred during conversion initialization for a field. // *Action: Internal error. Contact customer supprt. 02355, 00000, "Conversion error occurred on CONSTANT field %s" // *Cause: A CONSTANT field caused an oracle error; all rows will be rejected. // *Action: Determine the oracle error and correct the record. 02356, 00000, "The database is out of space. The load cannot continue" // *Cause: The load was discontinued due to space exhaustion in the database. // *Action: Add space for the specified table. 02357, 00000, "Packed Decimal conversion error" // *Cause: The column could not be converted from packed decimal to character. // *Action: Check the column and make it conform to packed decimal format. 02358, 00000, "Zoned Decimal conversion error" // *Cause: The column could not be converted from packed decimal to character. // *Action: Check the column and make it conform to packed decimal format. 02359, 00000, "Field in data file exceeded maximum specified length" // *Cause: The field is too long for the specified column. // *Action: Shorten the field so that its length is =< the column length. 02360, 00000, "Column not found before end of logical record (use TRAILING NULLCOLS)" // *Cause: A column started after the end of the logical record had been reached. // *Action: Use the TRAILING NULLCOLS option or supply data for the column. 02361, 00000, "Initial enclosing character not found" // *Cause: The initial enclosing character of an enclosed field was not found. // *Action: Supply the character before the start of the field. 02362, 00000, "Logical record ended - second enclosing character not present" // *Cause: The second enclosing character of an enclosed field was not found. // *Action: Supply the character after the end of the field. 02363, 00000, "No terminator found after TERMINATED and ENCLOSED field" // *Cause: No terminator was found after a terminated and enclosed field. // *Action: Supply the character after the end of the field. 02364, 00000, "Record %s: Discarded - failed all WHEN clauses" // *Cause: The record was not loaded because it failed all tables' WHEN clauses" // *Action: none. 02365, 00000, "Index %s was left in Direct Load State due to" // *Cause: The index was not loaded because of the error specified. // *Action: Correct the error, then reload. 02366, 00000, "The following index(es) on table %s were processed:" // *Cause: The table had some indexes which were loaded if there were no errors. // *Action: none. 02367, 00000, "Index %s was loaded." // *Cause: The index was loaded. // *Action: none. 02368, 00000, "Record %s: Discarded - all columns null." // *Cause: The record was not loaded because all tables' columns were null. // *Action: none. 02369, 00000, "Warning: Variable length field was truncated." // *Cause: A variable length field was truncated by the end of the logical // record. // *Action: This is just a warning, but since a variable length field has the // length embedded in the data for each row, you may want to check your data. 02370, 00000, "Record %s - Warning on table %s, column %s" // *Cause: The record indicated caused an warning. // *Action: Determine the warning and correct the record if necessary. 02371, 00000, "Loader must be at least version %s.%s.%s.%s.%s for direct path" // *Cause: The loader being used is incompatible with this version of the // kernel. // *Action: Upgrade your loader to at least the specified version or use the // conventional path. 02372, 00000, "Relative start position > absolute field end position." // *Cause: A field specified as POSITION(*+n:y) had its relative start occur // after the absolute position y. // *Action: Check that you are not missing a delimiter and that the values of // n and y are correct. 02373, 00000, "Error parsing insert statement for table %s." // *Cause: self-evident. // *Action: Check the error given below this one. 02374, 00000, "No more slots for read buffer queue." // *Cause: There are no free read buffers. // *Action: Use the READBUFFERS keyword in the loader to increase the number // of read buffers. / / 2376 - 2399 Resource limit errors / 02376, 00000, "invalid or redundant resource" // *Cause: a create, or alter profile command which names a resource not // yet defined, or try to specify same resource twice. // *Action: define resource first 02377, 00000, "invalid resource limit" // *Cause: specifying limit of 0 // *Action: specify limit > 0 02378, 00000, "duplicate resource name %s" // *Cause: // *Action: 02379, 00000, "profile %s already exists" // *Cause: Try to create a profile which already exist // *Action: 02380, 00000, "profile %s does not exist" // *Cause: Try to assign a user to a non-existant profile // *Action: 02381, 00000, "cannot drop PUBLIC_DEFAULT profile" // *Cause: Try to drop PUBLIC_DEFAULT profile // *Action: 02382, 00000, "profile %s has users assigned, cannot drop without CASCADE" // *Cause: // *Action: 02383, 00000, "illegal cost factor" // *Cause: Negative or UNLIMITED cost for this resourc // *Action: 02390, 00000, "exceeded COMPOSITE_LIMIT, you are being logged off" // *Cause: // *Action: 02391, 00000, "exceeded simultaneous SESSIONS_PER_USER limit" // *Cause: An attempt was made to exceed the maximum number of // concurrent sessions allowed by the SESSION_PER_USER clause // of the user prfile. // *Action: End one or more concurrent sessions or ask the database // administrator to increase the SESSION_PER_USER limit of // the user profile. 02392, 00000, "exceeded session limit on CPU usage, you are being logged off" // *Cause: // *Action: 02393, 00000, "exceeded call limit on CPU usage" // *Cause: // *Action: 02394, 00000, "exceeded session limit on IO usage, you are being logged off" // *Cause: // *Action: 02395, 00000, "exceeded call limit on IO usage" // *Cause: // *Action: 02396, 00000, "exceeded maximum idle time, please connect again" // *Cause: as stated // *Action: 02397, 00000, "exceeded PRIVATE_SGA limit, you are being logged off" // *Cause: Only when using TP monitor // *Action: expand limit 02398, 00000, "exceeded procedure space usage" // *Cause: Stored procedured used up too much space in SYSTEM Tablespace // *Action: Use less stored procedure 02399, 00000, "exceeded maximum connect time, you are being logged off" // *Cause: As stated // *Action: / / 2400 - 2479 EXPLAIN facility errors / 02401, 00000, "cannot EXPLAIN view owned by another user" // *Cause: The view specified in the SQL statement belongs to another user // and cannot be explained. // *Action: Create a view with the same definition that belongs to // current user. 02402, 00000, "PLAN_TABLE not found" // *Cause: The table used by EXPLAIN to store row source information does // not exist in the current schema. // *Action: Create a plan table in the current schema or use the INTO clause // of the statement to put the results of the explain command in an // existing plan table. 02403, 00000, "plan table does not have correct format" // *Cause: The explicit plan table does not have the appropriate field // definitions. // *Action: Redefine the plan table to have the appropriate field definitions. 02404, 00000, "specified plan table not found" // *Cause: The specified plan table does cannot be found. // *Action: Create the specified plan table or use an existing plan table. / / 2420 - 2429 Schema errors / 02420, 00000, "missing schema authorization clause" // *Cause: the AUTHORIZATION clause is missing from a create schema // statement. // *Action: Preceed the schema authorization identifier with the // AUTHORIZATION keyword. 02421, 00000, "missing or invalid schema authorization identifier" // *Cause: the schema name is missing or is incorrect in an authorization // clause of a create schema statement. // *Action: If the name is present, it must be the same as the current // schema. 02422, 00000, "missing or invalid schema element" // *Cause: A statement other than a create table, create view, or grant // privilege appears in a create schema statement. // *Action: Self-evident. 02423, 00000, "schema name does not match schema authorization identifier" // *Cause: a table definition with a schema name prepended to the table // name does not match the schema name provided in the authorization // clause of a create schema statement. // *Action: make sure the schema names match. 02424, 00000, "potential circular view references or unknown referenced tables" // *Cause: the create schema statement contains views that depend on other // views in the containing create schema statement or they contain // references to unknown tables. // *Action: create the dependent views in a separate create schema statement // and make sure all referenced tables are either defined in the // create schema statement or exist outside the statement. 02425, 00000, "create table failed" // *Cause: a create table statement failed in the create schema statement. // *Action: the cause for failure will be presented below this error message. // Follow appropriate action(s) as suggested by the subsequent error // message. 02426, 00000, "privilege grant failed" // *Cause: a grant privilege statement failed inthe create schema statement. // *Action: the cause for failure will be presented below this error message. // Follow appropriate action(s) as suggested by the subsequent error // message. 02427, 00000, "create view failed" // *Cause: a create view statement failed in the create schema statement. // *Action: the cause for failure will be presented below this error message. // Follow appropriate action(s) as suggested by the subsequent error // message. 02428, 00000, "could not add foreign key reference" // *Cause: could not add a foreign key reference because of error in // declaration. Either referenced table does not exist or // table does not have an unique key. // *Action: make sure referenced table exists and/or has unique key 02429, 00000, "cannot drop index used for enforcement of unique/primary key" // *Cause: user attempted to drop an index that is being used as the // enforcement mechanism for unique or primary key. // *Action: drop the constraint instead of the index. / / 2430 - Enable/Disable Constraint Error Messages - continued / 02430, 00000, "cannot enable constraint (%s) - no such constraint" // *Cause: the named constraint does not exist for this table. // *Action: Obvious 02431, 00000, "cannot disable constraint (%s) - no such constraint" // *Cause: the named constraint does not exist for this table. // *Action: Obvious 02432, 00000, "cannot enable primary key - primary key not defined for table" // *Cause: Attempted to enable a primary key that is not defined for the table. // *Action: Need to add a primary key definition for the table. 02433, 00000, "cannot disable primary key - primary key not defined for table" // *Cause: Attempted to disable a primary key tht is not defined for the // table. // *Action: None 02434, 00000, "cannot enable unique(%s) - unique key not defined for table" // *Cause: attempted to enable a unique key that is not defined for the table. // *Action: None 02435, 00000, "cannot disable unique(%s) - unique key not defined for table" // *Cause: attempted to disable a unique key that is not deined for the table. // *Action: None 02436, 00000, "date or system variable wrongly specified in CHECK constraint" // *Cause: An attempt was made to use a date constant or system variable, // such as USER, in a check constraint that was not completely // specified in a CREATE TABLE or ALTER TABLE statement. For // example, a date was specified without the century. // *Action: Completely specify the date constant or system variable. 02437, 00000, "cannot enable (%s.%s) - primary key violated" // *Cause: attempted to enable 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, "Nonunique index exists on unique/primary key constraint" // *Cause: attempted to enable a primary key/unique constraint that has // existing nonunique index on the constraint columns. // *Action: drop the nonunique index on the constraint columns. 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. / / 2450 - 2475 Parse and execution errors for hashed clusters / 02450, 00000, "Invalid hash option - missing keyword IS" // *Cause: Missing IS keyword. // *Action: Specify HASH IS option. 02451, 00000, "duplicate HASHKEYS specification" // *Cause: The HASHKEYS option is specified more than once. // *Action: Only specify the HASHKEYS option once. 02452, 00000, "invalid HASHKEYS option value" // *Cause: The specified HASHKEYS option must be an integer value. // *Action: Specify an appropriate value. 02453, 00000, "duplicate HASH IS specification" // *Cause: The HASH IS option is specified more than once. // *Action: only specify the HASH IS option once. 02454, 00000, "Number of hash keys per block (%s) exceeds maximum of %s" // *Cause: The SIZE argument is too small. // *Action: Increase the SIZE argument. 02455, 00000, "The number of cluster key column must be 1" // *Cause: When specifing the HASH IS option, the number of key columns // must be 1. // *Action: Either do not specify the HASH IS option or reduce the number // of key columns. 02456, 00000, "The HASH IS column specification must be NUMBER(*,0)" // *Cause: The column specification must specify an integer. // *Action: Specify the column definition as type NUMBER(precision, 0). 02457, 00000, "The HASH IS option must specify a valid column" // *Cause: The HASH IS column name is not specified in the cluster // definition. // *Action: Specify a valid column name. 02458, 00000, "HASHKEYS must be specified for a HASH CLUSTER" // *Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER. // *Action: Specify the HASHKEYS option. 02459, 00000, "Hashkey value must be a positive integer" // *Cause: The value of the hash key was not a positive number. // *Action: Specify a positive integer. 02460, 00000, "Inappropriate index operation on a hash cluster" // *Cause: An attempt to create a cluster index was issued on a hash cluster. // *Action: Do not attempt to create such an index. 02461, 00000, "Inappropriate use of the INDEX option" // *Cause: This option is only valid for non hash clusters. // *Action: Do not specify this option. 02462, 00000, "Duplicate INDEX option specified" // *Cause: The INDEX option is specified more than once. // *Action: Only specify the INDEX option once. 02463, 00000, "Duplicate HASH IS option specified" // *Cause: The HASH IS option is specified more than once. // *Action: Only specify the HASH IS option once. 02464, 00000, "Cluster definition can not be both HASH and INDEX" // *Cause: The cluster can either be a hash or indexed cluster - not both" // *Action: Remove either the HASH IS or INDEX options. 02465, 00000, "Inappropriate use of the HASH IS option" // *Cause: This option is only valid for clusters // *Action: Do not specify this option 02466, 00000, "The SIZE option is not allow to be altered for HASH CLUSTERS" // *Cause: The SIZE can not be changed once the hash cluster has been // created. // *Action: Do not specify this option. 02467, 00000, "Column referenced in expression not found in cluster definition" // *Cause: A column in the hash is expression was not present in cluster // definition. // *Action: Recreate the cluster and correct the error in hash expression. 02468, 00000, "Constant or system variable wrongly specified in expression" // *Cause: A constant or system variable was specified in the hash expression. // *Action: Recreate the cluster and correct the error in hash expression. 02469, 00000, "Hash expression does not return an Oracle Number." // *Cause: Result of evaluating hash expression is not an Oracle Number. // *Action: Recreate the cluster and correct the error in hash expression. 02470, 00000, "TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression." // *Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions. // *Action: Recreate the cluster and correct the error in hash expression. 02471, 00000, "SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion." // *Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s. // *Action: Recreate the cluster and remove the offending keywords. 02472, 00000, "PL/SQL functions not allowed in hash expressions" // *Cause: A PL/SQL function was used in the hash expression." // *Action: Recreate the cluster and remove the PL/SQL function. 02473, 00000, "Error while evaluating the cluster's hash expression." // *Cause: An error occurred while evaluating the clusters hash expression. // *Action: Correct the query and retry. 02474, 00000, "Fixed hash area extents used (%s) exceeds maximum allowed (%s)" // *Cause: The number of extents required for creating the fixed hash // area exceeds the maximum number allowed. // *Action: Reduce the number of extents required by increasing the extent // allocation sizes within the STORAGE clause. / / 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 / 02480, 00000, "too many event classes specified for events" // *Cause: Illegal trace enable string // *Action: Enter a legal trace enable control string 02481, 00000, "too many id ranges specified for events" // *Cause: Illegal trace enable string // *Action: Enter a legal trace enable control string 02482, 00000, "Specified an event class but gave no events" // *Cause: Illegal trace enable string // *Action: Enter a legal trace enable control string 02483, 00000, "Illegal ID value specified for events" // *Cause: Illegal trace enable string // *Action: Enter a legal trace enable control string 02485, 00000, "Low ID value is greater than high ID value" // *Cause: Bad file name given in trace_dest init.ora parameter // *Action: 02486, 00000, "Error in file %s. Check trace_dest init.ora parm" // *Cause: Bad file name given in trace_dest init.ora parameter // *Action: 02487, 00000, "Error in writing file name %s. Check trace_dest init.ora parm" // *Cause: Bad file name given in trace_dest init.ora parameter // *Action: 02489, 00000, "trace_block_size (%s) must be divisable by %s" // *Cause: The init.ora parameter trace_block_size was incorrectly set // *Action: Change the init.ora parameter and restart / / 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. 2758, 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. 2759, 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. 2760, 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. 2761, 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. 2762, 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. 2763, 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. 2764, 00000, "Invalid package mode" // *Cause: The mode of the package can only be parallel or duplex. // *Action: See sfa.h for the correct values. 2765, 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. 2766, 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. 2767, 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 2768, 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. 2769, 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. 2770, 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. 2771, 00000, "Illegal request time out value" // *Cause: The number was not a positive number. // *Action: Use a positive number. 2772, 00000, "Invalid maximum server idle time" // *Cause: The time given was not a positive number. // *Action: Use a positive number. 2773, 00000, "Invalid maximum client wait time" // *Cause: The time given was not a positive number. // *Action: Use a positive number. 2774, 00000, "Invalid request list latch time out value" // *Cause: The time given was not a positive number. // *Action: Use a positive number. 2775, 00000, "Invalid request done signal" // *Cause: The signal number was not a positive number. // *Action: Use a positive number. 2776, 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: 2777, 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. 2778, 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. 2779, 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. 2780, 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. 2781, 00000, "Invalid value given for the timing wanted flag" // *Cause: The value given was not TRUE or FALSE. // *Action: 2782, 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. 2783, 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. 2784, 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. 2785, 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. 2786, 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. 2787, 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: 2788, 00000, "Unable to find kernel process pointer in async process array" // *Cause: Internal error - Contact ORACLE support. // *Action: 2789, 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. 2790, 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. 2791, 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. 2792, 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. 2793, 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. 2794, 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. 2795, 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. 2796, 00000, "Done request is not in correct state" // *Cause: A request is not in the right state. // *Action: Internal error - contact ORACLE support. 2797, 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. 2798, 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. 2799, 00000, "Unable to arm signal handler" // *Cause: The arming of a signal handler for the "done" signal failed. // *Action: Internal error - contact ORACLE support. 2800, 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. 2801, 00000, "Operations timed out" // *Cause: Some asynchronous operations timed out in kernel mode. // *Action: Internal error - contact ORACLE support. 2802, 00000, "No idle servers available in parallel mode" // *Cause: Internal error. // *Action: Contact ORACLE support. 2803, 00000, "Retrieval of current time failed" // *Cause: Internal error. // *Action: Contact ORACLE support. 2804, 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. 2805, 00000, "Unable to set handler for SIGTPA" // *Cause: Internal error. // *Action: Contact ORACLE support. 2806, 00000, "Unable to set handler for SIGALRM" // *Cause: Internal error. // *Action: Contact ORACLE support. 2807, 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. 2808, 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. 2809, 00000, "Jump buffer not valid" // *Cause: Internal error. // *Action: Contact ORACLE support. 2810, 00000, "Unable to make temporary file name for memory mapped file" // *Cause: // *Action: 2811, 00000, "Unable to attach shared memory segment" // *Cause: // *Action: 2812, 00000, "Bad attach address" // *Cause: // *Action: 2813, 00000, "Unable to make temporary file name in order to get key" // *Cause: Internal error. // *Action: Contact ORACLE support. 2814, 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. 2815, 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. 2816, 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. 2817, 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. 2818, 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. 2819, 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. 2820, 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. 2821, 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. 2822, 00000, "Invalid block offset" // *Cause: A server was unable to seek to the designated block. // *Action: Check the UNIX error number. 2823, 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. 2824, 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. 2825, 00000, "Request on free list was not free" // *Cause: Internal error. // *Action: Contact ORACLE support. 2826, 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. 2827, 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. 2828, 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. 2829, 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. 2830, 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. 2831, 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. 2832, 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. 2833, 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. 2834, 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. 2835, 00000, "Server unable to send signal to client" // *Cause: Internal error. // *Action: Contact ORACLE support. 2836, 00000, "Unable to create temporary key file" // *Cause: Internal error. // *Action: Contact ORACLE support. 2837, 00000, "Unable to unlink temporary file" // *Cause: Internal error. // *Action: Contact ORACLE support. 2838, 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. 2839, 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. 2840, 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. 2841, 00000, "Server died on start up" // *Cause: A server exited during its initialization process. // *Action: Check the servers' logs for more information. 2842, 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. 2843, 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. 2844, 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. 2845, 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. 2846, 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. 2847, 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. 2848, 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. 2849, 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. 2850, 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. 2851, 00000, "Request list is empty when it should not be" // *Cause: This is an internal problem. // *Action: Contact ORACLE support. 2852, 00000, "Invalid critical-section time out value" // *Cause: The time given was not a positive number. // *Action: Use a positive number. 2853, 00000, "Invalid server list latch time out value" // *Cause: The time given was not a positive number. // *Action: Use a positive number. 2854, 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. 2855, 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 / / 2900 - 2999 Reserved for licensing server errors / / 3000-3099 currently not implemented features / 03001, 00000, "unimplemented feature" // *Cause: This feature is not implemented. // *Action: None. 03002, 00000, "operator not implemented" // *Cause: This is an internal error. // *Action: Contact your customer support representative. 03007, 00000, "obsolete feature" // *Cause: User attempted to use a feature which is no longer supported. // *Action: None. 3008, 00000, "parameter COMPATIBLE >= %s needed for %s" // *Cause: An attempt was made to use a feature for a later Oracle version, // than the setting of the initialization parameter, COMPATIBLE. // *Action: Set COMPATIBLE to the value in the message (or higher), and // retry the command, but be aware that this will limit your // downgrade options. / / 3100-3199 two task interface errors / some of these can eventually convert to internal ercs / 03100, 00000, "communication area cannot be allocated; insufficient memory" // *Cause: // *Action: 03105, 00000, "internal protocol error" // *Cause: // *Action: 03106, 00000, "fatal two-task communication protocol error" // *Cause: // *Action: 03107, 00000, "oranet buffer underflow" // *Cause: // *Action: 03108, 00000, "oranet: ORACLE does not support this interface version" // *Cause: // *Action: 03109, 00000, "oranet buffer overflow" // *Cause: // *Action: 03110, 00000, "oranet: ORACLE does not support this SQL version" // *Cause: // *Action: 03111, 00000, "break received on communication channel" // *Cause: // *Action: 03112, 00000, "a server linked as single-task cannot use SQL*Net" // Cause: A statement containing a SQL*Net connect string was issued to the // single-task server. For example, a database link was used in a // SQL statement. // Action: Do not use SQL*Net connect strings in a single-task environment. 03113, 00000, "end-of-file on communication channel" // *Cause: // *Action: 03114, 00000, "not connected to ORACLE" // *Cause: // *Action: 03115, 00000, "unsupported network datatype or representation" // *Cause: // *Action: 03116, 00000, "invalid buffer length passed to a conversion routine" // *Cause: // *Action: 03117, 00000, "two-task save area overflow" // *Cause: // *Action: 03118, 00000, "two-task coroutine has invalid state" // *Cause: // *Action: 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. / / 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 / 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. / 03274, 00000, "both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified" // *Cause: The DEALLOCATE option and the ALLOCATE option are specified in // the same command. // *Action: Choose one of the options or issue two separate commands. 03275, 00000, "duplicate DEALLOCATE option specification" // *Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX // is specified more than once. // *Action: Specify the option at most once. 03276, 00000, "duplicate ALLOCATE EXTENT option specification" // MERGE: 2376 RENUMBERED TO 3276 // *Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX // is specified more than once. // *Action: Specify the option at most once. 03277, 00000, "invalid SIZE specified" // MERGE: 2377 RENUMBERED TO 3277 // *Cause: The specified value must be an integer. // *Action: Choose an appropriate integer value. 03278, 00000, "duplicate ALLOCATE EXTENT option specification" // MERGE: 2378 RENUMBERED TO 3278 // *Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more // than once. // *Action: Specify each option at most once. 03279, 00000, "invalid INSTANCE specified" // MERGE: 2379 RENUMBERED TO 3279 // *Cause: The specified value is not recognized as a valid instance name. // *Action: Use a valid name. 03280, 00000, "invalid DATAFILE filename specified" // MERGE: 2380 RENUMBERED TO 3280 // *Cause: A character string literal is expected, but not found. // *Action: Specify filenames using character string literals. 03281, 00000, "invalid ALLOCATE EXTENT option" // MERGE: 2381 RENUMBERED TO 3281 // *Cause: An option other than DATAFILE, SIZE or INSTANCE was specified. // *Action: Remove invalid option and retry the command. 03282, 00000, "missing ALLOCATE EXTENT option" // MERGE: 2382 RENUMBERED TO 3282 // *Cause: No ALLOCATE EXTENT options were specified. // *Action: Specified one or more of the following options: // DATAFILE, SIZE or INSTANCE. 03283, 00000, "specified datafile %s does not exist" // MERGE: 2383 RENUMBERED TO 3283 // *Cause: The datafile does not exist // *Action: Retry the option with the correct datafile 03284, 00000, "datafile %s is not a member of tablespace %s" // MERGE: 2384 RENUMBERED TO 3284 // *Cause: The specified datafile does not belong to the tablespace // that the object resides in. // *Action: Retry the option with the correct datafile. 03286, 00000, "ALLOCATE EXTENT not valid for HASH CLUSTERS" // *Cause: The cluster is a hash cluster, and can not use the // allcoate extent option. // Action: 03287, 00000, "invalid FREELIST GROUP specified" // *Cause: The specified FREELIST GROUP number is invalid // *Action: Choose a number between 1 and # freelist groups for this object 03288, 00000, "both FREELIST GROUP and INSTANCE parameters may not be specified" // *Cause: Both FREELIST GROUP and INSTANCE were specified in clause // *Action: Remove one of the two parameters / / 3290 - 3295 Truncate Parse and Execution Errors / 03290, 00000, "Invalid truncate command - missing CLUSTER or TABLE keyword" // *Cause: Invalid object specification given. // *Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE 03291, 00000, "Invalid truncate option - missing STORAGE keyword" // *Cause: Expected STORAGE keyword // *Action: Either specify DROP STORAGE or REUSE STORAGE 03292, 00000, "Table to be truncated is part of a cluster" // *Cause: The table being truncated is a member of a cluster. // *Action: Either use TRUNCATE CLUSTER or DROP TABLE 03293, 00000, "Cluster to be truncated is a HASH CLUSTER" // *Cause: Only INDEX CLUSTERS can be truncated. // *Action: Drop and recreate the HASH CLUSTER instead of using truncate. / / 3296 - 3299 Reserved for Resizeable Datafiles / 03296, 00000, "cannot resize datafile - file %s not found" // *Cause: The specified datafile is not available for resizing. // *Action: Ensure that the datafile name is valid, and if so, ensure the // file is accessible. 03297, 00000, "file contains %s blocks of 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 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 is occurred. // *Action: Retry the operation later. 04028, 00000, "cannot generate diana for object %s%s%s%s%s" // *Cause: Cannot generate diana for an object because of lock conflict. // *Action: Please report this error to your support representative. 04029, 00000, "error ORA-%s occurred when querying %s%s%s" // *Cause: The table or view being queried might be missing. The error // number indicates the error. // *Action: Fix the error. / / 4030-4039 Reserved for Memory Manager errors / 04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)" // *Cause: Operating system process private memory has been exhausted // *Action: 04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\")" // *Cause: More shared memory is needed than was allocated in the shared // pool. // *Action: Either use the dbms_shared_pool package to pin large packages, // reduce your use of shared memory, or increase the amount of // available shared memory by increasing the value of the // init.ora parameter "shared_pool_size". / / 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, or package is not allowed here" // *Cause: Attempt to specify a procedure, function, or package in an // appropriate 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. 04050, 00000, "invalid or missing procedure, function, or package name" // *Cause: The required procedure, function, or package name is invalid // or missing. // *Action: Specify a valid name. 04051, 00000, "user %s cannot use database link %s.%s" // *Cause: During forwarding of a remote object access, an attempt was // made to use a non-existent database link or one owned by // a user other than the logon user or PUBLIC. // *Action: Change your database link structure so that all indirect remote // accesses are done from the same userid that originates the // request. 04052, 00000, "error occurred when looking up remote object %s%s%s%s%s" // *Cause: An error has occurred when trying to look up a remote object. // *Action: Fix the error. Make sure the remote database system has run // KGLR.SQL to create necessary views used for querying/looking up // objects stored in the database. 04053, 00000, "error occurred when validating remote object %s%s%s%s%s" // *Cause: An error has occurred when trying to validate a remote object. // *Action: Fix the error. Make sure the remote database system has run // KGLR.SQL to create necessary views used for querying/looking up // objects stored in the database. 04054, 00000, "database link %s does not exist" // *Cause: During compilation of a PL/SQL block, an attempt was made to use // a non-existent database link. // *Action: Either use a different database link or create the database link. / / 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. // *Action: Fix the errors and/or create referenced objects as necessary. 04064, 00000, "not executed, invalidated %s" // *Cause: Attempt to execute a stored procedure that has // been invalidated. // *Action: Recompile it. 04065, 00000, "not executed, altered or dropped %s" // *Cause: Attempt to execute a stored procedure that has // been altered or dropped thus making it not callable from the // calling procedure. // *Action: Recompile its dependents. 04066, 00000, "non-executable object, %s" // *Cause: Attempt to execute a non-procedure. // *Action: Make sure that a correct name is given. 04067, 00000, "not executed, %s does not exist" // *Cause: Attempt to execute a non-existent stored procedure. // *Action: Make sure that a correct name is given. 04068, 00000, "existing state of packages%s%s%s has been discarded" // *Cause: One of errors 4060 - 4067 when attempt to execute a stored // procedure. // *Action: Try again after proper re-initialization of any application's // state. / / 4070-4099 Reserved for Trigger errors / 04070, 00000, "invalid trigger name" // *Cause: An invalid trigger name was specified. // *Action: Verify that trigger name is not a reserved keyword. 04071, 00000, "missing BEFORE or AFTER keyword" // *Cause: The trigger statement is missing the BEFORE/AFTER clause. // *Action: Specify either BEFORE or AFTER. 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 trigger NEW values in after row triggers" // *Cause: New trigger variables can only be changed in before row 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' 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. / / 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 / / 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 / 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 reg.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 / reg.h file. / 06500, 00000, "PL/SQL: storage error" // *Cause: // *Action: 06501, 00000, "PL/SQL: program error" // *Cause: // *Action: 06502, 00000, "PL/SQL: numeric or value error" // *Cause: // *Action: 06503, 00000, "PL/SQL: Function returned without value" // *Cause: A call to PL/SQL function completed, but no RETURN statement was // executed. // *Action: Rewrite PL/SQL function, making sure that it always returns // a value of a proper type. 06504, 00000, "PL/SQL: Return types of Result Set variables or query do not match" // *Cause: Number and/or types of columns in a query does not match declared // return type of a result set variable, or declared types of two Result // Set variables do not match. // *Action: Change the program statement or declaration. Verify what query the variable // actually refers to during execution. 06508, 00000, "PL/SQL: could not find program unit being called" // *Cause: // *Action: 06509, 00000, "PL/SQL: ICD vector missing for this package" // *Cause: // *Action: 06510, 00000, "PL/SQL: unhandled user-defined exception" // *Cause: A user-defined exception was raised by PL/SQL code, but // not handled. // *Action: Fix the problem causing the exception or write an exception // handler for this condition. Or you may need to contact your // application administrator or DBA. 06511, 00000, "PL/SQL: cursor already open" // *Cause: An attempt was made to open a cursor that was already open. // *Action: Close cursor first before reopening. 06512, 00000, "at %sline %s" // *Cause: Backtrace message as the stack is unwound by unhandled // exceptions. // *Action: Fix the problem causing the exception or write an exception // handler for this condition. Or you may need to contact your // application administrator or DBA. 06513, 00000, "PL/SQL: index for PL/SQL table out of range for host language array" // *Cause: An attempt is being made to copy a PL/SQL table to a host language // array. But an index in the table is either less than one or // greater than the maximum size of the host language array. // When copying PL/SQL tables to host language arrays, the table // entry at index 1 is placed in the first element of the array, the // entry at index 2 is placed in the second element of the array, etc. // If an table entry has not been assigned then the corresponding // element in the host language array is set to null. // *Action: Increase size of host language array, or decrease size of PL/SQL // table. Also make sure that you don't use index values less than 1. // 06514, 00000, "PL/SQL: The remote call cannot be handled by the server" // *Cause: The remote call has parameters that are cursor variables. // This cannot be handled by stored procedures on your server. // *Action: Avoid using cursor variables as parameters for stored procedures // on this server or upgrade your server to a version that supports // this. //-------------------------------------------------------- // 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. // 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. // 06542, 00000, "PL/SQL: execution error" // Currently unused. Reserved for future use. 06543, 00000, "PL/SQL: execution error - execution aborted" // Currently unused. Reserved for future use. // 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. // //-------------------------------------------------------- // 06550, 00000, "line %s, column %s:\n%s" // *Cause: Usually a PL/SQL compilation error. // *Action: 06551, 00000, "PL/SQL: Unhandled exception" // *Cause: // *Action: 06552, 00000, "PL/SQL: %s" // *Cause: // *Action: 06553, 00000, "PLS-%s: %s" // *Cause: // *Action: 06554, 00000, "package DBMS_STANDARD must be created before using PL/SQL" // *Cause: The DBMS specific extensions to PL/SQL's package "STANDARD" // are in package "DBMS_STANDARD". This package must be // created before using PL/SQL. // *Action: Create package "DBMS_STANDARD". The source for this // PL/SQL stored package is provided with the distribution. 06555, 00000, "this name is currently reserved for use by user SYS" // *Cause: You tried to create a package named "STANDARD", // "DBMS_STANDARD" or "DEBUG_IO". These are currently // reserved for use by user SYS. // *Action: Choose another name for your package. 06556, 00000, "the pipe is empty, cannot fulfill the unpack_message request" // *Cause: There are no more items in the pipe. // *Action: Check that the sender and receiver agree on the number and types // of items placed on the pipe. 06557, 00000, "null values are not allowed for any parameters to pipe icd's" // *Cause: Internal error from the dbms_pipe package. // *Action: 06558, 00000, "buffer in dbms_pipe package is full. No more items allowed" // *Cause: The pipe buffer size has been exceeded. // *Action: 06559, 00000, "wrong datatype requested, %s, actual datatype is %s" // *Cause: The sender put different datatype on the pipe than that being // requested (package 'dbms_pipe'). The numbers are: 6 - number, // 9 - char, 12 - date. // *Action: Check that the sender and receiver agree on the number and types // of items placed on the pipe. 06560, 00000, "pos, %s, is negative or larger than the buffer size, %s" // *Cause: Internal error from the dbms_pipe package. // *Action: 06561, 00000, "given statement is not supported by package DBMS_SQL" // *Cause: Attempting to parse an unsupported statement using procedure // PARSE provided by package DBMS_SQL. // *Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, // LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported. 06562, 00000, "type of out argument must match type of column or bind variable" // *Cause: Attempting to get the value of a column or // a bind variable by calling procedure COLUMN_VALUE or // VARIABLE_VALUE of package DBMS_SQL but the type of // the given out argument where to place the value is different // from the type of the column or bind variable that was previously // defined by calling procedure DEFINE_COLUMN (for defining a column) // or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL. // *Action: Pass in an out argument of the correct type when calling // procedure COLUMN_VALUE or VARIABLE_VALUE. The right // type is the type that was provided when defining the column or // binding the bind variable. 06563, 00000, "top level procedure/function specified, cannot have subparts" // *Cause: The name to be resolved was specified with three parts (a.b.c) // but the a.b part resolves to a top level procedure or function // (which don't have nested procedures). This can also happen // with a two-part name, a.b, where a is a synonym for a top // level package or procedure. // *Action: Specify a procedure/function within a package, or a top level // procedure/function. 06564, 00000, "object %s does not exist" // *Cause: The named object could not be found. Either it does not exist // or you do not have permission to access it. // *Action: Create the object or get permission to access it. 06565, 00000, "cannot execute %s from within stored procedure" // *Cause: The named procedure cannot be executed from within a stored // procedure, function or package. This function can only be // used from pl/sql anonymous blocks. // *Action: Remove the procedure from the calling stored procedure. 06566, 00000, "invalid number of rows specified" // *Cause: An invalid number of rows was specified in a call to the // procedure DEFINE_COLUMN in the package DBMS_SQL. For a given // parsed statement in a given cursor, all columns must be // defined to have the same number of rows, so all the calls // to DEFINE_COLUMN must specify the same number of rows. // *Action: Specify a number that matches that for previously defined // columns. 06567, 00000, "invalid number of values specified" // *Cause: An invalid number of values to be bound was specified in a // call to the procedure BIND_VARIABLE in the package DBMS_SQL. // In order to execute a given parsed statement in a given cursor, // the same number of values must have been bound for all bind // variables, so when EXECUTE is called, the latest calls to // BIND_VARIABLE must must have specified the same number of values // to be bound for all bind variables. // *Action: Make sure that the same number of values have been bound for all // of the bind variables. 06568, 00000, "obsolete ICD procedure called" // *Cause: An obsolete ICD procedure was called by a PL/SQL program. // The PL/SQL program was probably written for an eralier release of // RDBMS. // *Action: Make sure that all PL/SQL programs have been upgraded to the latest // release of the RDBMS. This can be accomplished by following // upgrade instructions in the README file, or by running // the catproc.sql script supplied with the RDBMS. / / 06570, 00000, "shared pool object does not exist, cannot be pinned" // *Cause: The specified shared pool shared cursor could not be found, // therefore it cannot be pinned. // *Action: Make sure that a correct shared cursor name is given. Names // are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's // are an 8 digit hex number from the 'address' column of v$sqlarea, // and the D's are a 1 to 10 digit decimal number with an optional // leading sign (from the 'hash_value' column) // *Action: Remove the procedure from the calling stored procedure. / / 6571-6579 Reserved for Plsql functions called from Sql / 06571, 00000, "Function %s does not guarantee not to update database" // *Cause: There are two possible causes for this message: // * A SQL statement references a packaged, PL/SQL function // that does not contain a pragma that prevents the database // from being updated. // * A SQL statement references a stand-alone, PL/SQL function // that contains an instruction to update the database. // *Action: If the referenced function is a packaged, PL/SQL function: // Recreate the PL/SQL function with the required pragma; be // certain to include the 'Write No Database State' (WNDS) // argument in the argument list of the pragma. // If the referenced function is a stand-alone, PL/SQL function: // Do not use the function. 06572, 00000, "Function %s has out arguments" // *Cause: A SQL statement references either a packaged, or a stand-alone, // PL/SQL function that contains an OUT parameter in its argument // list. PL/SQL functions referenced by SQL statements must not // contain the OUT parameter. // *Action: Recreate the PL/SQL function without the OUT parameter in the // argument list. 06573, 00000, "Function %s modifies package state, cannot be used here" // *Cause: There are two possible causes for this message: // * A SQL statement references a packaged, PL/SQL function that // does not contain a pragma containing the 'Write no Package // State' (WNPS). // * A SQL statement references a stand-alone, PL/SQL function // that modifies a package state. A stand-alone, PL/SQL function // referenced by a SQL statement cannot modify a package state. // *Action: If the function is a packaged, PL/SQL function: Recreate // the function and include a pragma containing the 'Write no // Package State' (WNPS). // If the function is a stand-alone, PL/SQL function: Delete // the function from the SQL statement. 06574, 00000, "Function %s references package state, cannot execute remotely" // *Cause: There are two possible causes for this message: // * A remote, packaged function or a remote-mapped, local, // packaged function that does not contain a pragma with the // 'Write no Package State' (WNPS) and 'Read no Package State' // (RNPS) arguments references a package state. // * A remote, stand-alone function or a remote-mapped, local, // stand-alone function contains a reference to a package // state (reads or writes a package variable). // Only local functions that are referenced in a SELECT list, VALUES // clause of an INSERT statement, or SET clause of an UPDATE // statement can modify a package state. // *Action: If the function is a packaged function: Recreate the function // and include a pragma containing the 'Write no Package State' // (WNPS) and 'Read no Package State' (RNPS) arguments. // If the function is a stand-alone function: Do not call the // function. 06575, 00000, "Package or function %s is in an invalid state" // *Cause: A SQL statement references a PL/SQL function that is in an // invalid state. Oracle attempted to compile the function, but // detected errors. // *Action: Check the SQL statement and the PL/SQL function for syntax // errors or incorrectly assigned, or missing, privileges for a // referenced object. / 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) / / 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, "sftget: supplied buffer not big enough to hold entire line." // *Cause: The fgets call read only part of the line because the supplied // buffer was not big enough. // *Action: Internal error. Contact customer support. Additional information // indicates how big the supplied buffer was. 07244, 00000, "ssfccf: create file failed, file size limit reached." // *Cause: An attempt was made to create a file that exceeds the process's file // size limit. // *Action: Run osh to raise the file size limit. 07245, 00000, "sfccf: unable to lseek and write the last block." // *Cause: An attempt was made to move and write to a bad device address. // *Action: Check errno. Possible lack of space on device. 07246, 00000, "sfofi: open error, unable to open database file." // *Cause: sfofi returns an error. // *Action: This is an oracle internal error. 07247, 00000, "sfrfb: read error, unable to read requested block from database file." // *Cause: sfrfb returns an error. // *Action: This is an oracle internal error. 07248, 00000, "sfwfb: write error, unable to write database block." // *Cause: sfwfb returns an error. // *Action: This is an oracle internal error. 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, "soarch: malloc of temporary buffer for file-to-file copy failed." // *Cause: Malloc() failed to allocate buffer for log archiving. // *Action: You have run out of heap space on your machine. 07281, 00000, "soarch: interrupt received." // *Cause: An interrupt was received while archiving the logs. // *Action: Retry operation. 07282, 00000, "soaprd: 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, "soaprd: 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, "soaprd: 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, "soaprd: 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, "soagdi: 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, "soagdi: unsupported device for log archiving." // *Cause: Log archiving to this device is unsupported. // *Action: Try log archiving to a supported device. 07288, 00000, "soabfn: string overflow when constructing filename." // *Cause: The internal buffer is not big enough to hold the fully-qualified // name for archive destination. // *Action: Internal restriction. 07289, 00000, "soafls: write to tape failed." // *Cause: The write system call failed on the tape device. // *Action: Check addition information for the OS error. Verify that the // tape is mounted correctly. 07290, 00000, "soagdi: specified directory for archiving does not exist." // *Cause: The specified pathname is not a directory. // *Action: Verify that the archive destination directory exists. 07292, 00000, "soaotp: tape volume is too small to accommodate the log file." // *Cause: The current tape volume cannot accommodate the entire log file. // *Action: Increase the tape volume size or decrease the size of // the log file. Additional information indicates the size of // the log file and tape volume size. 07293, 00000, "soaotp: cannot open the current tape volume." // *Cause: The open system call failed on the tape device. // *Action: Check additional information for the OS error. 07294, 00000, "soaotp: cannot allocate buffer for tape write." // *Cause: Malloc() failed to allocate buffer for writing to tape. // *Action: You have run out of heap space on your machine. 07295, 00000, "soaotp: cannot find out the status of log file." // *Cause: The stat system call failed to return the status of log file. // *Action: Verify that the log file still exists. Check additional // information for the OS error. 07296, 00000, "soaotp: lseek error, unable to seek to beginning of log file." // *Cause: Lseek failed to seek to the beginning of log file. // *Action: Check additional information for OS error. 07297, 00000, "soaotp: read error, unable to read header block." // *Cause: Read system call returned an error. Unable to read log file. // *Action: Check additional information for OS error. 07298, 00000, "soacls: trying to close a file that has been closed." // *Cause: Trying to close a file with an invalid file descriptor. // *Action: Internal error. Contact customer support. 07299, 00000, "soacls: failed to close the tape device." // *Cause: The close system call failed on the tape device. // *Action: Verify that the tape is still on-line. Check additional // information for OS error. 07300, 00000, "smscre: translation error while expanding ?/dbs/sgadef@.dbf." // *Cause: Failure of sltln(?/dbs/sgadef@.dbf) in smscre. // *Action: Check additional return error for more information. 07301, 00000, "smscre: ?/dbs/sgadef@.dbf file already exists when creating sga." // *Cause: The sgadef file should not exist when trying to create the // SGA. Otherwise a running instance could be clobbered. The error // from sltln is stored in sercose[0]. // *Action: Verify that database is really down, and delete the sgadef // file. This should only happen when system has crashed with the // database up. Cleanin up sgadef files can be done out of /etc/rc. 07302, 00000, "smscre: create failure in creating ?/dbs/sgadef@.dbf." // *Cause: Create() failed when trying to create the sgadef file. // *Action: Verify permissions on $(ORACLE_HOME)/dbs directory. 07303, 00000, "smscre: 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, "smscre: 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, "sms1sg: ftok error in creating sga." // *Cause: the ftok() library call failed in sms1sg(). // *Action: Verify that ?/dbs/sgadef@.dbf file exists. If it does then this is a // possible system failure. Perhaps System V compatibility is // not enabled. 07306, 00000, "sms1sg: shmget error, unable to get a shared memory segment." // *Cause: Error in shmget. The code fails to find a single segment large // enough for the entire SGA, but cannot continue to the next // allocation model because of a fatal error. // *Action: Check errno returned. Verify that enough shared memory is available // on the system to fit the entire SGA. 07307, 00000, "sms1sg: shmat error, unable to attach sga." // *Cause: Failed to attach shared memory segment, after having gotten it. // *Action: Check errno returned. Verify that SGA attach address is valid. 07308, 00000, "smscre: write error when writing ?/dbs/sgadef@.dbf file." // *Cause: Write call failed in smscre. // *Action: Check errno returned. Possibly out of space on device. 07309, 00000, "smscre: close error, unable to close ?/dbs/sgadef@.dbf file." // *Cause: Close system call returned an error. // *Action: Check errno returned. Possible operating system failure. 07310, 00000, "smscre: unable to create sga." // *Cause: All SGA allocation models have been tried, but none succeeded. // *Action: Possible oracle system error. Try reconfiguring the UNIX kernel // to fit the entire SGA into one segment. 07311, 00000, "smsdes: name translation failure 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 from sltln returned as additional error. 07312, 00000, "smsdes: open error, unable to open sgadef.dbf file." // *Cause: Open failed when trying to open sgadef.dbf file. // *Action: Verify errno returned. Verify sgadef.dbf file exists. // Possible permission problem. 07313, 00000, "smsdes: read error, unable to read sgadef.dbf file." // *Cause: Read system call returned an error when attempting to read // ?/dbs/sgadef@.dbf. // *Action: Check errno returned. Sgadef file may be corrupted or // incompatible with oracle version. 07314, 00000, "smsdes: shmctl error when trying to destroy shared memory segment." // *Cause: Shmctl(IPC_RMID) called failed when trying to destroy shared // memory segment. // *Action: Check errno. Verify that shared exist. Possible permission problem. // May be necessary to manually remove segments. 07315, 00000, "smsdes: close error, unable to close sgadef.dbf file." // *Cause: An error occurred in close(), when closing sgadef.dbf file. // *Action: Verify that sgadef.dbf file has been deleted. Possible operating // system error. 07316, 00000, "smsdes: unlink error, unable to destroy sgadef.dbf file." // *Cause: Unlink() error occurred when attempting to destroy sgadef.dbf file. // *Action: Check errno. Verify that sgadef.dbf file has been destroyed. // May require manual cleanup. 07317, 00000, "smsget: translation error when expanding sgadef.dbf filename." // *Cause: Error occurred translating ?/dbs/sgadef@.dbf. // *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. // Check error returned from sltln as additional error. 07318, 00000, "smsget: open error when opening sgadef.dbf file." // *Cause: Unable to open sgadef.dbf file. // *Action: Check errno. Possible permission problem. Verify that // sgadef.dbf file exists. 07319, 00000, "smsget: 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. 07320, 00000, "smsget: shmat error when trying to attach sga." // *Cause: Unable to attach segment. // *Action: Check errno. sercose[0] returns segment id. Verify segment // exists and that permissions are correct. 07321, 00000, "smsget: shmat error, unable to attach segment at requested address." // *Cause: sercose[0] returns segment id. // *Action: Check errno. Possible operating system error. 07322, 00000, "smsget: close error, unable to close sgadef.dbf file." // *Cause: Unable to close sgadef.dbf file. // *Action: Retry. Possible operating system error. 07323, 00000, "smsfre: shmdt error, unable to delete sga." // *Cause: Problem deleting shared segments. // *Action: Retry. Check errno. May require manual cleanup of shared memory // segments. 07324, 00000, "smpall: malloc error while allocating pga." // *Cause: Malloc library routine returned an error. // *Action: Check errno. Possibly out of swap space. 07325, 00000, "smsacx: malloc error when allocating context area." // *Cause: Malloc library routine returned an error. // *Action: Check errno. Possible lack of swap space. 07326, 00000, "smsfre: attempt to free un-mapped sga." // *Cause: Smsfre was called when the SGA was not mapped. // *Action: Oracle internal error. 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. 07328, 00000, "smsmax: cannot guess the maximum size for a segment." // *Cause: Shmget system call returned a fatal error. // *Action: Check errno. // Additional information indicates the SGA model attempted. 07329, 00000, "smscsg: too many shared memory segments." // *Cause: The internal data structure which holds segment information // is full. // *Action: Reconfigure the UNIX kernel to have bigger segments. 07330, 00000, "smsnsg: unable to allocate the fixed portion of the SGA." // *Cause: The fixed portion of the SGA is too big to fit contiguously // into one segment. // *Action: Reconfigure the UNIX kernel to have bigger segments. 07331, 00000, "smsnsg: unable to allocate the variable portion of the SGA." // *Cause: The variable portion of the SGA is too big to fit contiguously // into one segment. // *Action: Reconfigure the UNIX kernel to have bigger segments. 07332, 00000, "smsnsg: unable to allocate redo buffers." // *Cause: Redo block size is too big, preventing each buffer from being // allocated contiguously. // *Action: Reconfigure the UNIX kernel to have bigger segments, or reduce // the value of log_buffer parameter in init.ora. 07333, 00000, "smsnsg: unable to allocate database buffers." // *Cause: database block size is too big, preventing each buffer from being // allocated contiguously. // *Action: Reconfigure the UNIX kernel to have bigger segments, or reduce // the value of db_block_size parameter in init.ora. 07334, 00000, "smsnsg: too many shared memory segments." // *Cause: The internal data structure which holds segment information // is full. // *Action: Reconfigure the UNIX kernel to have bigger segments. 07335, 00000, "smsmat: ftok error in creating sga." // *Cause: the ftok() library call failed in smsmat(). // *Action: Verify that sgadef.dbf file exists. If it does then this is a // possible system failure. Perhaps System V compatibility is not // enabled. Additional information indicates the SGA model attempted. 07336, 00000, "smsmat: 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 to fit the entire SGA. // Additional information indicates the SGA model attempted. 07337, 00000, "smsmat: shmat error, unable to attach sga." // *Cause: Failed to attach shared memory segment, after having gotten it. // *Action: Check errno returned. Verify that SGA attach address is valid. // Additional information indicates the SGA model attempted. 07338, 00000, "smscre: cannot test for existence of the sga file." // *Cause: The access system call returned an error. Possible OS error. // *Action: Check errno returned and the permission on the sga file. 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. 07340, 00000, "sfccf: fstat error, unable to obtain file status." // *Cause: Unable to obtain file status. Further error closing file is // returned as additional information. // *Action: Verify database files exist, and have proper permissions. 07341, 00000, "sfsrd: invalid block number." // *Cause: The block number requested was out of bounds for the file. // Additional information indicates block number. // *Action: Verify block number. 07342, 00000, "sfsrd: lseek error, unable to seek to requested block" // *Cause: Additional information returns block number. // *Action: Check errno. Check block number. 07343, 00000, "sfsrd: read error, unable to read requested block." // *Cause: Read system call returned an error. // *Action: Check errno. Additional information indicates block number. 07344, 00000, "sfsrd: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 07347, 00000, "sfsrd: simulated error for testing purposes." // *Cause: Error generated from internal testing procedures. // *Action: None. 07350, 00000, "sfccf: 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. 07351, 00000, "sfccf: malloc error, unable to allocate write buffer." // *Cause: Malloc library routine returned an error. // *Action: Verify adequate system resources are available. 07352, 00000, "sfccf: create error, unable to create file." // *Cause: Create system call returned an error. Unable to create database file // *Action: Verify filename, and permissions. 07353, 00000, "sfccf: close error, unable to close file." // *Cause: Close system call returned an error. // *Action: Check errno. 07354, 00000, "sfccf: open error, unable to open file." // *Cause: Open system call returned an error. Unable to open database file. // *Action: Check errno. 07355, 00000, "sfccf: fstat error, unable to obtain file status." // *Cause: Unable to obtain file status. Further error closing file is // returned as additional information. // *Action: Verify database files exist, and have proper permissions. 07356, 00000, "sfccf: lseek error, unable to seek to beginning of file." // *Cause: Additional information indicates if close also failed. // *Action: Check errno. 07357, 00000, "sfccf: write error, unable to write database header block." // *Cause: Write system call returned an error. Unable to write database file. // *Action: Check errno. 07358, 00000, "sfccf: write error, unable to write to file." // *Cause: Additional information indicates if close failed. // *Action: Check errno. Possible lack of space on device. 07359, 00000, "sfifi: invalid logical block size." // *Cause: A blocksize was specified which is incorrect. The logical block size // must be a multiple of the physical block size, and smaller than the // maximum. // *Action: Additional information returns the block size specified. Check block // size parameters in init.ora file. 07360, 00000, "sfifi: stat error, unable to obtain information about file." // *Cause: Stat system call returned an error. // *Action: Check errno. Check that file exists. 07361, 00000, "sfifi: malloc error, unable to allocate buffer for header block." // *Cause: Malloc library routine returned an error. // *Action: Possible memory resource shortage. 07362, 00000, "sfifi: open error, unable to open file." // *Cause: Open system call returned an error. // *Action: Check errno. Verify existence, and permissions on database files. 07363, 00000, "sfifi: lseek error, unable to seek to beginning of file." // *Cause: Lseek system call returned an error. // *Action: Check errno. Additional information indicates error in closing file. 07364, 00000, "sfifi: read error, unable to read header block." // *Cause: Read system call returned an error. Unable to read database file. // *Action: Check errno. 07365, 00000, "sfifi: close error." // *Cause: Close system call returned an error. // *Action: Check errno. 07366, 00000, "sfifi: invalid file, file does not have valid header block." // *Cause: This file does not look like a valid database file. // *Action: Verify database files are correct. 07367, 00000, "sfifi: logical block size mismatch." // *Cause: Logical block size of file is not expect block size. // *Action: Verify logical block sizes are correct. 07368, 00000, "sfofi: open error, unable to open database file." // *Cause: Open system call returned an error. // *Action: Check errno. Verify existence, and permissions on database files. 07369, 00000, "sfcfi: close error, unable to close database file." // *Cause: Close system call returned an error. // *Action: Check errno. 07370, 00000, "sfrfb: invalid block number." // *Cause: The block number requested was out of bounds for the file. // Additional information indicates block number. // *Action: Verify block number. 07371, 00000, "sfrfb: lseek error, unable to seek to requested block" // *Cause: Additional information returns block number. // *Action: Check errno. Check block number. 07372, 00000, "sfrfb: read error, unable to read requested block from database file." // *Cause: Read system call returned an error. // *Action: Check errno. Additional information indicates block number. 07373, 00000, "sfrfb: read returned incorrect number of bytes." // *Cause: Possible truncated read of database file. Additional information // returns block number and actual number of bytes read. // *Action: Check block number and number of bytes read. 07374, 00000, "sfwfb: invalid block number." // *Cause: File block number is out of range of file. Additional informatin // returns block number. // *Action: Check block number. 07375, 00000, "sfwfb: lseek error, unable to seek to requested block." // *Cause: Additional information indicates block number. // *Action: Verify block number. 07376, 00000, "sfwfb: write error, unable to write database block." // *Cause: Additional information returns block number. // *Action: Check errno. Check block number. 07377, 00000, "sfwfb: write returned incorrect number of bytes." // *Cause: Possible truncated write. Additional information returns block // number and number of bytes. // *Action: Check block number and number of bytes written. 07378, 00000, "sfcmf: translation error, unable to expand file name." // *Cause: Additional information returns error returned from sltln. Unable // to expand old file name. // *Action: Check additional information. 07379, 00000, "sfcmf: new file exists." // *Cause: Attempt to create a new database file with existing file name. // This could clobber a database file. // *Action: Check file name. Verify that new file does not exist. 07380, 00000, "sfcmf: translation error, unable to expand old file name." // *Cause: Additional information indicates sltln error. // *Action: Check additional information. 07381, 00000, "sfccf: translation error, unable to expand file name." // *Cause: Additional information indicates sltln error. // *Action: Check additional information. 07382, 00000, "sfifi: translation error, unable to expand file name." // *Cause: Additional information indicates sltln error. // *Action: Check additional information. 07383, 00000, "sfgfs: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 07384, 00000, "sfgfn: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 07385, 00000, "sfcfi: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 07386, 00000, "sfrfb: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 07387, 00000, "sfwfb: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 07388, 00000, "sfccf: reuse specified, but file does not exist." // *Cause: Reuse option was specified to create database statement, but file // to reuse does not exist. // *Action: Verify that file exists, or do not specify reuse. 07389, 00000, "sfccf: open error, unable to open file to reuse." // *Cause: Open system call returned an error. // *Action: Check errno. 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, "sfccf: file mismatch, trying to reuse a file with different size." // *Cause: The file size does not match. If error occurs in closing the file, // additional information indicates the errno. // *Action: Verify that file size is correct. 07394, 00000, "sfccf: file mismatch, trying to reuse a file with different block size." // *Cause: The logical block size does not match. // *Action: Verify that logical block size is correct. If error occurs in // closing the file, additional information indicates the errno. 07395, 00000, "sfccf: function called with illegal option." // *Cause: Funcion was called with an invalid parameter. // *Action: Possible internal error. 07396, 00000, "sfccf: lseek error, unable to seek to begining of reuse file." // *Cause: Lseek system call returned an error. // *Action: Check errno. 07397, 00000, "sfccf: read error, unable to read header block of file." // *Cause: Read system call returned an error. // *Action: Check errno. 07398, 00000, "sfccf: invalid header information, file is not a valid database file." // *Cause: Possibly trying to use a non-database file as a database file. // *Action: Verify that file is a database file. 07399, 00000, "sfccf: 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. 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, "sfcfi: Close failed in one of the database writers." // *Cause: One of the database writer processes got an error when // closing a file. // *Action: Check errno in all database writer trace files. 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. 07413, 00000, "sfcopy: source and destination logical block sizes must match." // *Cause: The destination file supplied to sfcopy has a different // logical block size than the source file. // *Action: Internal error; please contact customer support. 07414, 00000, "sfcopy: allocation of memory buffer failed." // *Cause: Malloc() failed to allocate the temporary buffer for copying // data from the source file to the destination file. // *Action: System has run out of heap space. 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. 07420, 00000, "sfccf: Illegal file type." // *Cause: Cannot initialize a file of illegal file type. // *Action: Verify that your file name is correct. The supported file types // are raw devices and regular files. 07421, 00000, "sfcopy: failed to read from the source file during copy." // *Cause: An error occurred when reading from the source file. // *Action: Check additional information for the error occurred during read. 07422, 00000, "sfcopy: failed to write to the destination file during copy." // *Cause: An error occurred when writing to the destination file. // *Action: Check additional information for the error occurred during write. 07423, 00000, "sfrfb: read failed because buffer was not aligned properly." // *Cause: The i/o buffer was not aligned to the correct boundary. // *Action: Internal error. Keep the trace file and contact customer support. 07424, 00000, "sfwfb: write failed because buffer was not aligned properly." // *Cause: The i/o buffer was not aligned to the correct boundary. // *Action: Internal error. Keep the trace file and contact customer support. 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. 07428, 00000, "smsgsg: ftok() returned error in calculating key for sga." // *Cause: the ftok() library call failed in smsgsg(). // *Action: Verify that the ${ORACLE_HOME}/sgadef${ORACLE_SID}.dbf file // exists. If it does, this is a possible system failure. Perhaps // System V compatibility is not enabled. The additional information // indicates the segment in which the error occurred. 07429, 00000, "smsgsg: shmget() failed to get segment." // *Cause: a shared memory segment used for all part of the SGA could not be // retrieved. // *Action: Use the system error number in the error message to determine why // the segment could not be retrieved. If it does not exists, shutdown // the database using the "abort" option, and then restart it. // If the get failed because the permissions are incorrect, make sure // that the ownership of the oracle executable is the same as that on // the shared memory segment. 07430, 00000, "smsgsg: calculated and stored keys do not match." // *Cause: When smsgsg() gets a segment, it re-calculates the key // for the segment. It then compares the value against the value // stored in the sgadef file. If they do not match, the file is // probably corrupt. // *Action: shutdown the database and restart it. 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. 07433, 00000, "sfrnms: the mirror side status parameter is invalid" // *Cause: The mirror side status passed to sfrnms is invalid. // *Action: This is an Oracle internal error. 07434, 00000, "sfgmsn: the mirror side status parameter is invalid" // *Cause: The mirror side status passed to sfgmsn is invalid. // *Action: This is an Oracle internal error. 07435, 00000, "invalid parameter passed to an resilvering testing function" // *Document: NO // *Cause: Some of the parameters passed to resilvering testing functions // via the event mechanism are invalid. // *Action: Read the alert log for more detailed error messages and // specify correct parameters. 07440, 00000, "WMON process terminated with error" // *Cause: The wakeup monitor process died. // *Action: Warm start instance. 07441, 00000, "function address must be aligned on %s byte boundary" // *Cause: An improperly aligned function address was specified. // *Action: Use a properly aligned function address. 07442, 00000, "function address must be in the range %s to %s" // *Cause: An invalid function address was specified. // *Action: Use a valid function address. 07443, 00000, "function %s not found" // *Cause: An invalid function name was specified. // *Action: Use a valid function name. 07444, 00000, "function address %s is not readable" // *Cause: An invalid function name/address was specified. // *Action: Use a valid function name/address. 07445, 00000, "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]" // *Cause: An OS exception occurred which should result in the creation of a // core file. This is an internal error. // *Action: Contact your customer support representative. 07446, 00000, "sdnfy: bad value '%s' for parameter %s." // *Cause: The directory specified as the value for the stated parameter could // not be used. // *Action: Make sure the directory you have specified is a valid // directory/file specification. 07447, 00000, "ssarena: usinit failed." // *Cause: Oracle failed to create a shared arena file. // *Action: Use sercerrno field to determine cause of failure. 07448, 00000, "ssarena: maximum number of shared arenas exceeded." // *Cause: Oracle attempted to create more shared arena files than permitted. // *Action: Raise the value for max_arena in init.ora. 07449, 00000, "sc: usnewlock failed." // *Cause: Oracle failed to acquire a shared arena lock. // *Action: Check result code in sercerrno to determine the cause of failure. 07450, 00000, "sms1sg: vm_mapmem error, unable to create shared memory." // *Cause: Error in vm_mapmem. Failed to create SGA as a single shared // memory segment. // *Action: Check result code returned in sercose[0]. 07451, 00000, "sms1sg: shared memory attach address incorrect." // *Cause: The vm_mapmem system call attached the SGA at an incorrect // location. // *Action: Verify that the SGA attach address is valid. 07452, 00000, "sms1sg: failed to change SGA inheritance." // *Cause: The vm_inherit system called failed to change the inheritance // of the SGA. // *Action: Check result code returned in sercose[0]. Possible operating // system failure. 07453, 00000, "smsmat: vm_mapmem error, unable to create shared memory." // *Cause: Error in vm_mapmem. Failed to create a segment of the SGA. // *Action: Check result code returned in sercerrno. 07454, 00000, "smsmat: shared memory attach address incorrect." // *Cause: The vm_mapmem system call attached an SGA segment at // an incorrect location. // *Action: Verify that the SGA attach address is valid. 07455, 00000, "smsmat: failed to change SGA segment inheritence." // *Cause: The vm_inherit system call failed to change the inheritence // of a segment of the SGA. // *Action: Check result code returned in sercerrno. Possible operating // system failure. 07456, 00000, "smsmax: cannot get cluster size." // *Cause: The cluster_stat system call failed to return status for // the cluster. // *Action: Check result code in sercose[0]. Possible operating system // failure. 07457, 00000, "smsdes: name translation failure 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]. 07458, 00000, "smsdes: close error, unable to close sgadef.dbf." // *Cause: An error occurred in close, while closing the file // ?/dbs/sgadef@.dbf" // *Action: Verify that sgadef.dbf file has been deleted. Possible operating // system error. 07459, 00000, "smsvmfcre: name translation failure 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]. 07460, 00000, "smsvmfcre: sgadef.dbf already exists when creating SGA." // *Cause: The file ?/dbs/sgadef@.dbf should not exist when trying to create // the SGA; otherwise a running instance could be clobbered. // *Action: Verify that the database is really down, and delete the // sgadef.dbf file. This should only happen when the machine // crashed with the database up. 07461, 00000, "smsvmfcre: create failure in creating sgadef.dbf file." // *Cause: open failed when trying to create the file ?/dbs/sgadef@.dbf. // *Action: Verify permissions on the $(ORACLE_HOME)/dbs directory. 07462, 00000, "smsget: 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]. 07463, 00000, "smsget: 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. 07464, 00000, "smsget: vm_mapmem or vm_allocate error when trying to attach SGA." // *Cause: The vm_mapmem or vm_allocate system call failed when attempting // to attach a segment of the SGA. // *Action: Check result code returned in sercerrno. SGA segment number // returned in sercose[1]. 07465, 00000, "smsget: shared memory attach address incorrect." // *Cause: The vm_mapmem system call attached an SGA segment at // an incorrect location. // *Action: Verify that the segment exists, and the SGA attach address is valid. 07466, 00000, "smsget: failed to change SGA segment inheritence." // *Cause: The vm_inherit system call failed to change the inheritence // of a segment of the SGA. // *Action: Check result code returned in sercerrno. Possible operating // system failure. 07467, 00000, "smsget: 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. 07468, 00000, "spwat: mset wrror, unable to set semaphore." // *Cause: The mset routine returned an error. Semaphore may not exist. // *Action: Check result code in sercerrno. Semaphore number returned // in sercose[0]. 07469, 00000, "sppst: mclear error, unable to clear semaphore." // *Cause: The mclear routine returned an error. Semaphore may not exist. // *Action: Check result code in sercerrno. Semaphore number returned // in sercose[0]. 07470, 00000, "snclget: cannot get cluster number." // *Cause: The cluster_status system call failed to get status information // for the current cluster. // *Action: Check result code in sercose[0]. Possible operating system // failure. 07471, 00000, "snclrd: name translation error of sgadef.dbf file name." // *Cause: Unable to expand out ?/dbs/sgadef@.dbf file name. // *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. // Check error number returned from sltln in sercose[0]. 07472, 00000, "snclrd: open error when opening sgadef.dbf file." // *Cause: open failed when opening the file ?/dbs/sgadef@.dbf // *Action: Check errno. Possible permission problem. Verify that the // file ?/dbs/sgadef@.dbf exists. 07473, 00000, "snclrd: read error when trying to read sgadef.dbf file." // *Cause: Read had an error when reading sgadef.dbf file. // *Action: Check errno. Verify file exists, and is correct size. 07474, 00000, "snclrd: close error, unable to close sgadef.dbf file." // *Cause: An error occurred in close, while closing the file // ?/dbs/sgadef@.dbf" // *Action: Check errno. Possible operating system error. 07475, 00000, "slsget: cannot get vm statistics." // *Cause: The vm_statistics system call failed to get virtual memory // statistics. // *Action: Check result code in sercerrno. Possible operating system // failure. 07476, 00000, "slsget: cannot get mapped memory statistics." // *Cause: The vm_mapmem system call failed to get mapped memory // statistics. // *Action: Check result code in sercerrno. Possible operating system // failure. 07477, 00000, "scgcmn: lock manager not initialized." // *Cause: Lock manager must be initialized before converting locks. // *Action: Check result code in sercerrno. Possible lock manager failure. 07478, 00000, "scgcmn: cannot get lock status." // *Cause: lm_stat_lock failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07479, 00000, "scgcmn: cannot open or convert lock." // *Cause: lm_open or lm_open_convert failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07480, 00000, "snchmod: cannot change permissions on ?/dbs/sgalm.dbf." // *Cause: When creating an instance, snlmini could not change the // permissions on ?/dbs/sgalm.dbf // *Action: Contact your customer support representative. 07481, 00000, "snlmatt: cannot attach to lock manager instance." // *Cause: lm_attach failed to attach to lock manager instance. // *Action: Check result code in sercerrno. Possible lock manager failure. 07482, 00000, "snlmini: cannot create lock manager instance." // *Cause: lm_create failed to create lock manager instance. // *Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if // it exists, then retry. 07483, 00000, "snlkget: cannot convert(get) lock." // *Cause: lm_convert failed to convert(get) lock. // *Action: Check result code in sercerrno. Possible lock manager failure. 07484, 00000, "snlkput: cannot convert(put) lock." // *Cause: lm_convert failed to put lock value. // *Action: Check result code in sercerrno. Possible lock manager failure. 07485, 00000, "scg_get_inst: cannot open instance number lock." // *Cause: lm_open failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07486, 00000, "scg_get_inst: cannot convert(get) instance number lock." // *Cause: lm_convert failed to get lock value. // *Action: Check result code in sercerrno. Possible lock manager failure. 07487, 00000, "scg_init_lm: cannot create lock manager instance." // *Cause: lm_create failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07488, 00000, "scgrcl: lock manager not initialized." // *Cause: Lock manager must be initialized before releasing locks. // *Action: Check result code in sercerrno. Possible lock manager failure. 07489, 00000, "scgrcl: cannot get lock status." // *Cause: lm_stat_lock failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07490, 00000, "scgrcl: cannot convert lock." // *Cause: lm_convert failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07491, 00000, "scgrcl: cannot cancel lock request." // *Cause: lm_cancel failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07492, 00000, "scgrcl: cannot close lock." // *Cause: lm_close failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07493, 00000, "scgrcl: lock manager error." // *Cause: An error was encountered releasing the lock. // *Action: Check result code in sercerrno. Possible lock manager failure. 07494, 00000, "scgcm: unexpected error." // *Cause: Unknown or unexpected error code. // *Action: Check result code in sercerrno. Possible lock manager failure. 07495, 00000, "spwat: lm_wait failed." // *Cause: lm_wait failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07496, 00000, "sppst: lm_post failed." // *Cause: lm_post failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07497, 00000, "sdpri: cannot create trace file '%s'; errno = %s." // *Cause: The trace file cannot be created for writing. // *Action: Check if the dump directory exists and whether it is writable. 07498, 00000, "spstp: Unable to open /dev/resched." // *Cause: The rescheduling driver /dev/resched is not found or is // not working properly. // *Action: Check installation of the ORACLE rescheduling driver // in the AIX kernel. 07499, 00000, "spglk: Cannot reschedule." // *Cause: The rescheduling driver /dev/resched is not open. // This is an internal error and should not occur. // *Action: Contact your customer support representative. / / 7500-7999 VMS OSD ERRORS / 07500, 00000, "scglaa: $cantim unexpected return" // *Cause: VMS system service $CANTIM returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07501, 00000, "scgtoa: $deq unexpected return" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07502, 00000, "scgcmn: $enq unexpected return" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07503, 00000, "scgcmn: $setimr unexpected return" // *Cause: VMS system service $SETIMR returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07504, 00000, "scgcmn: $hiber unexpected return" // *Cause: VMS system service $HIBER returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07505, 00000, "scggt: $enq parent lock unexpected return" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07506, 00000, "scgrl: $deq unexpected return on lockid %s" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07507, 00000, "scgcm: unexpected lock status condition" // *Cause: A global locking system service returned an unexpected value. // *Action: Check for system error message (if any) and refer to // VMS documentation, or contact your customer support // representative. 07508, 00000, "scgfal: $deq all unexpected return" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07509, 00000, "scgfal: $deq parent lock unexpected return" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07510, 00000, "scgbrm: $getlki unexpected return on lockid %s" // *Cause: VMS system service $GETLKI returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07511, 00000, "sscggtl: $enq unexpected return for master termination lock" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07512, 00000, "sscggtl: $enq unexpected return for client termination lock" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07513, 00000, "sscgctl: $deq unexpected return on cancel of term. lock" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07514, 00000, "scgcan: $deq unexpected return while canceling lock" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation / / 7515 .. 7525: sfccf errors / 07515, 00000, "sfccf: UIC group <= MAXSYSGROUP - file operations not allowed" // *Cause: Allowing DBAs to perform file operations if their account's UIC // group is less than or equal to the SYSGEN parameter MAXSYSGROUP // poses a security risk. // *Action: Make sure that the DBA creating or opening database files, // redo log files, etc. has a UIC group greater than MAXSYSGROUP. 07516, 00000, "sfccf: $open file error" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07517, 00000, "sfccf: existing file size mismatch with specified file size" // *Cause: A file that was specified REUSE exists already but differs in size // *Action: Specify a file size equal to that of the existing file or // don't REUSE. 07518, 00000, "sfccf: illegal file creation option" // *Cause: An illegal creation option (reuse, etc) was sent to sfccf. // *Action: This is an internal error, please report to Oracle 07519, 00000, "sfccf: REUSE not allowed since file owner group <= MAXSYSGROUP" // *Cause: Allowing the ORACLE server to REUSE files owned by users with a // UIC group less than or equal to the SYSGEN parameter MAXSYSGROUP // poses a security risk. // *Action: Be sure that no database files, log files, or control files // that you attempt to REUSE are owned by an account with a UIC // group less than or equal to the SYSGEN parameter MAXSYSGROUP. // If any valid ORACLE files exist with such ownership conditions, // you will need to change their ownership before attempting to // REUSE them. 07520, 00000, "sfccf: illegal logical block size" // *Cause: An illegal logical 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. 07521, 00000, "sfccf: $create file error" // *Cause: VMS system service $CREATE failed // *Action: Examine system error message and refer to VMS documentation 07522, 00000, "sfccf: new file exists" // *Cause: A file that was not designated as REUSE already existed // *Action: Add REUSE to the file specification or delete the existing file 07523, 00000, "sfccf: $connect error" // *Cause: VMS system service $CONNECT failed // *Action: Examine system error message and refer to VMS documentation 07524, 00000, "sfccf: $write (zero file) error" // *Cause: VMS system service $WRITE failed // *Action: Examine system error message and refer to VMS documentation 07525, 00000, "sfccf: $close error" // *Cause: VMS system service $CLOSE failed // *Action: Examine system error message and refer to VMS documentation 07526, 00000, "sfifi: illegal logical block size" // *Cause: An illegal logical 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. 07527, 00000, "sfifi: UIC group <= MAXSYSGROUP - file operations not allowed" // *Cause: Allowing DBAs to perform file operations if their account's UIC // group is less than or equal to the SYSGEN parameter MAXSYSGROUP // poses a security risk. // *Action: Make sure that the DBA creating or opening database files, // redo log files, etc. has a UIC group greater than MAXSYSGROUP. 07528, 00000, "sfifi: $open error" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07529, 00000, "sfifi: $close error" // *Cause: VMS system service $CLOSE failed // *Action: Examine system error message and refer to VMS documentation 07530, 00000, "sfofi: $open error" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07531, 00000, "ssfccf: $DISPLAY error" // *Cause: VMS system service $DISPLAY failed // *Action: Examine system error message and refer to VMS documentation 07532, 00000, "sfcfi: $dassgn error" // *Cause: VMS system service $DASSGN failed // *Action: Examine system error message and refer to VMS documentation 07533, 00000, "sfifi: Cannot open file since file owner group <= MAXSYSGROUP" // *Cause: Allowing the ORACLE server to open files owned by users with a UIC // group less than or equal to the SYSGEN parameter MAXSYSGROUP // poses a security risk. // *Action: Be sure that no database files, log files, or control files // that you attempt to open are owned by an account with a UIC // group less than or equal to the SYSGEN parameter MAXSYSGROUP. // If any valid ORACLE files exist with such ownership conditions, // you will need to change their ownership before attempting to // open them. 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 07535, 00000, "sfrfb: illegal logical block number" // *Cause: An attempt was made to read a block beyond the end of the file // *Action: This is an internal error, please report to Oracle 07536, 00000, "sfrfb: $qio(read) error" // *Cause: VMS system service $QIO failed // *Action: Examine system error message and refer to VMS documentation 07537, 00000, "sfccf: Cannot create file since file owner group <= MAXSYSGROUP" // *Cause: Allowing the ORACLE server to CREATE or REUSE files owned by // users with a UIC group less than or equal to the SYSGEN parameter // MAXSYSGROUP poses a security risk. // *Action: Be sure that no database files, log files, or control files // that you attempt to REUSE are owned by an account with a UIC // group less than or equal to the SYSGEN parameter MAXSYSGROUP. // If any valid ORACLE files exist with such ownership conditions, // you will need to change their ownership before attempting to // REUSE them. Likewise, if you attempt to create a file which // will inherit an illegal ownership from the parent directory, // you should create it in a different location, or take other // steps to avoid this situation. 07538, 00000, "sfsgrow: $qiow failed" // *Cause: VMS system service $QIOW failed // *Action: Examine system error message and refer to VMS documentation 07539, 00000, "sfqioini: $qio error" // *Cause: VMS system service $QIO failed // *Action: Examine system error message and refer to VMS documentation 07540, 00000, "sfqioast: I/O completion ast error" // *Cause: An asynchronous disk I/O operation completed abnormally. // *Action: Examine system error message and refer to VMS documentation, // or contact your customer support representative. 07541, 00000, "sfifi: Cannot identify zero-length file." // *Cause: Cannot use the specified file since it is zero-length. // *Action: Examine each of the specified files to determine which one is // zero-length and replace that with a file that is not zero-length. 07542, 00000, "sfccf: Cannot create-reuse anything but top version of file." // *Cause: You tried to create-reuse an ORACLE data file with a specific // version number. The specified version number was above or below // that of the top version of the data file. This poses a security // risk. // *Action: Do not specifiy the version number of the file when create- // reusing ORACLE data files. Alternately, you should specify the // version number of the existing top version of this file. 07543, 00000, "sfrfb: Cannot read from zero-length file." // *Cause: Cannot read any logical blocks from the specified file since it is // zero-length. // *Action: Examine each of the specified files to determine which one is // zero-length and replace that with a file that is not zero-length. 07544, 00000, "sfqio: asynchronous I/O not completed successfully" // *Cause: The asynchronous I/O being performed did not complete successfully. // *Action: Examine the additional error messages and refer to VMS // documentation 07545, 00000, "sfcmf: $PARSE failure (filename syntax)" // *Cause: VMS system service failed due to a syntax error when trying to add // a new file to the database // *Action: Examine system error and correct filename syntax 07546, 00000, "sfcmf: new file exists" // *Cause: The filename of a file to be added resolved to that of one // already in the database // *Action: Change the filename of the file to be added 07547, 00000, "sfcmf: $OPEN failure" // *Cause: VMS system service $OPEN failed // *Action: Examine 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 07553, 00000, "sfofi: out of open files" // *Cause: The number of open files has exceeded a VMS Oracle compile // time limit. // *Action: Internal error; please contact customer support. 07554, 00000, "sfcopy: source & destination logical block sizes must match" // *Cause: The destination file supplied to sfcopy has a different // logical block size than the source file. // *Action: Internal error; please contact customer support 07555, 00000, "sfqioast: illegal pending value" // *Cause: An internal inconsistency was found while doing an asynch disk io // *Action: Internal error; please contact customer support. 07556, 00000, "sfotf: $create error" // *Cause: VMS system service $CREATE failed // *Action: Examine system error message and refer to VMS documentation 07557, 00000, "ssfctf: illegal logical block size specified for tape file" // *Cause: An illegal logcial block size was specified for the tape file. // *Action: This is an internal error; please contact customer support. 07558, 00000, "ssfctf: $create error" // *Cause: VMS system service $CREATE failed // *Action: Examine system error message and refer to VMS documentation 07559, 00000, "sfdone: asynchronous I/O not completed successfully" // *Cause: The asynchronous I/O being performed did not complete successfully. // *Action: Internal error; please contact customer support. 07560, 00000, "sltln: $trnlog error" // *Cause: Translation of a logical name failed, for example due to // overflow or too many levels of logical names. // *Action: Look for a name like ORA_SID that is exceptionally long or // defined circularly. If none, report as a bug. 07561, 00000, "szprv: $IDTOASC failure" // *Cause: VMS system service $IDTOASC failed // *Action: Examine system error message and refer to VMS documentation 07562, 00000, "sldext: extension must be 3 characters" // *Cause: An extension was found but it is of improper length // *Action: This is an internal error, please report to Oracle 07563, 00000, "sldext: $PARSE failure" // *Cause: VMS system service $PARSE failed // *Action: Examine system error message and refer to VMS documentation 07564, 00000, "sldext: wildcard in filename or extension" // *Cause: A wildcard was used in the file name // *Action: Reenter the file name completely 07565, 00000, "sldext: $SEARCH failure" // *Cause: VMS system service $SEARCH failed // *Action: Examine system error message and refer to VMS documentation 07568, 00000, "slspool: $OPEN failure" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07569, 00000, "slspool: $CLOSE failure" // *Cause: VMS system service $CLOSE failed // *Action: Examine system error message and refer to VMS documentation 07570, 00000, "szrfc: $IDTOASC failure" // *Cause: VMS system service $IDTOASC failed // *Action: Examine system error message and refer to VMS documentation 07571, 00000, "szrfc: $FIND_HELD failure" // *Cause: VMS system service $FIND_HELD failed // *Action: Examine system error message and refer to VMS documentation 07572, 00000, "szrfc: insufficient rolename buffer space" // *Cause: An OS role name was too long. // *Action: Re-define the role name to be of correct length. 07573, 00000, "slkhst: could not perform host operation" // *Cause: VMS system service LIB$SPAWN failed // *Action: Examine system error message and refer to VMS documentation 07574, 00000, "szrfc: $GETUAI failure" // *Cause: VMS system service $GETUAI failed // *Action: Examine system error message and refer to VMS documentation 07576, 00000, "sspexst: $GETJPIW failure on process id %s" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07577, 00000, "no such user in authorization file" // *Cause: An attempt was made to set an INTERNAL password (for either DBA // or OPER privilege), but the corresponding VMS account (either // ORA__DBA or ORA__OPER) hasn't been created yet. // *Action: Add a VMS account for ORA__DBA and/or ORA__OPER before // trying to set a password for them. 07578, 00000, "szprv: $FIND_HELD failure" // *Cause: VMS system service $FIND_HELD failed // *Action: Examine system error message and refer to VMS documentation 07579, 00000, "spini: $DCLEXH failure" // *Cause: VMS system service $PARSE failed // *Action: Examine system error message and refer to VMS documentation 07580, 00000, "spstp: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07581, 00000, "spstp: cannot derive SID from unexpected process name" // *Cause: A background process did not have name of correct form // *Action: If the job name was changed, restore it, otherwise this is // an internal error, please report to Oracle. 07582, 00000, "spstp: ORA_SID has illegal value" // *Cause: The ORA_SID must exist and be less than 6 characters // *Action: Consult the VMS Installation guide for information on setting // the SID. 07584, 00000, "spdcr: invalid value for ORA_sid_(proc_)PQL$_item" // *Cause: A logical name used to set a detached process quota value // has an invalid value (probably non-numeric). // *Action: Examine the values of these logical names, correct the one // in error, and retry. 07585, 00000, "spdcr: $PARSE failure" // *Cause: VMS system service $PARSE failed // *Action: Examine system error message and refer to VMS documentation 07586, 00000, "spdcr: $SEARCH failure" // *Cause: VMS system service $SEARCH failed // *Action: Examine system error message and refer to VMS documentation 07587, 00000, "spdcr: $CREPRC failure" // *Cause: VMS system service $CREPRC failed // *Action: Examine system error message and refer to VMS documentation 07588, 00000, "spdcr: $GETJPIW get image name failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07589, 00000, "spdde: system id not set" // *Cause: The logical name ORA_SID doesn't translate to a valid value. // *Action: Check the value of ORA_SID in the process that gets the // error, and correct the installation or command procedures // that caused ORA_SID to be set incorrectly. 07590, 00000, "spdde: $DELPRC failure" // *Cause: VMS system service $DELPRC failed // *Action: Examine system error message and refer to VMS documentation 07591, 00000, "spdde: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07592, 00000, "sspgprv: Error obtaining required privileges" // *Cause: While obtaining needed privileges, an error was returned from // SYS$SETPRV. // *Action: This is an internal error. Please report to Oracle 07593, 00000, "ssprprv: Error release privileges" // *Cause: While releasing privileges, an error was returned from SYS$SETPRV. // *Action: This is an internal error. Please report to Oracle 07594, 00000, "spiip: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07595, 00000, "sppid: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07596, 00000, "sptpa: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07597, 00000, "spguns: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07598, 00000, "spwat: $SETIMR failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07599, 00000, "spwat: $SCHDWK failure" // *Cause: VMS system service $SCHDWK failed // *Action: Examine system error message and refer to VMS documentation 07600, 00000, "slkmnm: $GETSYIW failure" // *Cause: VMS system service $GETSYIW failed // *Action: Examine system error message and refer to VMS documentation 07601, 00000, "spguno: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07602, 00000, "spgto: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07605, 00000, "szprv: $ASCTOID failure" // *Cause: VMS system service $ASCTOID failed // *Action: Examine system error message and refer to VMS documentation 07606, 00000, "szprv: $CHKPRO failure" // *Cause: VMS system service $CHKPRO failed // *Action: Examine system error message and refer to VMS documentation 07607, 00000, "szaud: $SNDOPR failure" // *Cause: VMS system service $SNDOPR failed // *Action: Examine system error message and refer to VMS documentation 07608, 00000, "szprv: $GETUAI failure" // *Cause: VMS system service $GETUAI failed // *Action: Examine system error message and refer to VMS documentation 07609, 00000, "szprv: $HASH_PASSWORD failure" // *Cause: VMS system service $HASH_PASSWORD failed // *Action: Examine system error message and refer to VMS documentation 07610, 00000, "$GETJPIW failed in retrieving the user's MAC priviledges" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07612, 00000, "$GETUAI failed in retrieving the user's clearance level" // *Cause: VMS system service $GETUAI failed // *Action: Examine system error message and refer to VMS documentation 07613, 00000, "$GETJPIW failed in retrieving the user's process label" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07614, 00000, "$CHANGE_CLASS failed in retrieving the user's process label" // *Cause: VMS system service $CHANGE_CLASS failed // *Action: Examine system error message and refer to SEVMS documentation 07615, 00000, "$CHANGE_CLASS failed in retrieving the specified file label" // *Cause: VMS system service $CHANGE_CLASSS failed // *Action: Examine system error message and refer to SEVMS documentation 07616, 00000, "$CHANGE_CLASS failed in retrieving the specified device label" // *Cause: VMS system service $CHANGE_CLASS failed // *Action: Examine system error message and refer to SEVMS documentation 07617, 00000, "$FORMAT_CLASS failed translating the binary label to a string" // *Cause: VMS system service $FORMAT_CLASS failed because the given binary // classification was not valid. // *Action: Examine system error message and refer to SEVMS documentation 07618, 00000, "$IDTOASC failed translating a secrecy level" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of a secrecy level. // *Action: Define the entry in the rights database which the binary label // you specified references. 07619, 00000, "$IDTOASC failed translating an integrity level" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of an integrity level. // *Action: Define the entry in the rights database which the binary label // you specified references. 07620, 00000, "smscre: illegal database block size" // *Cause: An illegal database block size was specified in the parameter file. // It must be positive, a multiple of 512, and less than the maximum // physical i/o data size. // *Action: Change db_block_size in the parameter file to conform to these // limits. 07621, 00000, "smscre: illegal redo block size" // *Cause: An illegal redo log buffer size was specified in the parameter file. // It must be positive and a multiple of 512. // *Action: Change log_buffer in the parameter file to conform to these limits. 07622, 00000, "smscre: $CREATE failure" // *Cause: While creating the system global area (SGA) backing file, VMS // system service $CREATE failed. // *Action: Examine the system error message and refer to VMS documentation. 07623, 00000, "smscre: $CRMPSC failure" // *Cause: While creating the system global area (SGA), VMS system service // $CRMPSC failed. // *Action: Examine the system error message and refer to VMS documentation. 07624, 00000, "smsdes: $DGBLSC failure" // *Cause: While deleting the system global area (SGA), VMS system service // $DGBLSC failed. // *Action: Examine the system error message and refer to VMS documentation. 07625, 00000, "smsget: $MGBLSC failure" // *Cause: While mapping the system global area (SGA) during logon, VMS // system service $MGBLSC failed. The usual reason is that ORACLE // has not been started up. // *Action: Examine the system error message and refer to VMS documentation. // Start up ORACLE if it is not already started. 07626, 00000, "smsget: sga already mapped" // *Cause: An attempt to map the SGA during logon failed because it was // already mapped. This is an internal error. // *Action: Exit your program and try again, and report this to your // customer support representative. 07627, 00000, "smsfre: $CRETVA failure" // *Cause: While unmapping the system global area (SGA) during logoff, VMS // system service $CRETVA failed. // *Action: Examine the system error message and refer to VMS documentation. 07628, 00000, "smsfre: sga not mapped" // *Cause: An attempt to unmap the SGA during logoff failed because it was // not mapped. This is an internal error. // *Action: Exit your program and try again, and report this to your // customer support representative. 07629, 00000, "smpall: $EXPREG failure" // *Cause: While extending the program global area (PGA), VMS // system service $EXPREG failed. This often happens when the virtual // memory page count quota is exceeded. // *Action: Examine the system error message and refer to VMS documentation. 07630, 00000, "smpdal: $DELTVA failure" // *Cause: While deleting the program global area (PGA) during logoff, VMS // system service $DELTVA failed. // *Action: Examine the system error message and refer to VMS documentation. 07631, 00000, "smcacx: $EXPREG failure" // *Cause: While creating or extending a context area, VMS system service // $EXPREG failed. This often happens when the virtual memory page // count quota is exceeded. // *Action: Examine the system error message and refer to VMS documentation. 07632, 00000, "smsrcx: $DELTVA failure" // *Cause: While deleting a context area, VMS system service $DELTVA failed. // *Action: Examine the system error message and refer to VMS documentation. 07633, 00000, "smsdbp: illegal protection value" // *Cause: The buffer debug function was called with an illegal value. // This is an internal error. // *Action: Contact your customer support representative. 07634, 00000, "smsdbp: $CRETVA failure" // *Cause: While attempting to set protection in the database buffer // debug mechanism, VMS system service $CRETVA failed. // *Action: Contact your customer support representative. 07635, 00000, "smsdbp: $SETPRT failure" // *Cause: While attempting to set protection in the database buffer // debug mechanism, VMS system service $SETPRT failed. // *Action: Contact your customer support representative. 07636, 00000, "smsdbp: $MGBLSC failure" // *Cause: While attempting to set protection in the database buffer // debug mechanism, VMS system service $MGBLSC failed. // *Action: Contact your customer support representative. 07637, 00000, "smsdbp: buffer protect option not specified when sga created" // *Cause: Trying to change the buffer protect mode when the SGA was not // created with buffer protect debug option. This is an internal error. // *Action: Contact your customer support representative. 07638, 00000, "smsget: SGA pad area not large enough for created SGA" // *Cause: An attempt was made to map an SGA with software in which // the SGA pad area isn't large enough. // *Action: Create a smaller SGA, or relink the software with a larger pad. 07639, 00000, "smscre: SGA pad area not large enough (%s bytes required)" // *Cause: An attempt was made to create an SGA with software in which // the SGA pad area isn't large enough. // *Action: Create a smaller SGA, or relink the software with a larger pad. 07640, 00000, "smsget: SGA not yet valid. Initialization in progress" // *Cause: An attempt was made to map to the SGA while it was being // initialized. // *Action: Wait until initialization is complete, and try again. 07641, 00000, "smscre: Unable to use the system pagefile for the SGA" // *Cause: The system global area (SGA) backing file could not be allocated // using the system pagefile because the system-wide limit on // global pages has been exceeded. // *Action: Either increase the VMS system parameter GBLPAGFIL or use a disk // file as the SGA backing file. 07642, 00000, "smprtset: $CMKRNL failure" // *Cause: While attempting to set the protection of a region of memory, // an error was returned from the $CMKRNL system service. // *Action: Examine the system error message and refer to VMS documentation. 07643, 00000, "smsalo: SMSVAR is invalid" // *Cause: an internal error // *Action: Report this error to ORACLE customer support, provide your // init.ora file. 07645, 00000, "sszfsl: $CHANGE_CLASS failure" // *Cause: While attempting to set the label on a file, SEVMS service // $CHANGE_CLASS failed. // *Action: Examine the system message and refer to SEVMS system documentation. 07646, 00000, "sszfck: $CREATE failure" // *Cause: While attempting to create a file, VMS system service $CREATE // failed. // *Action: Examine the system message and refer to VMS system documentation. 07647, 00000, "sszfck: $OPEN failure" // *Cause: While attempting to reopen a file, VMS system service $OPEN failed. // *Action: Examine the system message and refer to VMS system documentation. 07650, 00000, "sigunc: $GETJPIW failure" // *Cause: While attempting to get the user's terminal device name, // user name, user program name, or process name // during logon, VMS system service $GETJPIW failed. // *Action: Examine the system error message and refer to VMS documentation. 07655, 00000, "slsprom:$TRNLOG failure" // *Cause: While attempting to translate SYS$INPUT during a prompt for // a password, VMS system service $TRNLOG failed. // *Action: Examine the system error message and refer to VMS documentation. 07656, 00000, "slsprom:$GETDVI failure" // *Cause: While attempting to get device characteristics during a prompt // for a password, VMS system service $GETDVI failed. // *Action: Examine the system error message and refer to VMS documentation. 07657, 00000, "slsprom:$ASSIGN failure" // *Cause: While prompting for a password, VMS system service $ASSIGN failed. // *Action: Examine the system error message and refer to VMS documentation. 07658, 00000, "slsprom:$QIOW read failure" // *Cause: While prompting for a password, VMS system service $QIOW failed. // *Action: Examine the system error message and refer to VMS documentation. 07665, 00000, "ssrexhd: recursive exception encountered %s %s %s %s %s %s" // *Cause: A VMS exception occurred while executing in the ORACLE exception // handler. The message includes the signal number, first and second // signal arguments, and exception PC, PSL and R0. This is an // internal error. // *Action: Contact your customer support representative. 07670, 00000, "$IDTOASC failed translating a secrecy category" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of a secrecy category. // *Action: Define the entry in the rights database which the binary label // you specified references. 07671, 00000, "$IDTOASC failed translating an integrity category" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of an integrity category. // *Action: Define the entry in the rights database which the binary label // you specified references. 07672, 00000, "$PARSE_CLASS failed translating the string into a binary label" // *Cause: SEVMS system service $PARSE_CLASS failed because the given // string did not represent a valid classification. // *Action: Examine system error message and refer to SEVMS documentation. 07680, 00000, "sou2os: another call to ORACLE currently executing" // *Cause: A call to the ORACLE shared image entry point occurred from within // the shared image. This is an internal error. // *Action: Contact your customer support representative. 07681, 00000, "sou2os: An error occurred while initializing Oracle" // *Cause: While attempting to set up the dispatch vectors for the shared // image, an error occurred. This is an internal error. // *Action: Contact your customer support representative. 07682, 00000, "sou2os: set kernel dispatch fail err" // *Cause: During ORACLE shared image entry, a dispatch to kernel mode // failed. // *Action: Make sure that your shared image is installed with the CMKRNL // privilege, then contact your customer support representative. 07683, 00000, "sou2os: $SETPRV reset error" // *Cause: During an attempt to restore user privileges at ORACLE shared // image exit, VMS system service $SETPRV failed. This is an // internal error. // *Action: Contact your customer support representative. 07684, 00000, "sou2os: supervisor stack reset error" // *Cause: During an attempt to restore the supervisor-mode stack at // ORACLE shared image exit, VMS system service $SETSTK failed. // This is an internal error. // *Action: Contact your customer support representative. 07685, 00000, "sou2os: supervisor stack set error" // *Cause: During an attempt to set the ORACLE supervisor-mode stack // at ORACLE shared image entry, VMS system service $SETSTK failed. // This is an internal error. // *Action: Contact your customer support representative. / / 7700 - 7720: sksarch errors / 07700, 00000, "sksarch: interrupt received" // *Cause: An interrupt was received while archiving the logs // *Action: Retry operation 07701, 00000, "sksatln: internal exception: output buffer too small" // *Cause: Overflow of buffer for parsing archive control text string // *Action: This is an internal error, please report to Oracle 07702, 00000, "unrecognized device type in archive text" // *Cause: Unrecognized device type in archive text // *Action: This is an internal error, please report to Oracle 07703, 00000, "error in archive text: need '/' after device type" // *Cause: The archive control text in the ARCHIVE command is invalid; // the device type (to indicate a file or tape) must be followed // by a '/'. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07704, 00000, "error in archive text: need ':' after device name" // *Cause: The archive control text in the ARCHIVE command is invalid; // the device name must be followed by a ':'. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07705, 00000, "sksaprs: device name buffer too small" // *Cause: The buffer supplied for the device name is too small. This is // an internal error. // *Action: Contact your customer support representative. 07706, 00000, "error in archive text: need disk file name" // *Cause: The archive control text in the ARCHIVE command is invalid; // the disk file name is missing. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07707, 00000, "error in archive text: need tape label name" // *Cause: The archive control text in the ARCHIVE command is invalid; // the tape label name is missing. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07708, 00000, "sksaprs: tape label name buffer too small" // *Cause: The buffer supplied for the tape label is too small. This is // an internal error. // *Action: Contact your customer support representative. 07709, 00000, "sksaprs: archiving to a remote host is not allowed" // *Cause: The user specified a remote disk for archiving via DECnet. // *Action: Archive to a disk on the local host. 07710, 00000, "sksaprs: file name buffer too small" // *Cause: The buffer supplied for the file name is too small. This is // an internal error. // *Action: Contact your customer support representative. 07713, 00000, "sksamtd: could not mount archival device (SYS$MOUNT failure)" // *Cause: VMS system service SYS$MOUNT failed // *Action: Examine system error message and refer to VMS documentation 07715, 00000, "sksadtd: could not dismount archival device (SYS$DISMNT failure)" // *Cause: VMS system service SYS$DISMNT failed // *Action: Examine system error message and refer to VMS documentation 07716, 00000, "sksachk: invalid device specification for ARCHIVE" // *Cause: VMS system service SYS$GETDVI failed" // *Action: Specify a valid device in ARCHIVE control string 07717, 00000, "sksaalo: error allocating memory" // *Cause: VMS system service LIB$GET_VM failed" // *Action: Examine system error message and refer to VMS documentation 07718, 00000, "sksafre: error freeing memory" // *Cause: VMS system service LIB$FREE_VM failed" // *Action: Examine system error message and refer to VMS documentation / / 7721-7729 scg overflow errors / 07721, 00000, "scgcm: not enough OS resource to obtain system enqueue" // *Cause: A call to sys$enq returned an error indicating that the operating // system lacked the resources necessary to create a lock. This is // caused by the messages SS$_EXENQLM or SS$_INSFMEM. // *Action: Free up some of the required resource to allow the creation of the // required lock. / / 7740 - 7760 error message file errors 07740, 00000, "slemop: incorrect handle size (programming error)" // *Cause: structures used for reading error message files do not match // *Action: this is an internal error, please report to Oracle 07741, 00000, "slemop: $OPEN failure" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07742, 00000, "slemop: $CONNECT failure" // *Cause: VMS system service $CONNECT failed // *Action: Examine system error message and refer to VMS documentation 07743, 00000, "slemop: incorrect error file attributes" // *Cause: An error message file is of incorrect format // *Action: Unless an error file has been changed, report this to Oracle 07744, 00000, "slemcl: invalid error message file handle" // *Cause: seal in passed in handle does not match correct value // *Action: this is an internal error, please report to Oracle 07745, 00000, "slemcl: $CLOSE failure" // *Cause: VMS system service $CLOSE failed // *Action: Check system error and refer to VMS documentation 07746, 00000, "slemrd: invalid error message file handle" // *Cause: seal in passed in handle does not match correct value // *Action: this is an internal error, please report to Oracle 07747, 00000, "slemrd: $READ failure" // *Cause: VMS system service $READ failed // *Action: Check system error and refer to VMS documentation 07750, 00000, "slemcr: fopen failure" // *Cause: An attempt to create a message file failed. This is an // internal error. // *Action: Contact your customer support representative. 07751, 00000, "slemcr: malloc failure" // *Cause: An attempt to allocate a cache for a newly-created message // file failed. This is an internal error. // *Action: Contact your customer support representative. 07753, 00000, "slemcf: fseek before write failure" // *Cause: An attempt to seek before writing a message file cache // element failed. This is an internal error. // *Action: Contact your customer support representative. 07754, 00000, "slemcf: fwrite failure" // *Cause: An attempt to write a message file cache element failed. // This is an internal error. // *Action: Contact your customer support representative. 07755, 00000, "slemcf: fseek before read failure" // *Cause: An attempt to seek before reading a message file cache // element failed. This is an internal error. // *Action: Contact your customer support representative. 07756, 00000, "slemcf: fread failure" // *Cause: An attempt to read a message file cache element failed. // This is an internal error. // *Action: Contact your customer support representative. 07757, 00000, "slemcc: invalid handle" // *Cause: The seal in a passed-in handle does not match correct value. // This is an internal error. // *Action: Contact your customer support representative. 07758, 00000, "slemcw: invalid handle" // *Cause: The seal in a passed-in handle does not match correct value. // This is an internal error. // *Action: Contact your customer support representative. 07759, 00000, "slemtr: invalid destination" // *Cause: The destination string provided to the function is too short // This is an internal error. // *Action: Contact your customer support representative. 07760, 00000, "slemtr: $open failure" // *Cause: the $open service failed. This is an internal error // *Action: Contact your customer support representative. 07800, 00000, "slbtpd: invalid number" // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed 07801, 00000, "slbtpd: invalid exponent" // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed 07802, 00000, "slbtpd: overflow while converting to packed decimal" // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed 07803, 00000, "slpdtb: invalid packed decimal nibble" // *Cause: An impossible request for decimal to binary conversion was made // *Action: This conversion cannot be performed 07804, 00000, "slpdtb: number too large for supplied buffer" // *Cause: An impossible request for decimal to binary conversion was made // *Action: This conversion cannot be performed / / 7820-7839 SSP error messages / 07820, 0000, "sspscn: SYS$CRELNM failure" // *Cause: An error was returned from the SYS$CRELNM function // *Action: Check system error and refer to VMS documentation 07821, 0000, "sspsdn: SYS$DELLNM failure" // *Cause: An error was returned from the SYS$DELLNM function // *Action: Check system error and refer to VMS documentation 07822, 0000, "sspscm: SYS$CREMBX failure" // *Cause: An error was returned from the SYS$CREMBX function while // trying to create the process dump mailbox. // *Action: Check system error and refer to VMS documentation 07823, 0000, "sspsqr: $QIO failure" // *Cause: An error was returned from $QIO while trying to // queue a read to the process dump mailbox. // *Action: Check system error and refer to VMS documentation 07824, 0000, "sspain: $SETIMR failure" // *Cause: An error was returned from SYS$SETIMR while trying to // queue a process spin-watch timer. // *Action: Check system error and refer to VMS documentation 07825, 0000, "sspsck: $QIO failure at AST level" // *Cause: An error was returned from SYS$QIO while trying to // read the process dump mailbox. // *Action: Check system error and refer to VMS documentation 07826, 0000, "sspscm: SYS$GETDVIW failure" // *Cause: An error was returned from SYS$GETDVIW while trying to // get information about the process dump mailbox. // *Action: Check system error and refer to VMS documentation / / 7840-7859 SLLF error messages / 07840, 0000, "sllfop: LIB$GET_VM failure" // *Cause: An error was returned from LIB$GET_VM while attempting to // allocate memory for an i/o vector. // *Action: Check system error and refer to VMS documentation 07841, 0000, "sllfop: SYS$OPEN failure" // *Cause: An error was returned from SYS$OPEN while attempting to // open the data file for reading // *Action: Check system error and refer to VMS documentation 07842, 0000, "sllfcl: SYS$CLOSE failure" // *Cause: An error was returned from SYS$CLOSE while attempting to // close the input data file // *Action: Check system error and refer to VMS documentation 07843, 0000, "sllfcl: LIB$FREE_VM failure" // *Cause: An error was returned from LIB$FREE_VM while attempting to // free the memory for the i/o vector // *Action: Check system error and refer to VMS documentation 07844, 0000, "sllfop: LIB$GET_VM failure" // *Cause: An error was returned from LIB$GET_VM while attempting to // allocate memory for data and index buffers // *Action: Check system error and refer to VMS documentation 07845, 0000, "sllfcl: LIB$FREE_VM failue" // *Cause: An error was returned from LIB$FREE_VM while attempting to // free memory used by data and index buffers // *Action: Check system error and refer to VMS documentation 07846, 0000, "sllfop: %s byte record too big for %s byte user buffer" // *Cause: The longest record in the file will not fit into the // largest data buffer that can be allocated // *Action: Modify the RMS file to have smaller records 07847, 0000, "sllfop: $CONNECT failure" // *Cause: An error was returned by SYS$CONNECT while attempting // to open the data file // *Action: Check system error and refer to VMS documentation 07848, 0000, "sllfrb: $GET failure" // *Cause: An error was returned by SYS$GET while attempting // to read the data file // *Action: Check system error and refer to VMS documentation 07849, 0000, "sllfsk: $GET failure" // *Cause: An error was returned by SYS$GET while attempting to // skip records in the input file // *Action: Check system error and refer to VMS documentation 07850, 0000, "sllfop: bad option" // *Cause: You are using a bad option to loader // Fixed= is one legal option. Check documentation for others. // *Action: Check documentation 07860, 0000, "osnsoi: error setting up interrupt handler" // *Cause: An error occurred while setting up the control interrupt handler // *Action: This is an internal error. Contact your Oracle representative. / / 7861 - 7879 Overflow error messages for sf / 07861, 0000, "sfqio: cannot write to file opened in read-only mode" // *Cause: A write operation was attempted on a file opened in read-only mode. // *Action: Do not open the file in read-only mode. 07862, 0000, "sfqio: cannot expand the file" // *Cause: The size of a file could not be expanded. // *Action: Check for additional error messages and contact your customer // support representative. / / 7880 - 7889 Error message for sd / 07880, 0000, "sdopnf: internal error" // *Cause: A list of all files open by this process could not be obtained. // *Action: This is an internal error. Contact your customer support // representative. / / 8000 - 8174 Data layer error messages / 08000, 00000, "maximum number of session sequence lists exceeded" // *Cause: the sequence parent state objects for this session are all used // *Action: an internal error; quit the session and begin a new one 08001, 00000, "maximum number of sequences per session exceeded" // *Cause: the limit on the number of sequences usable by session has been hit // *Action: increase init.ora parameter user_sequences to get more 08002, 00000, "sequence %s.CURRVAL is not yet defined in this session" // *Cause: sequence CURRVAL has been selected before sequence NEXTVAL // *Action: select NEXTVAL from the sequence before selecting CURRVAL 08003, 00000, "sequence %s.NEXTVAL exceeds internal limits" // *Cause: The sequence was created with unsafe values for some of the // parameters. The calculation of NEXTVAL cannot be made because it // exceeds the legal represention size. // *Action: Alter or recreate the sequence number with legal limits. 08004, 00000, "sequence %s.NEXTVAL %s %sVALUE and cannot be instantiated" // *Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE // *Action: alter the sequence so that a new value can be requested 08005, 00000, "specified row does not exist" // *Cause: A row with the given rowid does not exist in any of the tables given // *Action: check the query for misspellings of table names and the rowid 08006, 00000, "specified row no longer exists" // *Cause: the row has been deleted by another user since the operation began // *Action: re-try the operation 08008, 00000, "another instance is mounted with USE_ROW_ENQUEUES = %s" // *Cause: the shared instance being started does not have the same value // for use_row_enqueues as already running instances // *Action: ensure that all instances' init.ora files specify the same value // for the parameter 'use_row_enqueues' 08100, 00000, "index is not valid - see trace file for diagnostics" // *Cause: Validate Index detected an inconsistency in its argument index // *Action: Send trace file to your customer support representative 08101, 00000, "index key does not exist root dba %s, dba %s (%s)" // *Cause: Internal error: possible inconsistency in index // *Action: Send trace file to your customer support representative, along // with information on reproducing the error 08102, 00000, "index key not found, obj# %s, dba %s (%s)" // *Cause: Internal error: possible inconsistency in index // *Action: Send trace file to your customer support representative, along // with information on reproducing the error 08103, 00000, "object no longer exists" // *Cause: the object has been deleted by another user since the operation // began // *Action: / / 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. / / 8200 - 8399 Reserved for NCUBE OSD errors / 08200, 00000, "scggc: failed to open lock" // *Cause: The lock manager failed to open a lock. // *Action: Check if enough memory is available and retry the operation. 08201, 00000, "scggc: failed to convert lock" // *Cause: The lock manager failed to convert a lock. // *Action: Retry the operation. 08202, 00000, "scgcc: failed to close lock" // *Cause: The lock manager encountered an error closing a lock. // *Action: Check the lock manager status returned as additional information. 08203, 00000, "scgcan: failed to cancel a pending convert request" // *Cause: The lock manager encountered an error cancelling a convert request. // *Action: Check the lock manager status returned as additional information. 08204, 00000, "scgcm: unexpected lock manager return code" // *Cause: The lock manager returned an unexpected value. // *Action: Check the lock manager status returned as additional information. 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. 08211, 00000, "sfgcwd: Current working directory could not be obtained" // *Cause: The pathname for the current directory could not be obtained." // *Action: This should not occur in normal Oracle operation. Contact support. 08212, 00000, "sfphys: Cannot translate filename" // *Cause: A filename could not be translated. // *Action: Check the translation error returned as additional information. 08213, 00000, "sfphys: Cannot stat filename" // *Cause: Oracle could not obtain information about a specified file. // *Action: Check the Unix errno returned as additional information. 08214, 00000, "sfccf: SID too long" // *Cause: The ORACLE_SID environment variable is too long. // *Action: Check that ORACLE_SID is properly set or use a shorter SID. 08215, 00000, "sfccf: Invalid logical block size" // *Cause: Oracle attempted to create a file with an invalid block size. // *Action: Check that your init.ora parameters specify valid block sizes. 08216, 00000, "sfccf: Cannot translate filename" // *Cause: A filename could not be translated. // *Action: Check the translation error returned as additional information. 08217, 00000, "sfccf: Cannot reuse file" // *Cause: Oracle could not open a database file for reuse. // *Action: Check the Unix errno returned as additional information. 08218, 00000, "sfccf: Cannot create file; file exists" // *Cause: Oracle could not create a file because the file already existed. // *Action: Remove the file or specify the REUSE keyword. 08219, 00000, "sfccf: Cannot create file" // *Cause: Oracle could not create a file. // *Action: Check the Unix errno returned as additional information. 08220, 00000, "sfccf: Create for reuse failed" // *Cause: Oracle could neither open nor create a file. // *Action: Check the Unix errno returned as additional information. 08221, 00000, "sfccf: Internal error; illegal use option" // *Cause: Oracle failed on an internal consistency check. // *Action: Contact customer support. 08222, 00000, "sfccf: Cannot fstat file" // *Cause: Oracle could not obtain information about an open file. // *Action: Check the Unix errno returned as additional information. 08223, 00000, "sfccf: Invalid file size when creating for reuse" // *Cause: Oracle found an existing file whose length differs from // that specified on the CREATE REUSE command. // *Action: Remove the file or change the length specified on the // CREATE REUSE command. 08224, 00000, "sfccf: Invalid logical block size" // *Cause: Oracle attempted to create a file with an invalid block size. // *Action: Check that your init.ora parameters specify valid block sizes. 08225, 00000, "sfccf: Cannot ftruncate file" // *Cause: Oracle could not truncate a created file to its desired length. // *Action: Check the Unix errno returned as additional information. 08226, 00000, "sfccf: Erase failed" // *Cause: Oracle could not erase an existing file. // *Action: Check the Unix errno returned as additional information. 08227, 00000, "sfifi: Cannot translate filename" // *Cause: A filename could not be translated. // *Action: Check the translation error returned as additional information. 08228, 00000, "sfifi: Cannot stat filename" // *Cause: Oracle could not obtain information about a specified file. // *Action: Check the Unix errno returned as additional information. 08229, 00000, "sfifi: Invalid logical block size" // *Cause: The logical block size used when identifying a file is incompatible // with the physical block size supported by the file system. // *Action: Check that your init.ora parameters specify valid block sizes. / / Additional sf.c errors appear below. / 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 Reserved 08240, 00000, "snlmatt: parallel server name too long" // *Cause: The file name of the lock manager address file is too long. // *Action: Use a shorter parallel server name. 08241, 00000, "snlmatt: cannot attach to lock manager" // *Cause: Failed to attach to lock manager, perhaps because it's not running. // *Action: Additional information is lock manager return code. Check that // lock manager is running. 08242, 00000, "snlmdet: cannot detach from lock manager" // *Cause: An error was encountered detaching from the lock manager. // *Action: Additional information is lock manager return code. Contact // your customer support representative. 08243, 00000, "soarch: 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. 08244, 00000, "soarch: cannot open online log file for reading" // *Cause: The online log file cannot be opened. // *Action: Check file existence and permissions. Additional information // gives scf_open return value. 08245, 00000, "soarch: cannot create archive destination file" // *Cause: The archive destination file does not exist, and cannot be created. // *Action: Check directory permissions. Additional information gives // scf_create return code. 08246, 00000, "soarch: cannot open archive destination file for write" // *Cause: The destination file cannot be written. // *Action: Check file existence and permissions. Additional information // gives scf_create return value. 08247, 00000, "soarch: cannot connect to archive server" // *Cause: The archive server is not registered with the nameserver. // *Action: Check that the archive server is registered. Additional // information tells which archive server cannot be found. 08248, 00000, "soarch: archive server failure" // *Cause: An archive server returned failure. // *Action: Additional information gives the process-ID of the failing // archive server, and its status return value. 08249, 00000, "soarch: failed sending piece to server" // *Cause: An archive server failed to archive a piece. // *Action: Contact your customer support representative. 08250, 00000, "soarch: ORACLE_PSRV undefined" // *Cause: The parallel server name ORACLE_PSRV was undefined. // *Action: Define ORACLE_PSRV and retry. 08251, 00000, "soarch: archival interupted" // *Cause: Either a contol-C or a system shutdown in progress // *Action: none /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. 08262, 00000, "ora_addr: ORACLE_PSRV undefined" // *Cause: The parallel server name ORACLE_PSRV was undefined. // *Action: Set the environment variable ORACLE_PSRV and try again. 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, "soachk: Illegal archival control string" // *Cause: Archive files cannot be created with the given archival control // string. // *Action: Check that the volume exists 08271, 00000, "soabln: 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. 08272, 00000, "soarch: 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. / 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. 08279, 00000, "sfsrd: Cannot seek to read location" // *Cause: Oracle could not seek to the address of a block to be read. // *Action: The Unix errno, block number, and block size are returned // as additional information. 08281, 00000, "sfofi: Cannot open file" // *Cause: Oracle could not open a file. // *Action: Check the Unix errno returned as additional information. 08282, 00000, "sfcfi: Cannot close file" // *Cause: Oracle could not close a file. // *Action: Check the Unix errno. Contact customer support. 08283, 00000, "sfrfb: Invalid block number; internal error" // *Cause: Oracle tried to read from a non-existant location. // *Action: Contact customer support. 08284, 00000, "sfrfb: Buffer is unaligned; internal error" // *Cause: Oracle tried to read data into an incorrectly aligned buffer. // *Action: Contact customer support. 08285, 00000, "sfrfb: Cannot seek to read location" // *Cause: Oracle could not seek to the address of a block to be read. // *Action: The Unix errno, block number, and block size are returned // as additional information. 08286, 00000, "sfrfb: Read failed" // *Cause: Oracle could not read data from disk. // *Action: The Unix errno, block number, and number of blocks being read // are returned as additional information. 08287, 00000, "sfcmf: Cannot translate target filename" // *Cause: The target filename could not be translated when comparing. // *Action: Check the translation error returned as additional information. 08288, 00000, "sfcmf: Cannot translate source filename" // *Cause: The source filename could not be translated when comparing. // *Action: Check the translation error returned as additional information. 08289, 00000, "sfcopy: Files have different block sizes" // *Cause: An attempt was made to copy between two files with differing // logical block sizes. // *Action: The logical block sizes of the source and destination files // are returned. 08290, 00000, "sfcopy: Cannot malloc buffer for copy" // *Cause: A buffer could not be allocated for copying between to files. // *Action: Free up storage by killing processes, reducing the SGA, etc. 08291, 00000, "sfcopy: Read failed while copying" // *Cause: Oracle could not read from disk while copying between two files. // *Action: Check the error code returned as additional information. 08292, 00000, "sfcopy: Write failed while copying" // *Cause: Oracle could not write to disk while copying between two files. // *Action: Check the error code returned as additional information. 08293, 00000, "sfnfy: ulimit failed" // *Cause: The ulimit() system called failed. // *Action: Contact customer support. 08294, 00000, "sfsrd: Invalid block number; internal error" // *Cause: Oracle tried to read from a non-existant location. // *Action: Contact customer support. 08295, 00000, "sfsrd: Read is too large" // *Cause: A request was made to read more blocks than could be handled. // *Action: Verify init.ora parameters. Additional information is the // block number and number of blocks. 08296, 00000, "sfsrd: Read failed" // *Cause: Oracle could not read data from disk. // *Action: Additional information is the Unix errno, block number, and // number of blocks being read. 08297, 00000, "sfsrd: read returned incorrect number of bytes" // *Cause: Possible truncated read of database file. // *Action: Check additional information, which is block number, number // of blocks requested, and number of bytes read. 08298, 00000, "sfsync: Gigacache sync failed" // *Cause: Oracle could not flush dirty Gigacache blocks to disk. // *Action: Check the Unix errno returned as additional information. 08299, 00000, "sfsync: Gigacache file sync failed" // *Cause: Oracle could not flush dirty Gigacache blocks to disk for a file. // *Action: Check the Unix errno returned as additional information. 08300, 00000, "sfq_clean1: Asynchronous I/O failed" // *Cause: An asynchronous read or write operation failed. // *Action: Check the Unix errno returned as additional information. 08301, 00000, "sfdone: Asynchronous I/O failed" // *Cause: One or more requests in a batch of asynchronous I/Os failed. // *Action: Check the Unix errno returned as additional information. 08302, 00000, "sfqio: internal error" // *Cause: Oracle failed on an internal consistency check. // *Action: Contact customer support. 08303, 00000, "sfqio: Cannot malloc asynchronous I/O vector" // *Cause: Oracle could not allocate storage need for an I/O operation. // *Action: Check init.ora parameters to reduce I/O request sizes. 08304, 00000, "sfqio: Invalid block number; internal error" // *Cause: Oracle tried to read from or write to a non-existant location. // *Action: Contact customer support. 08305, 00000, "sfqio: Buffer is unaligned; internal error" // *Cause: Oracle tried to read to/write from an incorrectly aligned buffer. // *Action: Contact customer support. 08306, 00000, "sfqio: Cannot set I/O control flags" // *Cause: An error occurred trying to set I/O control flags. // *Action: Check the Unix errno returned as additional information. 08307, 00000, "sfqio: Cannot issue asynchronous I/O request" // *Cause: An asynchronous I/O request operation could not be issued. // *Action: Check the Unix errno returned as additional information. 08308, 00000, "sllfop: Cannot open file" // *Cause: Oracle could not open a file. // *Action: Check the Unix errno returned as additional information. 08309, 00000, "sllfop: Cannot fstat file" // *Cause: Oracle could not obtain information about an open file. // *Action: Check the Unix errno returned as additional information. 08310, 00000, "sllfop: Bad value for recsize" // *Cause: An illegal value for the record size was specified. // *Action: Specify a value for the recsize option that is greater than 0. 08311, 00000, "sllfop: bad value for maxrecsize" // *Cause: An illegal value for the maximum record size was specified. // *Action: Specify a value for the maxrecsize option that is greater // than 0. 08312, 00000, "sllfop: unrecognized processing option" // *Cause: An unrecognized processing option was specified. // *Action: Check the Oracle for nCUBE 2 User's Guide for valid options. 08313, 00000, "sllfop: could not allocate buffers" // *Cause: Memory for the load buffers could not be allocated. // *Action: Reduce the maximum record size. Eliminate any unnecessary // processes on your current node before running SQL*Loader again. 08314, 00000, "sllfcf: Error closing file" // *Cause: An error occurred trying to close a file. // *Action: Check the Unix errno returned as additional information. 08315, 00000, "sllfrb: Error reading file" // *Cause: An error occurred trying to read from a file. // *Action: Check the Unix errno returned as additional information. 08316, 00000, "sllfsk: Error seeking in file." // *Cause: The lseek system call returned an error. // *Action: Check the Unix errno returned as additional information. 08317, 00000, "sllfsk: Error seeking in file." // *Cause: The lseek system call returned an error. // *Action: Check the Unix errno returned as additional information. 08318, 00000, "sllfsk: Error reading file" // *Cause: An error occurred trying to read from a file. // *Action: Check the Unix errno returned as additional information. 08319, 00000, "sllfsk: Error reading file" // *Cause: An error occurred trying to read from a file. // *Action: Check the Unix errno returned as additional information. / / 8320 - 8329 Reserved for scn.c 08320, 00000, "scnget: Call to scnget before scnset or scnfnd." // *Cause: An internal error // *Action: Contact your customer support representative. 08321, 00000, "scnmin: NOT IMPLEMENTED YET" // *Cause: An internal error // *Action: Contact your customer support representative. 08322, 00000, "scnmin: open/convert of bias lock failed" // *Cause: A call to the lkmgr failed to open and convert the bias lock // *Action: Check to make sure the lkmgr is up. 08323, 00000, "scnmin: close of bias lock failed" // *Cause: A call to the lkmgr failed to close the bias lock // *Action: Check to make sure the lkmgr is up. 08330, 00000, "Printing not supported" // *Cause: An attempt was made to automatically spool a file to the printer // *Action: none 08331, 00000, "Wait operation timed out" // *Cause: Oracle timed out waiting for an event // *Action: Contact your Oracle support representative 08332, 00000, "rollback segment #%s specified not available" // *Cause: (same as 1545) // *Action: (same as 1545). Also, make sure you have created enough rollback // segments for the number of instances you are trying to start. / / 8340-8359 Reserved for nCUBE redo server errors / 08340, 00000, "This command not allowed on nCUBE, only one thread is ever used." // *Cause: An illegal command was executed for the nCUBE platform. // *Action: There is no need to issue this command. 08341, 00000, "On nCUBE, this command can only be executed from instance 1." // *Cause: A command that can only be issued on instance 1 was issued elsewhere. // *Action: Log on to instance 1 and repeat the command. 08342, 00000, "sropen: failed to open a redo server connection" // *Cause: An error occurred trying to connect to the redo server. // *Action: The OS specific error message should tell you what to do. 08343, 00000, "srclose: failed to close a redo server connection" // *Cause: An error occurred trying to close the redo server connection. // *Action: The OS specific error message should tell you what to do. 08344, 00000, "srapp: failed to send redo data to the redo server" // *Cause: An error occurred trying to send redo to the redo server. // *Action: The OS specific error message should tell you what to do. / / 8363 - 8399 Reserved for nCUBE sosd errors (unassigned) / 08360, 00000, "sfccf: Illegal file type." // *Cause: Cannot initialize a file of illegal file type. // *Action: Verify that your file name is correct. The supported file types // are raw devices and regular files. 8361, 00000, "sfccf: No space left on raw device." // *Cause: There is not enough space on the raw device. // *Action: Use a larger device or a smaller file. 8362, 00000, "scgcm: Out of memory in lock manager." // *Cause: The lock manager ran out of memory. // *Action: Reduce the number of locks specified in the gc_db_locks init.ora // parameter or increase the number of lock manager processes. / / 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 / / MODIFIED: / png 12/01/94 - V7.01.06: / 8468 replaces 8421-24 / 8466 replaces 8425-28, 8461 / 8467 replaces 8406-8411, 8438, 8439, 8442 / 8401 replaces 8401-8405 / 8435 revised / 8414 added / cddavis 10/09/94 - deleted comments with kkxg references / cddavis 10/09/94 - header prefixed to us version of pirg msgs / 08401, 00000, "invalid compiler name: %s" // *Cause: An invalid compiler name was passed to a UTL_PG // conversion routine. // *Action: Correct the compiler name parameter in the PL/SQL code // that called the conversion routine. / 08412, 00000, "error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message" // *Cause: The WMSGBSIZ is the maximun size for warning message block, // it is recommanded to be 1024 bytes to 8 kbytes. // *Action: Defined WMSGBLK of size between 1k to 8k bytes and // update the WMSGBSIZ to the sizeof(WMSGBLK). / 08413, 00000, "invalid compiler type in FORMAT parameter at %s" // *Cause: An invalid compiler type is defined in format control block. // The format control block is invalid. // *Action: Check to be sure that the format parameter was built by // MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, // and that it was not accidentally overwritten or modified // by the PL/SQL procedure. / 08414, 00000, "error encountered in %s" // *Cause: The function returned an error. // Where may be: // RAW_TO_NUMER // NUMBER_TO_RAW // RAW_TO_NUMBER_FORMAT // NUMBER_TO_RAW_FORMAT // MAKE_NUMBER_TO_RAW_FORMAT // MAKE_RAW_TO_NUMBER_FORMAT // *Action: This message will be preceded by messages providing details // about the error. Check those messages to determine what // action to take. / 08429, 00000, "raw data has invalid digit in display type data" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine contained invalid data. The picture mask // parameter specified a digit, but the corresponding input // from the raw data did not contain a valid digit. // *Action: Either the input data is incorrect, or the picture mask // is incorrect. Correct the appropriate item. / 08430, 00000, "raw data missing leading sign" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine had no leading sign, but the mask // options parameter specified a leading sign. // *Action: Correct the input raw data or the mask options so that // they match. / 08431, 00000, "raw data missing zero as defined in picture" // *Cause: The picture mask parameter passed to a UTL_PG // RAW_TO_NUMBER conversion routine contained a zero, but // the corresponding input from the raw data was not a zero. // *Action: Either the input data is incorrect, or the picture mask // is incorrect. Correct the appropriate item. / 08432, 00000, "raw data has invalid floating point data" // *Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER // conversion routine contained invalid floating point data. // *Action: Correct the input raw data. / 08433, 00000, "invalid picture type in convert raw to number" // *Cause: The picture mask parameter passed to a UTL_PG // RAW_TO_NUMBER conversion routine contained non-numeric // characters, but the conversion was to a numeric data // type. // *Action: Correct the picture mask parameter. / 08434, 00000, "raw data has invalid trailing sign" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine had no trailing sign, but the mask // options parameter specified a trailing sign. // *Action: Correct the input raw data or the mask options so that // they match. / 08435, 00000, "PICTURE MASK missing the leading sign when SIGN IS LEADING specified" // *Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER // conversion routine had no leading sign, but the mask // options parameter specified a leading sign. // *Action: Correct the input raw data or the mask options so that // they match. / 08436, 00000, "raw data has invalid sign digit" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine had an invalid sign digit in the // position where the picture mask specified a sign. // *Action: Correct the input raw data or the picture mask so that // they match. / 08437, 00000, "invalid picture type in picture mask" // *Cause: The picture mask parameter passed to a UTL_PG // NUMBER_TO_RAW conversion routine contained non-numeric // characters, but the conversion was to a numeric data // type. // *Action: Correct the picture mask parameter. / 08440, 00000, "raw buffer is too short to hold converted data" // *Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW // conversion routine was not large enough to contain the // results of the conversion based on the picture mask. // *Action: Increase the raw buffer size to the size necessary to // hold the entire result of the conversion. / 08441, 00000, "closed parenthesis missing in picture mask" // *Cause: A closed parenthesis was missing from the picture mask // passed to a UTL_PG conversion routine. // *Action: Correct the picture mask. / 08443, 00000, "syntax error in BLANK WHEN ZERO clause in mask options" // *Cause: A syntax error was found in the BLANK WHEN ZERO clause in // the mask options parameter passed to a UTL_PG conversion // routine. Valid specifications are: // BLANK ZERO // BLANK ZEROS // BLANK ZEROES // BLANK WHEN ZERO // BLANK WHEN ZEROS // BLANK WHEN ZEROES // *Action: Correct the mask options parameter. / 08444, 00000, "syntax error in JUSTIFIED clause in mask options" // *Cause: A syntax error was found in the JUSTIFIED clause in the // mask options parameter passed to a UTL_PG conversion // routine. Valid specifications are: // JUST // JUST RIGHT // JUSTIFIED // JUSTIFIED RIGHT // *Action: Correct the mask options parameter. / 08445, 00000, "syntax error in SIGN clause in mask options" // *Cause: A syntax error was found in the SIGN clause in the mask // options parameter passed to a UTL_PG conversion routine. // Valid specifications are: // SIGN LEADING // SIGN LEADING SEPARATE // SIGN LEADING SEPARATE CHARACTER // SIGN TRAILING // SIGN TRAILING SEPARATE // SIGN TRAILING SEPARATE CHARACTER // SIGN IS LEADING // SIGN IS LEADING SEPARATE // SIGN IS LEADING SEPARATE CHARACTER // SIGN IS TRAILING // SIGN IS TRAILING SEPARATE // SIGN IS TRAILING SEPARATE CHARACTER // *Action: Correct the mask options parameter. / 08446, 00000, "syntax error in SYNCHRONIZED clause in mask options" // *Cause: A syntax error was found in the SYNCHRONIZED clause in the // mask options parameter passed to a UTL_PG conversion // routine. Valid specifications are: // SYNC // SYNC LEFT // SYNC RIGHT // SYNCHRONIZED // SYNCHRONIZED LEFT // SYNCHRONIZED RIGHT // *Action: Correct the mask options parameter. / 08447, 00000, "syntax error in USAGE clause in mask options" // *Cause: A syntax error was found in the USAGE clause in the mask // options parameter passed to a UTL_PG conversion routine. // Valid specifications are: // USAGE DISPLAY // USAGE COMP // USAGE COMP-3 // USAGE COMP-4 // USAGE COMPUTATIONAL // USAGE COMPUTATIONAL-3 // USAGE COMPUTATIONAL-4 // USAGE IS DISPLAY // USAGE IS COMP // USAGE IS COMP-3 // USAGE IS COMP-4 // USAGE IS COMPUTATIONAL // USAGE IS COMPUTATIONAL-3 // USAGE IS COMPUTATIONAL-4 // *Action: Correct the mask options parameter. / 08448, 00000, "syntax error in DECIMAL-POINT environment clause" // *Cause: A syntax error was found in the DECIMAL-POINT environment // clause parameter passed to a UTL_PG conversion routine. // Valid specifications are: // DECIMAL-POINT IS COMMA // *Action: Correct the environment clause parameter. / 08449, 00000, "invalid numeric symbol found in picture mask" // *Cause: An invalid numeric symbol was found in the picture mask // parameter passed to a UTL_PG conversion routine. // *Action: Correct the picture mask parameter. / 08450, 00000, "invalid specification of CR in picture mask" // *Cause: The CR suffix was incorrectly specified in the picture mask // parameter passed to a UTL_PG conversion routine. The CR // suffix can only appear at the end of a picture mask. // *Action: Correct the picture mask parameter. / 08451, 00000, "invalid specification of DB in picture mask" // *Cause: The DB suffix was incorrectly specified in the picture mask // parameter passed to a UTL_PG conversion routine. The DB // suffix can only appear at the end of a picture mask. // *Action: Correct the picture mask parameter. / 08452, 00000, "specification of E in picture mask is unsupported" // *Cause: The floating point exponent symbol 'E' was specified in the // picture mask parameter passed to a UTL_PG conversion // routine. The floating point data type is currently not // supported by the UTL_PG conversion routines. // *Action: Correct the picture mask parameter, and the data, if // necessary. / 08453, 00000, "more than one V symbol specified in picture mask" // *Cause: The picture mask passed to a UTL_PG conversion routine // contained more than one decimal point indicator ('V'). // Only one decimal point indicator is allowed in the picture // mask. // *Action: Correct the picture mask parameter. / 08454, 00000, "more than one S symbol specified in picture mask" // *Cause: The picture mask passed to a UTL_PG conversion routine // contained more than one operational sign indicator ('S'). // Only one operational sign indicator is allowed in the // picture mask. // *Action: Correct the picture mask parameter. / 08455, 00000, "syntax error in CURRENCY SIGN environment clause" // *Cause: A syntax error was found in the CURRENCY SIGN environment // clause parameter passed to a UTL_PG conversion routine. // Valid specifications are: // CURRENCY SIGN IS x where x is a valid currency sign // *Action: Correct the environment clause parameter. / 08456, 00000, "no sign in picture mask but SIGN clause in mask options" // *Cause: The picture mask parameter passed to a UTL_PG conversion // routine contained no sign symbol ('S', '+', or '-'), but // the mask options parameter contained a SIGN clause. A sign // symbol is required in the picture mask parameter when the // mask options parameter contains a SIGN clause. // *Action: Correct the picture mask parameter or the mask options // parameter. / 08457, 00000,"syntax error in SEPARATE CHARACTER option of SIGN clause" // *Cause: A syntax error was found in the SEPARATE CHARACTER option // of the SIGN clause in the mask options parameter passed to // a UTL_PG conversion routine. Valid specifications are: // SEPARATE // SEPARATE CHARACTER // *Action: Correct the mask options parameter. / 08458, 00000, "invalid format parameter" // *Cause: The format parameter passed to a UTL_PG conversion routine // was invalid. The format parameter should have been built by // a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or // MAKE_NUMBER_TO_RAW_FORMAT. // *Action: Check to be sure that the format parameter was built by // MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, // and that it was not accidentally overwritten or modified // by the PL/SQL procedure. / 08459, 00000, "invalid format parameter length" // *Cause: The format parameter passed to a UTL_PG conversion routine // was not the correct length. Format parameters must be 2048 // bytes in length. // *Action: Check to be sure that the format parameter was built by // MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, // and that it was not accidentally overwritten or modified // by the PL/SQL procedure. / 08460, 00000, "invalid environment clause in environment parameter" // *Cause: The environment parameter passed to a UTL_PG conversion // routine contained an unsupported or invalid environment // clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS // COMMA environment clauses are supported. // *Action: Correct the environment parameter. / 08462, 00000, "raw buffer contains invalid decimal data" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine contains invalid decimal data. // *Action: Correct the input data. / 08463, 00000, "overflow converting decimal number to Oracle number" // *Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER // was not large enough to hold the Oracle number resulting // from the input decimal number. // *Action: Be sure that the input decimal number is valid, and besure // that the output variable is large enough to hold the Oracle // number value. / 08464, 00000, "input raw decimal data contains more than 42 digits" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine contained more than 42 digits. This // exceeds the maximum size of an Oracle number. // *Action: Correct the raw input buffer. / 08465, 00000, "input mask contains more than 32 characters" // *Cause: The input mask passed to UTL_PG numeric conversion // routine contained more the 32 characters. // *Action: Correct the mask input buffer. / 08466, 00000, "raw buffer length %s is too short for %s" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine was less than %s bytes long, but the // picture mask parameter specified that %s bytes of input data // were to be converted. // *Action: Either the input data is incorrect, or the picture mask // is incorrect. Correct the appropriate item. / 08467, 00000, "error converting Oracle number to %s" // *Cause: An error occurred when converting an Oracle number to a // COBOL of: // DISPLAY // COMP-3 // or character variable. // The Oracle number was not in the correct format. mat. // *Action: Correct the call to the conversion routine. The input // must be a valid Oracle number variable. / 08468, 00000, "mask option %s is not supported" // *Cause: The mask option was passed to a UTL_PG // conversion routine, but is not supported by UTL_PG. // The can be: // USAGE IS POINTER // USAGE IS INDEX // USAGE IS COMP-1 // USAGE IS COMP-2 // POINTER // *Action: Remove the from the mask options parameter // in the PL/SQL call to UTL_PG. / 08498, 00000, "Warning: picture mask '%s' overrides picture mask option 'USAGE IS %s' to 'USAGE IS DISPLAY'" // *Cause: Picture mask USAGE option was overridden by the picture mask. // *Action: This is an informational message only. The message may be // eliminated by changing the USAGE option to match the picture mask. / 08499, 00000, "Warning: picture mask options '%s' ignored by UTL_PG " // *Cause: Picture mask options such as OCCUR, SYNC and others are not // processed by the UTL_PG numeric conversion routines. // *Action: This is an informational message only. The message may be // eliminated by removing the unnecessary picture mask options // from the parameter list passed to the UTL_PG routine. / / / / End UTL_RAW and UTL_PG messages / / / 8401 - 8499 Reserved for APPC Gateway / / 8500 - 8599 Reserved for ??? sql*connnect errors / / 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 / / 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. 09707, 00000, "sfccf: 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. 09708, 00000, "soacon: failed to bind socket to port." // *Cause: The bind system call failed on the socket. // *Action: Check additional information for OS error. Try connecting again. 09709, 00000, "soacon: failed to accept a connection." // *Cause: The accept system call failed on the socket. // *Action: Check additional information for OS error. Try connecting again. 09710, 00000, "soarcv: buffer overflow." // *Cause: The internal buffer is not big enough to hold the message read. // *Action: Internal error. Contact customer support representative. 09711, 00000, "orasrv: archmon already connected." // *Cause: An existing connection has already been made from archmon to // orasrv. // *Action: Stop trying to connect. 09712, 00000, "orasrv: log archiver already connected." // *Cause: An existing connection has already been made from log archiver to // orasrv. // *Action: Stop trying to connect. 09713, 00000, "soadum: cannot do log archiving to tape." // *Cause: You are missing the necessary communication driver for the log // archiver to communicate with the console process. // *Action: Install the appropriate communication driver. 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. 09780, 00000, "sfifi: translation error, unable to expand instance name." // *Cause: Additional information indicates sltln error. // *Action: Check additional information. 09781, 00000, "sfifi: bad instance name stored in control file." // *Cause: The header block might have been corrupted. // *Action: Contact customer support. 09782, 00000, "sfifi: another instance has the same database mounted." // *Cause: In non-shared disk systems, database cannot be mounted shared. // *Action: Shutdown the other oracle instance and try again. The name // of the other instance was dumped to the trace file. 09783, 00000, "sfifi: Cannot determine if another instance has mounted the same database." // *Cause: Because of permission problems, could not check if the other // instance was up. // *Action: Check errno. Additional information indicates error in closing file 09784, 00000, "sfifi: lseek error, unable to seek to beginning of file." // *Cause: Lseek system call returned an error. // *Action: Check errno. Additional information indicates error in closing file. 09785, 00000, "sfifi: write error, unable to write header block." // *Cause: write system call returned an error. // *Action: Check errno. / / / 09786-09825 reserved for Loader V2.0 / 09786, 00000, "sllfop: open error, unable to open file." // *Cause: Open system call returned an error. // *Action: Check errno. 09787, 00000, "sllfop: unrecognizable processing option, incorrect format." // *Cause: Processing option passed is of incorrect format. // *Action: Consult your IUG for permissible formats. 09788, 00000, "sllfrb: unable to read file." // *Cause: Read system call returned an error. // *Action: Check errno. Verify file exists. 09789, 00000, "sllfsk: unable to read file." // *Cause: Read system call returned an error. // *Action: Check errno. Verify file exists. 09790, 00000, "sllfcf: unable to close file." // *Cause: Close system call returned an error. // *Action: Check errno. 09791, 00000, "slembdf: translation error, unable to translate error file name." // *Cause: Additional information indicates error returned from sltln. // *Action: Check additional information. 09792, 00000, "sllfop: cannot allocate read buffer." // *Cause: Malloc system call returned an error. The system might have run out // of heap space. // *Action: Check additional information for the OS error. 09793, 00000, "szguns: length of user name is greater than buffer." // *Cause: The length of the name of the user being looked up is longer than // size of the buffer provided by the calling routine. // *Action: This is an internal error. Contact ORACLE customer support. 09794, 00000, "szrbuild: length of role name is greater than buffer." // *Cause: The length of the name of the role being looked up is longer than // size of the buffer provided by the calling routine. // *Action: This is an internal error. Contact ORACLE customer support. 09795, 00000, "szrbuild: malloc of role structure failed." // *Cause: The allocation of memory for an internal structure used to // hold a role descriptor failed. // *Action: Check the UNIX error number for a possible operating system // failure. 09796, 00000, "szrbuild: malloc of role name failed." // *Cause: The allocation of memory for an internal buffer used to hold the // name of a role failed. // *Action: Check the UNIX error number for a possible operating system // failure. 09797, 00000, "Failed to get O/S MAC privileges." // *Cause: The operating system would not allow the retrieval of this // process' privileges. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09798, 00000, "Label comparison failed." // *Cause: The comparison of two binary labels failed. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09799, 00000, "File label retrieval failed." // *Cause: ORACLE was unable to get a label attached to a file. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09800, 00000, "Process sensitivity label retrieval failed." // *Cause: ORACLE was unable to get the sensitivity label for a process. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09801, 00000, "Unable to get user ID from connection" // *Cause: ORACLE was unable to retrieve the user's id number from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09802, 00000, "Conversion of binary label to string failed." // *Cause: ORACLE was unable to convert a binary label to a string. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09803, 00000, "Allocation of string buffer failed." // *Cause: a buffer used to hold the name of the file for which a label was // to be obtained could not be allocated. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. // The number of bytes that ORACLE attempted to allocate is in // the "Additional Information" field. 09804, 00000, "Class conversion from binary to ORACLE failed." // *Cause: ORACLE was unable to convert a class component from binary // format to ORACLE format. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09805, 00000, "conversion of category number to string failed." // *Cause: ORACLE was unable to translate a category number to its // corresponding string representation failed. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. The // category number is contained in the "Additional information" // field. 09806, 00000, "Allocation of label string buffer failed." // *Cause: a temporary buffer used to hold a label could not be allocated. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. // The number of bytes that ORACLE attempted to allocate is in // the "Additional Information" field. 09807, 00000, "Conversion of label from string to binary failed." // *Cause: ORACLE was unable to convert the string representation of a label // to binary format. // *Action: Re-enter a valid label. 09808, 00000, "Could not obtain user clearance." // *Cause: ORACLE was unable to get a user's clearance level. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09809, 00000, "Unable to get user's group ID from connection" // *Cause: ORACLE was unable to retrieve the user's group id number from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09810, 00000, "Unable to get process ID from connection" // *Cause: ORACLE was unable to retrieve the user's process id number from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE customer support. 09811, 00000, "Unable to initialize package." // *Cause: ORACLE was unable to initialize the library used to obtain // security information. // *Action: This is an internal error. Contact ORACLE support. 09812, 00000, "Unable to get user clearance from connection" // *Cause: ORACLE was unable to retrieve the user's operating system // session clearance from the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE customer support. 09813, 00000, "Unable to get directory status" // *Cause: ORACLE was unable to determine if a directory is multilevel. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09814, 00000, "Unable to expand file name" // *Cause: ORACLE was unable to expand the name of a file that resides // in multilevel directory. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09815, 00000, "File name buffer overflow" // *Cause: The buffer that ORACLE uses to hold the expanded name of a // too small. // *Action: This is an internal error. Contact ORACLE customer support. 09816, 00000, "Unable to set effective privileges" // *Cause: // *Action: This is an internal error. Contact ORACLE support. 09817, 00000, "Write to audit file failed." // *Cause: ORACLE was unable to write an entry to the file used as the // audit trail. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09818, 00000, "Number is too large" // *Cause: ORACLE was unable to convert a component string to a number because // the number is larger than the largest possible value for an // integer. The additional information field specifies the maximum. // *Action: Correct the string and repeat the conversion. 09819, 00000, "Number exceeds maximum legal value" // *Cause: the number specified for a component was greater than the maximum // value allowed for that component. // *Action: Change the component to a value less than the maximum and repeat // the conversion. The maximum component number is contained in the // "Additional information" field. 09820, 00000, "Conversion of class string to numeric representation failed." // *Cause: ORACLE was unable to convert a class string to a number because // all of the characters in the string were not numeric. // *Action: Change the string to be either all numbers or all non-numeric // characters and repeat the conversion. 09821, 00000, "Numeric label is not valid" // *Cause: A label specified in ORACLE numeric format was found not to be // valid. // *Action: Re-enter a valid label. Consult your system's encodings for valid // numeric component values. 09822, 00000, "Translation of audit file name failed." // *Cause: ORACLE was unable to translate the value of the // "audit_trail_dest" initialization parameter. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09823, 00000, "device name is too long" // *Cause: The name of a device was too long to fit into an internal buffer. // The additional information field contains the length of the device // name. // *Action: This is an internal error. Contact ORACLE support. 09824, 0000, "Unable to enable allowmacaccess privilege." // *Cause: ORACLE was not able to turn on allowmacaccess privilege so that it // could do a label comparison. // *Action: Check the UNIX error number. If it indicates that ORACLE does not // have the allowmacaccess privilege, add the allowmacaccess privilege // to the potential privilege set of $ORACLE_HOME/bin/oracle using // chpriv (1M). If the executable already has the allowmacaccess // privilege, contact ORACLE support. 09825, 0000, "Unable to disable allowmacaccess privilege." // *Cause: ORACLE was not able to turn off the allowmacaccess privilege after // doing a label comparison. // *Action: This is an internal error. Contact ORACLE support. 09826, 00000, "SCLIN: cannot initialize atomic latch." // *Cause: System call atomic_op() return error. // *Action: Check additional information in the trace file. 09827, 00000, "SCLGT: atomic latch return unknown error." // *Cause: System call atomic_op() return unexpected error. // *Action: Check additional information in the trace file. 09828, 00000, "SCLFR: atomic latch return error." // *Cause: System call atomic_op() return unexpected error. // *Action: Check additional information in the trace file. 09829, 00000, "pw_createPorts: server call pws_start_instance failed." // *Cause: The call pws_start_instance to (Oracle helper) failed; system // resources might be exhausted. // *Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. 09830, 00000, "snyAddPort: failed to perform a remote procedure call." // *Cause: The msg_rpc system call returned an error. // *Action: Internal error. Contact Oracle support. 09831, 00000, "snyStartThread: failed to build the server port set." // *Cause: The routine failed to build a port set on which to listen for // requests. // *Action: Possible operating system failure. Contact Oracle support. 09832, 00000, "infoCallback: bad message format." // *Cause: The routine received an incorrectly formatted request. // *Action: Internal error. Contact Oracle support. 09833, 00000, "addCallback: bad message format." // *Cause: The routine received an incorrectly formatted request. // *Action: Internal error. Contact Oracle support. 09834, 00000, "snyGetPortSet: failed to collect info on a port." // *Cause: The port_status system called failed. // *Action: Possible operating system error. Contact Oracle support. 09835, 00000, "addCallback: callback port is already in a set." // *Cause: The port to be added to the callback list is already in a port set. // *Action: Internal error. Contact Oracle support. 09836, 00000, "addCallback: could not add a port to the callback set." // *Cause: The port_set_add system called failed. // *Action: Possible operating system error. Contact Oracle support. 09837, 00000, "addCallback: could not add allocate a callback link." // *Cause: The malloc library call failed to allocate space for a callback link. // *Action: Possible operating system error. Contact Oracle support. 09838, 00000, "removeCallback: failure removing the callback port." // *Cause: The port port_set_remove system call failed. // *Action: Possible operating system error. Contact Oracle support. 09839, 00000, "removeCallback: callback port is not in the callback set." // *Cause: The port to be removed to the callback list is not in the // callback port set. // *Action: Internal error. Contact Oracle support. 09840, 00000, "soacon: Name translation failure." // *Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@. // *Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID // in oratab is correct. 09841, 00000, "soacon: Name translation failure." // *Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@. // *Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID // in oratab is correct. 09842, 00000, "soacon: Archmon unable to create named pipe." // *Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@. // *Action: Your current OS login may lack write permission for the // ORACLE_HOME/dbs directory. Only userids in the dba group of a // given instance can run archmon for that ORACLE_SID. Make sure // that the ORACLE_HOME directory is correct in oratab. 09843, 00000, "soacon: Archmon unable to create named pipe." // *Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@. // *Action: Your current OS login may lack write permission for the // ORACLE_HOME/dbs directory. Only userids in the dba group of a // given instance can run archmon for that ORACLE_SID. Make sure // that the ORACLE_HOME directory is correct in oratab. 09844, 00000, "soacon: Archmon unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/mon2arch_@. // *Action: Only the oracle dba can run archmon. Make sure that your // current OS login has owner or group search permission for the // ORACLE_HOME/dbs directory. The max number of open files may have // been exceeded. 09845, 00000, "soacon: Archmon unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/arch2mon_@. // *Action: Only the oracle dba can run archmon. Make sure that your // current OS login has owner or group search permission for the // ORACLE_HOME/dbs directory. The max number of open files may have // been exceeded. 09846, 00000, "soacon: ARCH unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/mon2arch_@. // *Action: Make sure that the OS userid of the currently running database // has search permission for the ORACLE_HOME/dbs directory. The max // number of open files may have been exceeded. 09847, 00000, "soacon: ARCH unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/arch2mon_@. // *Action: Make sure that the OS userid of the currently running database // has search permission for the ORACLE_HOME/dbs directory. The max // number of open files may have been exceeded. 09848, 00000, "soawrt: Unable to write to named pipe." // *Cause: // *Action: 09849, 00000, "soarcv: Unable to read from named pipe." // *Cause: // *Action: 09850, 00000, "soacon: Archmon unable to lock named pipe." // *Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@. // *Action: Make sure that archmon is not already active on another terminal // for this ORACLE_SID. Only one archmon session is allowed at a // time for a given instance. 09851, 00000, "soacon: Archmon unable to lock named pipe." // *Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@. // *Action: Make sure that archmon is not already active on another terminal // for this ORACLE_SID. Only one archmon session is allowed at a // time for a given instance. 09852, 00000, "sfgcwd: failed to get the name of the current directory." // *Cause: // *Action: 09853, 00000, "snyRemovePort: bad return code from request." // *Cause: The request to remove a port from the callback set returned a // failure code. // *Action: Possible operating system error. Contact Oracle support. 09854, 00000, "snyPortInfo: bad return code from request." // *Cause: The request to collect info on a port in the callback set returned // a failure code. // *Action: Possible operating system error. Contact Oracle support. 09855, 00000, "removeCallback: bad message format." // *Cause: The routine received an incorrectly formatted request. // *Action: Internal error. Contact Oracle support. 09856, 00000, "smpalo: vm_allocate error while allocating pga." // *Cause: The vm_allocate system call returned an error. // *Action: Check returned error. Possibly out of system resources. 09857, 00000, "smprset: vm_protect error while protecting pga." // *Cause: The vm_protect system call returned an error. // *Action: Internal error. Contact Oracle support. / / 09858-09859 Reserved For NeXT port / / / 09860-09869 Reserved For Oracle Europe / 09870, 00000, "spini: failure initializing maximum number of open files." // *Cause: ulimit system call returned an error. // *Action: Check errno. 09871, 00000, "TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf." // *Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages. // *Action: Check additional return error for more information. 09872, 00000, "TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf." // *Cause: Create() failed when trying to create the tasdef file. // *Action: Verify permissions on $(ORACLE_HOME)/dbs directory. 09873, 00000, "TASDEF_OPEN: open error when opening tasdef@.dbf file." // *Cause: Unable to open tasdef@.dbf file. // *Action: Check errno. Possible permission problem. Verify that // tasdef@.dbf file exists. 09874, 00000, "TASDEF_READ: read error, unable to read tasdef@.dbf file." // *Cause: Read system call returned an error when attempting to read // ?/dbs/tasdef@.dbf. // *Action: Check errno returned. Sgadef file may be corrupted or // incompatible with oracle version. 09875, 00000, "TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file." // *Cause: Write call failed. // *Action: Check errno returned. Possibly out of space on device. 09876, 00000, "TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file." // *Cause: Close system call returned an error. // *Action: Check errno returned. Possible operating system failure. 09877, 00000, "sstascre: shmget error, unable to get a shared memory segment." // *Cause: Error in shmget. // *Action: Check errno returned. Verify that enough shared memory is available // on the system. 09878, 00000, "sstascre/sstasat: shmat error, unable to attach tas write page" // *Cause: Error in shmat. // *Action: Check errno returned.Verify that enough shared memory is available // on the system. 09879, 00000, "sstascre/sstasat: shmat error, unable to attach tas read page" // *Cause: Error in shmat. // *Action: Check errno returned.Verify that enough shared memory is available // on the system. 09880, 00000, "sstasfre/sstasdel: shmdt error, unable to detach tas write page" // *Cause: Error in shmdt. // *Action: Check errno returned. 09881, 00000, "sstasfre/sstasdel: shmdt error, unable to detach tas read page" // *Cause: Error in shmdt. // *Action: Check errno returned. 09882, 00000, "sstasfre/sstasdel: shmctl error, unable to remove tas shm page" // *Cause: Error in shmctl. // *Action: Check errno returned. 09883, 00000, "Two Task interface: oratab file does not exist" // *Cause: The oratab file does not exist. // *Action: Install oracle before you use it or recreate the oratab file. 09884, 00000, "Two Task interface: SID doens't match current PU" // *Cause: You are trying to start oracle on another PU than you configured // oracle on or there is no entry for this SID in oratab file. // *Action: Start oracle with this SID on its designated PU (see oratab file). // Or install the new database with SID. 09885, 00000, "osnTXtt: cannot create TXIPC channel" // *Cause: The TXIPC driver failed to create pipes for two-task communications // with the oracle shadow process. // *Action: You have probably exceeded the maximum number of open file // descriptors per user or the system file table is full. Note the // operating system error code and contact your system administrator. 09886, 00000, "osnTXtt: translation error while expanding txipc@.trc." // *Cause: Failure of sltln(txipc@.trc) while creating debug channel. // *Action: Check additional return error for more information. 09887, 00000, "osnTXtt: Failed to create/open debug channel." // *Cause: // *Action: 09888, 00000, "osnTXtt: txipc channel creation failed" // *Cause: The txipc driver failed to create channels for two-task // communications with the oracle shadow process. // *Action: You have probably exceeded the maximum number of open file // descriptors per user or the system file table // operating system error code and contact your system administrator. 09889, 00000, "osnTXtt: access error on oracle executable" // *Cause: The txipc driver could not access the oracle executable. // *Action: Check the permissions on the ORACLE executable and each // component of the ORACLE_HOME/bin path. 09890, 00000, "osnTXtt: malloc failed" // *Cause: The txipx driver failed to allocate enough heap space for its // context area buffers. // *Action: Contact your customer support representative. 09894, 00000, "sfwrt: Unable to initialize Async Write." // *Cause: DIO_Ainit returned an error. // *Action: Possible OS memory resource shortage. 09895, 00000, "sfaswr: seals do not match." // *Cause: Function was called with invalid argument. // *Action: Internal error. 09896, 00000, "sfaswr: invalid block number." // *Cause: File block number is out of range of file. Additional information // returns block number. // *Action: Check block number. 09897, 00000, "sfaswr: write error, unable to write database block." // *Cause: Additional information returns block number. // *Action: Check errno. Check block number. Possible problem with Async IO. 09898, 00000, "sfalck: setitimer error, unable to set interval timer." // *Cause: An error occurred while trying to set an interval timer. // Probable porting problem. // *Action: Check errno. 09899, 00000, "sfapol: write error, unable to poll async write." // *Cause: DIO_Apoll timed out. // *Action: Check I/O Device, or turn off async_write. 09900, 00000, "sfapol: write error, unable to poll async write." // *Cause: DIO_Apoll returned an error. Possible internal error. // *Action: Check I/O Device, or turn off async_write. Check errno. 09901, 00000, "sfapol: write error, unable to write database block." // *Cause: Additional information returns block number. // *Action: Check errno. Check block number. 09902, 00000, "sfapol: write returned incorrect number of bytes." // *Cause: Possible truncated write. Additional information returns block // number and number of bytes. // *Action: Check block number and number of bytes written. 09903, 00000, "sfwrt: Internal error." // *Cause: Failed to write all requested blocks. // *Action: Check block number and number of bytes written. 09904, 00000, "sfotf: temporary file directory name is too long" // *Cause: The name of the directory where temporary sort files are to // reside is longer than the maximum, 120 characters. // *Action: Set the init.ora parameter "temporary_sort_file_dest" so that is // shorter than the maximum length. 09905, 00000, "sfotf: mktemp() failed" // *Cause: The routine used to generate the names of the temporary sort files // failed, because no more names were available. // *Action: This is an internal error, and should never happen. 09906, 00000, "sfotf: open of the temporary sort file failed." // *Cause: A file that is to be used as temporary sorting file could not be // opened. // *Action: Check the errno. The init.ora parameter "temporary_sort_file_dest" // may not point to a directory. 09907, 00000, "sfotf: unlink of the temporary sort file failed" // *Cause: As part of the process of creating a temporary sort file, the // file is removed while the process has it open. The file still // exists because the process has not closed it. However, the // unlink failed. // *Action: This is an internal error and should never happen. 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. 09917, 00000, "DBA group does not exist in system groups file." // *Cause: The group that was selected to hold the names of the dba users // does not exist in /etc/groups. // *Action: Either add an entry for the group to the file or re-install // ORACLE with the proper group name. 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: 09965, 00000, "sfsfs: invalid file size." // *Cause: An invalid file size was specified. A non-zero file size, specified // as a valid logical block size must be specified. The logical block // size must be a multiple of the physical block size and less than // the maximum block size. // *Action: Specify a valid file size. 09966, 00000, "sfsfs: unable to open file in read/write mode" // *Cause: A datafile resize operation failed because the operating system // was unable to open the file in read/write mode. // *Action: Correct the operating system error and retry the resize operation. 09967, 00000, "sfsfs: unable to resize a file larger" // *Cause: A datafile resize operation failed because the operating system // was unable to make the file larger. // *Action: Correct the operating system error and retry the resize operation. 09968, 00000, "sfsfs: unable to seek to beginning of file" // *Cause: A datafile resize operation failed because the operating system // was unable to seek to the beginning of the file the // resize operation. 09969, 00000, "sfsfs, sfrfs: malloc error, unable to allocate buffer." // *Cause: A datafile resize operation failed because the malloc library // routine returned an error. // *Action: Possible memory resouce shortage. 09970, 00000, "sfsfs: read error, unable to read header block." // *Cause: A datafile resize operation failed because the operating system // was unable to read the datafile header. // *Action: Correct the operating system error and retry the resize operation. 09971, 00000, "sfsfs: write error, unable to write header block." // *Cause: A datafile resize operation failed because the operating system // was unable to write the datafile header. // *Action: Correct the operating system error and retry the resize operation. 09972, 00000, "sfsfs: unable to resize a file smaller" // *Cause: A datafile resize operation failed because the operating system // was unable to make the file smaller. // *Action: Correct the operating system error and retry the resize operation. 09973, 00000, "sfsfs: close error." // *Cause: A datafile resize operation failed because the operating system // was unable to close the file. // *Action: Correct the operating system error and retry the resize operation. / 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. / 10000, 00000, "control file debug event, name 'control_file'" // *Cause: // *Action: 10001, 00000, "control file crash event1" // *Cause: // *Action: 10002, 00000, "control file crash event2" // *Cause: // *Action: 10003, 00000, "control file crash event3" // *Cause: // *Action: 10004, 00000, "control file crash event4" // *Cause: // *Action: 10005, 00000, "trace latch operations for debugging" // *Cause: // *Action: 10006, 00000, "testing - block recovery forced" // *Cause: // *Action: 10007, 00000, "log switch debug crash after new log select, thread %s" // *Cause: // *Action: level 1 - closed thread only // level 2 - open thread only // level 3 - open or closed thread 10008, 00000, "log switch debug crash after new log header write, thread %s" // *Cause: // *Action: level 1 - closed thread only // level 2 - open thread only // level 3 - open or closed thread 10009, 00000, "log switch debug crash after old log header write, thread %s" // *Cause: // *Action: level 1 - closed thread only // level 2 - open thread only // level 3 - open or closed thread 10010, 00000, "Begin Transaction" // *Cause: // *Action: 10011, 00000, "End Transaction" // *Cause: // *Action: 10012, 00000, "Abort Transaction" // *Cause: // *Action: 10013, 00000, "Instance Recovery" // *Cause: // *Action: 10014, 00000, "Roll Back to Save Point" // *Cause: // *Action: 10015, 00000, "Undo Segment Recovery" // *Cause: // *Action: 10016, 00000, "Undo Segment extend" // *Cause: // *Action: 10017, 00000, "Undo Segment Wrap" // *Cause: // *Action: 10018, 00000, "Data Segment Create" // *Cause: // *Action: 10019, 00000, "Data Segment Recovery" // *Cause: // *Action: 10020, 00000, "partial link restored to linked list (KSG)" // *Cause: // *Action: 10021, 00000, "latch cleanup for state objects (KSS)" // *Cause: // *Action: 10022, 00000, "trace ktsgsp" // *Cause: // *Action: 10023, 00000, "Create Save Undo Segment" // *Cause: // *Action: 10024, 00000, "Write to Save Undo" // *Cause: // *Action: 10025, 00000, "Extend Save Undo Segment" // *Cause: // *Action: 10026, 00000, "Apply Save Undo" // *Cause: // *Action: 10027, 00000, "latch cleanup for enqueue locks (KSQ)" // *Cause: // *Action: 10028, 00000, "latch cleanup for enqueue resources (KSQ)" // *Cause: // *Action: 10029, 00000, "session logon (KSU)" // *Cause: // *Action: 10030, 00000, "session logoff (KSU)" // *Cause: // *Action: 10031, 00000, "row source debug event (R*)" // *Cause: // *Action: 10032, 00000, "sort end (SOR*)" // *Cause: // *Action: 10033, 00000, "sort run (SRD*/SRS*)" // *Cause: // *Action: /10034, 00000, "access path analysis (APA*)" // *Cause: // *Action: 10035, 00000, "parse SQL statement (OPIPRS)" // *Cause: // *Action: // Level 1+ Print out user SQL statements // Level >3 Print out recursive SQL // Level >5 Print out row cache cached cursor stats 10036, 00000, "create remote row source (QKANET)" // *Cause: // *Action: 10037, 00000, "allocate remote row source (QKARWS)" // *Cause: // *Action: 10038, 00000, "dump row source tree (QBADRV)" // *Cause: // *Action: 10039, 00000, "type checking (OPITCA)" // *Cause: // *Action: 10040, 00000, "dirty cache list" // *Cause: // *Action: 10041, 00000, "dump undo records skipped" // *Cause: // *Action: 10042, 00000, "trap error during undo application" // *Cause: // *Action: 10043, 00000, "check consistency of owner/waiter/converter lists in KSQ" // *Cause: // *Action: 10044, 00000, "free list undo operations" // *Cause: // *Action: 10045, 00000, "free list update operations - ktsrsp, ktsunl" // *Cause: // *Action: 10046, 00000, "enable SQL statement timing" // *Cause: // *Action: 10047, 00000, "trace switching of sessions" // *Cause: // *Action: 10048, 00000, "Undo segment shrink" // *Cause: // *Action: 10049, 00000, "protect library cache memory heaps" // *Cause: // *Action: Use the OS memory protection (if available) to protect library // cache memory heaps that are pinned. 10050, 00000, "sniper trace" // *Cause: // *Action: 10051, 00000, "trace OPI calls" // *Cause: // *Action: 10052, 00000, "don't clean up obj$" // *Cause: // *Action: 10053, 00000, "CBO Enable optimizer trace" // *Cause: // *Action: 10054, 00000, "trace UNDO handling in MLS" // *Cause: // *Action: 10055, 00000, "trace UNDO handing" // *Cause: // *Action: 10056, 00000, "dump analyze stats (kdg)" // *Cause: // *Action: 10057, 00000, "suppress file names in error messages" // *Cause: // *Action: 10058, 00000, "use table scan cost in tab$.spare1" // *Cause: // *Action: 10059, 00000, "simulate error in logfile create/clear" // *Cause: // *Action: 10060, 00000, "CBO Enable predicate dump" // *Cause: // *Action: 10061, 00000, "disable SMON from cleaning temp segment" // *Cause: // *Action: 10062, 00000, "disable usage of OS Roles in osds" // *Cause: // *Action: 10063, 00000, "disable usage of DBA and OPER privileges in osds" // *Cause: // *Action: 10064, 00000, "thread enable debug crash level %s, thread %s" // *Cause: // *Action: level 1 - after new current log header written // level 2 - after current log committed // level 3 - after redo generation complete 10065, 00000, "limit library cache dump information for state object dump" // *Cause: // *Action: level 1 - minimal (only the address of state objects) // level 2 - little more (no object details) // level 3 - normal 10066, 00000, "simulate failure to verify file" // *Cause: // *Action: level is file number to fail verification 10067, 00000, "force redo log checksum errors - block number" // *Cause: // *Action: level is block number to corrupt 10068, 00000, "force redo log checksum errors - file number" // *Cause: // *Action: level is file number to corrupt 10069, 00000, "Trusted Oracle test event" // *Cause: // *Action: Should never be enabled by customers. Used to prevent diffs in // regression testing by making Trusted behave like Oracle in // specific events. // level > 1 - handle 254 column tables without error // level = 20 - implicitly include ROWLABEL in views 10070, 00000, "force datafile checksum errors - block number" // *Cause: // *Action: level is block number to corrupt 10071, 00000, "force datafile checksum errors - file number" // *Cause: // *Action: level is file number to corrupt 10072, 00000, "protect latch recovery memory" // *Cause: // *Action: 10073, 00000, "have PMON dump info before latch cleanup" // *Cause: // *Action: 10074, 00000, "default trace function mask for kst" // *Cause: // *Action: 10075, 00000, "CBO Disable outer-join to regular join conversion" // *Cause: // *Action: 10076, 00000, "CBO Enable cartesian product join costing" // *Cause: // *Action: 10077, 00000, "CBO Disable view-merging optimization for outer-joins" // *Cause: // *Action: 10078, 00000, "CBO Disable constant predicate elimination optimization" // *Cause: // *Action: / 10079, 00000, "trace data sent/received via SQL*Net" // *Cause: // *Action: level 1 - trace network ops to/from client // level 2 - in addition to level 1, dump data // level 4 - trace network ops to/from dblink // level 8 - in addition to level 4, dump data / 10080, 00000, "dump a block on a segment list which cannot be exchanged" // *Cause: // *Action: / At level > 1, dump the block / At level > 5, dump the stack / At level > 10, unlink the block 10081, 00000, "segment High Water Mark has been advanced" // *Cause: // *Action: 10082, 00000, "free list head block is the same as the last block" // *Cause: // *Action: / At level > 1, dump the block / At level > 5, dump the stack 10083, 00000, "a brand new block has been requested from space management" // *Cause: // *Action: 10084, 00000, "free list becomes empty" // *Cause: // *Action: 10085, 00000, "free lists have been merged" // *Cause: // *Action: 10086, 00000, "CBO Enable error if kko and qka disagree on oby sort" // *Cause: // *Action: 10087, 00000, "disable repair of media corrupt data blocks" // *Cause: // *Action: 10088, 00000, "CBO Disable new NOT IN optimization" // *Cause: // *Action: 10089, 00000, "CBO Disable index sorting" // *Cause: // *Action: 10090, 00000, "invoke other events before crash recovery" // *Cause: // *Action: 10091, 00000, "CBO Disable constant predicate merging" // *Cause: // *Action: 10092, 00000, "CBO Disable hash join" // *Cause: // *Action: 10093, 00000, "CBO Enable force hash joins" // *Cause: // *Action: 10094, 00000, "before resizing a data file" // *Document: NO // *Cause: // *Action: 10095, 00000, "dump debugger commands to trace file" // *Cause: // *Action: 10096, 00000, "after the cross instance call when resizing a data file" // *Document: NO // *Cause: // *Action: 10097, 00000, "after generating redo when resizing a data file" // *Document: NO // *Cause: // *Action: 10098, 00000, "after the OS has increased the size of a data file" // *Document: NO // *Cause: // *Action: 10099, 00000, "after updating the file header with the new file size" // *Document: NO // *Cause: // *Action: 10100, 00000, "after the OS has decreased the size of a data file" // *Document: NO // *Cause: // *Action: 10101, 00000, "atomic redo write recovery" // *Cause: // *Action: 10102, 00000, "switch off anti-joins" // *Cause: // *Action: 10103, 00000, "CBO Disable hash join swapping" // *Cause: // *Action: 10104, 00000, "dump hash join statistics to trace file" // *Cause: // *Action: 10105, 00000, "CBO Enable constant pred trans and MPs w WHERE-clause" // *Cause: // *Action: 10106, 00000, "CBO Disable evaluating correlation pred last for NOT IN" // *Cause: // *Action: 10107, 00000, "CBO Always use bitmap index" // *Cause: // *Action: 10108, 00000, "CBO Don't use bitmap index" // *Cause: // *Action: 10109, 00000, "CBO Disable move of negated predicates" // *Cause: // *Action: 10110, 00000, "CBO Try index rowid range scans" // *Cause: // *Action: 10111, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10112, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10113, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10114, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10115, 00000, "CBO Bitmap optimization use maximal expression" // *Cause: // *Action: 10116, 00000, "CBO Bitmap optimization switch" // *Cause: // *Action: 10117, 00000, "CBO Disable new parallel cost model " // *Cause: // *Action: 10118, 00000, "CBO Enable hash join costing " // *Cause: // *Action: 10119, 00000, "QKA Disable GBY sort elimination" // *Cause: // *Action: 10120, 00000, "CBO Disable index fast full scan" // *Cause: // *Action: 10121, 00000, "CBO Don't sort bitmap chains" // *Cause: // *Action: 10122, 00000, "CBO disable count(col) => count(*) transformation" // *Cause: // *Action: 10123, 00000, "QKA Disable Bitmap And-EQuals" // *Cause: // *Action: 10145, 00000, "test auditing network errors" // *Cause: // *Action: 10146, 00000, "enable Oracle TRACE collection" // *Cause: // *Action: 10200, 00000, "block cleanout" // *Cause: // *Action: 10201, 00000, "consistent read undo application" // *Cause: // *Action: 10202, 00000, "consistent read block header" // *Cause: // *Action: 10203, 00000, "consistent read buffer status" // *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 numbers 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: 10211, 00000, "check index 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: 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, "check redo generation by copying before applying" // *Cause: // *Action: 10231, 00000, "skip corrupted blocks on _table_scans_" // *Cause: // *Action: such blocks are skipped in table scans, and listed in trace files 10232, 00000, "dump corrupted blocks symbolically when kcbgotten" // *Cause: // *Action: puts corrupted block in trace file 10233, 00000, "skip corrupted blocks on index operations" // *Cause: // *Action: skip corrupted data and/or index blocks during index scans. // information is logged to a trace file. 10234, 00000, "trigger event after calling kcrapc to do redo N times" // *Cause: // *Action: creates a file named 'crash' 10235, 00000, "check memory manager internal structures" // *Cause: // *Action: 10236, 00000, "library cache manager" // *Cause: // *Action: 10237, 00000, "simulate ^C (for testing purposes)" // *Cause: // *Action: 10238, 00000, "instantiation manager" // *Cause: // *Action: 10239, 00000, "multi-instance library cache manager" // *Cause: // *Action: 10240, 00000, "dump dba's of blocks that we wait for" // *Cause: // *Action: 10241, 00000, "dump SQL generated for remote execution (OPIX)" // *Cause: // *Action: 10242, 00000, "suppress OER 2063 (for testing distrib w/o different error log)" // *Cause: // *Action: 10243, 00000, "simulated error for test %s of K2GTAB latch cleanup" // *Cause: levels 1..6 for insert, 7..11 for delete // *Action: 10244, 00000, "make tranids in error msgs print as 0.0.0 (for testing)" // *Cause: also makes "alter system enable distributed recovery" synchronous // *Action: 10245, 00000, "simulate lock conflict error for testing PMON" // *Cause: // *Action: 10246, 00000, "print trace of PMON actions to trace file" // *Cause: // *Action: 10247, 00000, "Turn on scgcmn tracing. (VMS ONLY)" // *Cause: // *Action: / / LEVEL ACTION /--------------------------------------------------------------------------- / >= 1 Print lock name, action, mode, comp ast, bast, timeout, val? / >= 2 print Success code of request (NORMAL, SYNCH, or NOTQUEUED) / >= 3 print Value block / >= 5 Print delta CPU and elapsed times. / >= 100 stack dump at level 100-. 10248, 00000, "turn on tracing for dispatchers" // *Cause: // *Action: 10249, 00000, "turn on tracing for multi-stated servers" // *Cause: // *Action: 10250, 00000, "Trace all allocate and free calls to the topmost SGA heap" // *Cause: // *Action: 10251, 00000, "check consistency of transaction table and undo block" // MERGE: 10235 RENUMBERED TO 10251 // *Cause: // *Action: 10252, 00000, "simulate write error to data file header" // MERGE: 10238 RENUMBERED TO 10252 // *Cause: // *Action: 10253, 00000, "simulate write error to redo log" // MERGE: 10239 RENUMBERED TO 10253 // *Cause: // *Action: 10254, 00000, "trace cross-instance calls" // *Cause: // *Action: 10255, 00000, "pl/sql parse checking" // *Cause: // *Action: sends all dml statements to pl/sql for parse and semantic check 10256, 00000, "turn off multi-threaded server load balancing" // *Cause: // *Action: 10257, 00000, "trace multi-threaded server load balancing" // *Cause: // *Action: 10258, 00000, "force shared servers to be chosen round-robin" // *Cause: // *Action: 10259, 00000, "get error message text from remote using explicit call" // *Cause: for npigem coverage testing (normally called only for V5 remote) // *Action: 10260, 00000, "Trace calls to SMPRSET (VMS ONLY)" // *Cause: Allow callers to find their own bugs in memory protection // *Action: // Level >=1 (101) : ini,quit (set) do simple trace // Level >=5 (105) : ini,quit (set) dump arglist // Level >=10 (110) : ini,quit (set) dump call stack 10261, 00000, "Limit the size of the PGA heap" // *Cause: the limit is one kilobyte times the level of the event. If the // pga grows bigger than this signal an internal error. // *Action: 10262, 00000, "Don't check for memory leaks" // *Cause: Setting this event to level one causes memory leak checking to // be disabled. Setting this event to any other non-zero number // allows that number to be used as a threshold value when checking // for memory leaks in the PGA, SGA, and UGA heaps. // *Action: 10263, 00000, "Don't free empty PGA heap extents" // *Cause: This is useful for debugging since watchpoints are lost on free // *Action: 10264, 00000, "Collect statistics on context area usage (x$ksmcx)" // *Cause: // *Action: 10265, 00000, "Keep random system generated output out of error messages" // *Cause: so test system files don't diff // *Action: 10266, 00000, "Trace OSD stack usage" // *Cause: Porters should implement this to help them debug // their stack implementations. It should be used in at least // smcstk(). // *Action: 10267, 00000, "Inhibit KSEDMP for testing" // *Cause: Some tests may generate internal or fatal errors on purpose. / This event can limit the size of tracefile produced for such / tests. // *Action: LEVEL used by KSEDMP is one less than level of this event. / 10268, 00000, "Don't do forward coalesce when deleting extents" // *Cause: setting this event keeps kts from coalescing forward at each // extent when dropping a temp segment. // *Action: 10269, 00000, "Don't do coalesces of free space in SMON" // *Cause: setting this event prevents SMON from doing free space coalesces 10270, 00000, "Debug shared cursors" // *Cause: Enables debugging code in shared cursor management modules // *Action: 10271, 00000, "distributed transaction after COLLECT" // *Cause: // *Action: 10272, 00000, "distributed transaction before PREPARE" // *Cause: // *Action: 10273, 00000, "distributed transaction after PREPARE" // *Cause: // *Action: 10274, 00000, "distributed transaction before COMMIT" // *Cause: // *Action: 10275, 00000, "distributed transaction after COMMIT" // *Cause: // *Action: 10276, 00000, "distributed transaction before FORGET" // *Cause: // *Action: 10277, 00000, "Cursor sharing (or not) related event (used for testing)" // *Cause: // *Action: 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: 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, "kdnchk - checkvalid event - not for general purpose use." // *Cause: // *Action: Internal Event - Should not be set unless directed by RDBMS DEV" 10291, 0000, "die in dtsdrv to test controlfile undo" // *Cause: // *Action: If this event is set, error OERI(10291) is signalled when // issueing DROP TABLESPACE. The drop command fails, and the // tablespace should still be there. 10292, 0000, "dump uet entries on a 1561 from dtsdrv" // *Cause: // *Action: dumps the uet$ entries blocking the drop on a 1561 to tracefile 10293, 0000, "dump debugging information when doing block recovery" // *Cause: // *Action: If this event is set and a block recovery done, then the // RBA range is printed, along with any chang vectors applied. 10294, 0000, "enable PERSISTENT DLM operations on non-compliant systems" // *Cause: // *Action: Allow specification of buffer cache locking that requires // persistant lock resources and recovery operations even though // the lock manager does not support it. ENABLE THIS EVENT FOR // TESTING ONLY. 10300, 00000, "disable undo compatibility check at database open" // *Cause: // *Action: If this event is enabled it will be possible to upgrade to a new // software version with an incompatible log format when there may be // undo that needs to be applied. This is intended for upgrades // from releases before 6.0.34.3 when there are tablespaces that are // offline cleanly with no save undo. Those releases did not check the // deferred rollback segments, it was assumed that there was some // undo in the segments and every offline tablespace had one. This // event must only be set if you are ABSOLUTELY SURE the last // shutdown was a shutdown normal with no errors (do it again to be // sure), and that there is no save undo for any of the offline // tablespaces (dump the save undo segment header). 10301, 0000, "Enable LCK timeout table consistency check" // *Cause: // *Action: / 10320, 0000, "Enable data layer (kdtgrs) tracing of space management calls" // *Cause: // *Action: // / / reserve events 10352-10359 for direct asynchronous read path / 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 / / reserve events for parallel query option. Available range 10360-10374 / 10374, 00000, "parallel query server interrupt (validate lock value)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to validate its lock value / 10375, 00000, "turn on checks for statistics rollups" // *Cause: // *Action: enables checks for stat rollup in QC // *Comment: verify that the rollup is being done accurately / / 10376, 00000, "turn on table queue statistics" // *Cause: // *Action: enables table queue statistics gathering // *Comment: all instances must be started with this event when used / 10377, 00000, "turn off load balancing" // *Cause: // *Action: turns off default load balancing // *Comment: allocates slaves sequentially from coordinater to (coord - width) / 10378, 00000, "force hard process/range affinity" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only / 10379, 00000, "direct read for rowid range scans (unimplemented)" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only / 10380, 00000, "kxfp latch cleanup testing event" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only--indicates the server to which the latch // cleanup key applies (0 for QC) / 10381, 00000, "kxfp latch cleanup testing event" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only--the latch cleanup key (the number of the // LCTEST() call on which to kill the process) / 10382, 00000, "parallel query server interrupt (reset)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to clear its buffers and reset itself / 10383, 00000, "auto parallelization testing event" // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: For testing only. Trace level bits can be used in combination: // 1: parallelize every full table scan (kkfd.c) // 2: create every table/cluster parallel (prsc.c) // 4: create every table/cluster cache // 8: create every table/cluster cache partitions (overrides 4) / 10384, 00000, "parallel dataflow scheduler tracing" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: trace level is a bitfield (see kkrp.h) / 10385, 00000, "parallel table scan range sampling method" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level: 0: (default) sample by random rowid // 1: sample by first rows of partition ranges / 10386, 00000, "parallel SQL hash and range statistics" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: print kxfq hash and range statistics / 10387, 00000, "parallel query server interrupt (normal)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to leave the server group normally / 10388, 00000, "parallel query server interrupt (failure)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to leave the server group (query // failed) / 10389, 00000, "parallel query server interrupt (cleanup)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to leave the server group (signaled // by PMON, coordinator died) / 10390, 00000, "Trace parallel query slave execution" // *Cause: // *Action: trace level is a bitfield (see kxfx.h) / 10391, 00000, "trace rowid range partitioning" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: print details of parallel query table scan range partitions / 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, "allow parallelization of small tables" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: parallelize small tables (for testing only) / 10395, 00000, "adjust sample size for range table queues" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: use reduced sample size for testing only / 10396, 00000, "circumvent range table queues for queries" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing. uses only hash table queues in queries, with // any output ordering done in the QC. does not avoid range // table queues during index creation. / 10397, 00000, "suppress verbose parallel coordinator error reporting" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: disable the ORA-12801 message when a parallel query // server gets a SQL error, instead report the slave's // actual error as if signaled in the foreground (for // testing, to match sequential log files) / 10398, 00000, "enable timeouts in parallel query threads" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level of this event indicates the number of seconds // before timing out of a kxfpqdeq() call, after which // an internal error will be signaled...for testing so // that test suites don't wedge. / 10399, 00000, "use different internal maximum buffer size" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level of this event indicates the size of kxfp buffers // to be used, in bytes...for testing, especially of row // and SQL statement fragmentation code / / 10400, 00000, "turn on system state dumps for shutdown debugging" // *Cause: // *Action: Enables debugging code for shutdown problems (e.g., hangs) 10500, 00000, "turn on traces for SMON" // *Cause: // *Action: // Level: <=5 trace instance recovery // > 5 trace posting of SMON 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: 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) 10600, 00000, "check cursor frame allocation" // *Cause: // *Action: 10602, 00000, "cause an access violation (for testing purposes)" // *Cause: // *Action: 10603, 00000, "cause an error to occur during truncate (for testing purposes)" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: this causes kdifrb to encounter an error during truncation of a // table with an index. it is for testing purposes only. 10604, 00000, "trace parallel create index" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of parallel create index 10605, 00000, "enable parallel create index by default" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: this causes all create index statement to by default // occur in parallel. it is for testing purposes only. // the level set in the event is the degree of parallelism. // *Comment: enables analysis of parallel create index - query coordinator 10606, 00000, "trace parallel create index" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of parallel create index - kkri slaves 10607, 00000, "trace index rowid partition scan" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of rowid index scan - rix row source 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 10610, 00000, "trace create index pseudo optimizer" // *Cause: // *Action: set this event only under the supervision of Oracle development 10666, 00000, "Do not get database enqueue name" // *Cause: // *Action: 10667, 00000, "Cause sppst to check for valid process ids" // *Cause: // *Action: 10690, 00000, "Set shadow process core file dump type (Unix only)" // *Cause: Control core file size for shadow processes // *Action: Level 1: Detach SGA before dumping core // Level 2: Do not produce any core 10691, 00000, "Set background process core file type (Unix only)" // *Cause: Control core file size file for background processes // *Action: Level 1: Detach SGA before dumping core 10700, 00000, "Alter access violation exception handler" // *Cause: Use this event to control what the VMS exception handler // does when it encounters an access violation. // *Action: // Level: >=10 Suspend current process on access violation // *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** 10701, 00000, "Dump direct loader index keys" // *Cause: // *Action: 10702, 00000, "Enable histogram data generation" // *Cause: When enabled, histogram entries will be processed when ANALYZE // is used. // *Action: 10703, 00000, "Simulate process death during enqueue get" // *Cause: Use this event to test process death enqueue cleanup by // causing the process to die in a known place getting an enqueue. // *** THIS SHOULD NEVER BE SET EXCEPT FOR TESTING *** // *Action: // *Comment: Level indicates which enqueue operation will cause death: // 1: enqueue get // 2: enqueue convert // 3: enqueue release 10704, 00000, "Print out information about what enqueues are being obtained" // *Cause: When enabled, prints out arguments to calls to ksqcmi and // ksqlrl and the return values. // *Action: Level indicates details: // Level: 1-4: print out basic info for ksqlrl, ksqcmi // 5-9: also print out stuff in callbacks: ksqlac, ksqlop // 10+: also print out time for each line 10705, 00000, "Print Out Tracing information for every I/O done by ODSs" // *Cause: When enabled, prints out tracing info on I/Os to datafiles. // *Action: // Level: >0 Print a trace of every I/O to the database files // *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** 10706, 00000, "Print out information about instance lock manipulation" // *Cause: When enabled, prints out activity in ksi routines. // *Action: Level indicates details: // 0-4: show args for each main call // 5-9: also indicate callbacks // 10+: also printout time for each line 10707, 00000, "Simulate process death for instance registration" // *Cause: When enabled, process commits suicide to test instance // registration recovery code. // *Action: Level indicates where the process will die 10708, 00000, "Print out Tracing information for skxf multi instance comms" // *Cause: When enabled, prints activity of skxf routines // *Action: Level indicates details: // 1: Print out tracing for each call // 2: Print a line on Entry to every skxf routine // *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** 10709, 00000, "enable parallel instances in create index by default" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: this causes all create index statement to by default // use multiple instances. it is for testing purposes only. // the level set in the event is the number of instances. // *Comment: enables analysis of parallel create index - query coordinator / / 10710 - 10729 are Reserved for BITMAP row sources / 10710, 00000, "trace bitmap index access" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: display the start-rowid, end-rowid of each bitmap segment - kkrbx // row source 10711, 00000, "trace bitmap index merge" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index merge - kkrbu row source 10712, 00000, "trace bitmap index or" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index or - kkrbo row source 10713, 00000, "trace bitmap index and" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index and - kkrba row source 10714, 00000, "trace bitmap index minus" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index minus - kkrbm row source 10715, 00000, "trace bitmap index conversion to rowids" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index merge - kkrbt row source 10716, 00000, "trace bitmap index compress/decompress" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index compression/decompression - // modules kdibc, kdibci, kdibco, kdibc3 / 10800, 00000, "disable Smart Disk scan" // *Cause: // *Action: 10801, 00000, "enable Smart Disk trace" // *Cause: // *Action: 10802, 00000, "reserved for Smart Disk" // *Cause: // *Action: 10803, 00000, "write timing statistics on OPS recovery scan" // *Cause: // *Action: 10804, 00000, "reserved for ksxb" // *Cause: // *Action: 10805, 00000, "reserved for row source sort" // *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 / 10924, 00000, "import storage parse error ignore event" // *Cause: causes server to ignore specific error associated with freelists // and freelist groups when parsing // *Action: this should be enabled by import code only / // 10925 - 10974 Reserved for PL/SQL // / 10925, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 237911 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. 10926, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 190119 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. 10927, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 235190 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / 10928, 00000, "trace name context forever" // * Cause: // * Action: Set this event only under the supervision of Oracle Development. // * Comment: This event causes PL/SQL to dump out information to trace files. / / 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 - 12019 Reserved for table snapshot errors / / 12000 - 12019 reserved for snapshots / 12000, 00000, "a snapshot log already exists on table '%s'" // *Cause: // *Action: 12001, 00000, "cannot create log: table '%s' already has a trigger" // *Cause: Snapshot logs are filled by a trigger on the master table. // That trigger cannot be created. // *Action: To create a snapshot log, drop the current trigger on the master. 12002, 00000, "there is no snapshot log on table '%s'" // *Cause: // *Action: 12003, 00000, "snapshot '%s' does not exist" // *Cause: // *Action: 12004, 00000, "REFRESH FAST cannot be used" // *Cause: The snapshot log does not exist or cannot be used. // *Action: Use just REFRESH, which will reinstantiate the entire table. // If a snapshot log exists and the form of the snapshot allows the // use of a snapshot log, REFRESH FAST will be available starting // the next time the snapshot is refreshed. 12005, 00000, "may not schedule automatic refresh for times in the past" // *Cause: An attempt was made to schedule an automated snapshot refresh // for a time in the past. // *Action: Choose a time in the future instead. 12006, 00000, "a snapshot with the same user.name already exists" // *Cause: // *Action: 12007, 00000, "snapshot reuse parameters are inconsistent" // *Cause: The CREATE SNAPSHOT .. or CREATE SNAPSHOT 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 snapshot 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, "snapshots may not contain long columns" // *Cause: // *Action: 12010, 00000, "cannot create snapshot log on table owned by SYS" // *Cause: CREATE SNAPSHOT LOG attempts to create a trigger on the // table, but triggers can not be created on SYS tables. // *Action: Cannot create snapshot logs on SYS tables. 12011, 00000, "execution of %s jobs failed" // *Cause: Some kind of error was caught in dbms_ijob.run . One or // more jobs which were due to be run produced errors which they // could not handle. // *Action: Look at the alert log for details on which jobs failed and why. 12012, 00000, "error on auto execute of job %s" // *Cause: Some kind of error was caught while doing an automatic execute // of a job. // *Action: Look at the accompanying errors for details on why the execute // failed. 12013, 00000, "updatable snapshots must be simple enough to do fast refresh" // *Cause: The updatable snapshot query has a join, subquery, union, // connect by, order by, or group by // *Action: Make the snapshot simpler. If a join is really needed, make // multiple simple snapshots then put a view on top of them. / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / 12100 - 12299 Reserved for sql*net errors / / 12150, 00000, "TNS:unable to send data" // *Cause: Unable to send data. Connection probably disconnected. // *Action: Re-establish connection. If the error is persistent, turn // on tracing and reexecute the operation. / 12151, 00000, "TNS:received bad packet type from network layer" // *Cause: Internal error. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12152, 00000, "TNS:unable to send break message" // *Cause: Unable to send break message. Connection probably disconnected. // *Action: Re-establish connection. If the error is persistent, turn // on tracing and reexecute the operation. / 12153, 00000, "TNS:not connected" // *Cause: Not currently connected to a remote host. // *Action: Re-establish connection. / 12154, 00000, "TNS:could not resolve service name" // *Cause: The service name specified is not defined correctly in the // TNSNAMES.ORA file. // *Action: Make the following checks and correct the error: // - Verify that a TNSNAMES.ORA file exists and is in the proper // place and accessible. See the operating system specific manual // for details on the required name and location. // - Check to see that the service name exists in one of the // TNSNAMES.ORA files and add it if necessary. // - Make sure there are no syntax errors anywhere in the file. // Particularly look for unmatched parentheses or stray characters. // Any error in a TNSNAMES.ORA file makes it unusable. See // Chapter 4 in the SQL*Net V2 Administrator's Guide. If // possible, regenerate the configuration files using the Oracle // Network Manager. / 12155, 00000, "TNS:received bad datatype in NSWMARKER packet" // *Cause: Internal error during break handling. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12156, 00000, "TNS:tried to reset line from incorrect state" // *Cause: Internal error during break handling. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12157, 00000, "TNS:internal network communication error" // *Cause: Internal error during network communication. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12158, 00000, "TNS:could not initialize parameter subsystem" // *Cause: Unable to locate parameter file. // *Action: Verify that a valid parameter file exists, and is readable. / 12159, 00000, "TNS:trace file not writeable" // *Cause: The trace file to be generated is not writeable by this user. // *Action: If the user does not have write permissions in the directory // to which the trace file will be written, contact the DBA to get the // proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA // to specify a directory the user can write to. / 12160, 00000, "TNS:internal error: Bad error number" // *Cause: Corrupt error reporting subsystem. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12161, 00000, "TNS:internal error: partial data received" // *Cause: The connection may be terminated. // *Action: Reconnect and try again. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12162, 00000, "TNS:service name is incorrectly specified" // *Cause: The connect descriptor corresponding to the service name in // TNSNAMES.ORA is incorrectly specified. // *Action: Make sure there are no syntax errors in the connect descriptor. // Particularly look for unmatched parentheses or stray characters. // Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 // in the SQL*Net V2 Administrator's Guide. / 12163, 00000, "TNS:connect descriptor is too long" // *Cause: The connect descriptor corresponding to the service name in // TNSNAMES.ORA is too long. // *Action: The maximum length for a connect descriptor is 512 bytes and this // limit has been exceeded. Use a smaller connect descriptor. If this is not // possible, contact Worldwide Customer Support. / / This line is an OSN Magic Cookie. Don't eat it. Last OSN error in 2.0.9. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12196 - 12285 NR errors reportable to OSN. / 12196, 00000, "TNS:received an error from TNS" // *Cause: The navigation layer received an error from TNS. // *Action: See the error log file for the specific TNS error. / 12197, 00000, "TNS:keyword-value resolution error" // *Cause: The navigation layer received an error while trying to look up a // value for a keyword. // *Action: Check the syntax of the connect descriptor. / 12198, 00000, "TNS:could not find path to destination" // *Cause: Could not navigate a path through Interchanges to the destination. // This error occurs if an invalid community is in the address string, or // the address includes a protocol that is not available or the // TNSNAV.ORA file does not have a correct CMANAGER address specified or // the Interchange is down. // *Action: Assure that Interchanges necessary to get to the desired // destination are up and have available capacity for an additional // connection. Also check that the correct community and protocol have been // specified in the CMANAGER address used. / 12200, 00000, "TNS:could not allocate memory" // *Cause: Out of memory on machine. // *Action: Reconfigure machine to have more storage or run fewer applications // while the Interchange is running. / 12201, 00000, "TNS:encountered too small a connection buffer" // *Cause: TNS connection buffer supplied by the application was too small // to retrieve the data sent back. // *Action: Supply a larger connection buffer. If problem persists, call // Worldwide Customer Support. / 12202, 00000, "TNS:internal navigation error" // *Cause: Internal navigation error. // *Action: Not normally visible to the user. For further details contact // Worldwide Customer Support. / 12203, 00000, "TNS:unable to connect to destination" // *Cause: Invalid TNS address supplied or destination is not listening. // This error can also occur because of underlying network transport // problems. // *Action: Verify that the service name you entered on the command line // was correct. Ensure that the listener is running at the remote node and // that the ADDRESS parameters specified in TNSNAMES.ORA are correct. // Finally, check that all Interchanges needed to make the connection are // up and running. / 12204, 00000, "TNS:received data refused from an application" // *Cause: The application using the Interchange refused the connection // at the listener. // *Action: Make sure that the application listener at the destination is // functioning correctly. If it is and the problem persists, contact // Worldwide Customer Support. / 12205, 00000, "TNS:could not get failed addresses" // *Cause: Internal navigation error. // *Action: Not normally visible to the user. For further details contact // Worldwide Customer Support. / 12206, 00000, "TNS:received a TNS error during navigation" // *Cause: Internal navigation error because of an unexpected TNS error. // *Action: Look at the log file to find the TNS error. If necessary, turn // on tracing and repeat the operation. / 12207, 00000, "TNS:unable to perform navigation" // *Cause: Improperly configured navigation file TNSNAV.ORA. // *Action: Check the syntax of the TNSNAV.ORA file on the application`s // machine,and verify that it lists the correct communities. / 12208, 00000, "TNS:could not find the TNSNAV.ORA file" // *Cause: Either the ORACLE environment is not set up correctly, or the // TNSNAV.ORA file is not present. // *Action: Ensure that the ORACLE environment is set up appropriately // on your platform and that a TNSNAV.ORA file is present. / 12209, 00000, "TNS:encountered uninitialized global" // *Cause: Application calling navigation routine has not properly configured // the global variables. There are no TNSNAV.ORA files available, or they // are defective. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12210, 00000, "TNS:error in finding Navigator data" // *Cause: Application calling navigation routine has not properly configured // the TNSNAV.ORA file. // *Action: Check the syntax of the TNSNAV.ORA file. / 12211, 00000, "TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA" // *Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined. // *Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file. / 12212, 00000, "TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA" // *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file // does not have a CMANAGER_NAME specified. // *Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS // binding. Use of the Oracle Network Manager should eliminate this // error. / 12213, 00000, "TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA" // *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file // does not have an ADDRESS specified. // *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. / 12214, 00000, "TNS:missing local communities entry in TNSNAV.ORA" // *Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA. // *Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA // file. / 12215, 00000, "TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA" // *Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. // entry. // *Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA // / 12216, 00000, "TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA" // *Cause: Address binding for the PREFERRED_CMANAGERS entry in the client's // TNSNAV.ORA file is improperly entered. // *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. / 12217, 00000, "TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA" // *Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or // addresses specified are wrong, or the intended Connection Managers are // unavailable. // *Action: Check the PREFERRED_CMANAGERS entries in the client's // TNSNAV.ORA file and correct them or talk with your network administrator // to determine if the specified Connection Managers are available. // Verify that the Interchangess are active by using the INTCTL STATUS // command. / 12218, 00000, "TNS:unacceptable network configuration data" // *Cause: Poorly formed network configuration data. For example, a // PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the // client's TNSNAV.ORA file. Or an Interchange downtime parameter // (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA. // *Action: Check the entries in TNSNAV.ORA and the Interchange // configuration files and correct them. If necessary, talk with your // network administrator to determine if the specified Interchanges // (Connection Managers) are available and properly configured. // Use the Oracle Network Manager to generate the configuration files // if necessary. / 12219, 00000, "TNS:missing community name from address in ADDRESS_LIST" // *Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it // that have no COMMUNITY component and others that do have a COMMUNITY // component. // *Action: Check that in the connect descriptors you are using either // all the ADDRESSes have a COMMUNITY component or all do not. / / All succeeding errors are a remap of NS erros in NR / 12221, 00000, "TNS:illegal ADDRESS parameters" // *Cause: An illegal set of protocol adapter parameters was specified. In // some cases, this error is returned when a connection cannot be made to the // protocol transport. // *Action: Verify that the destination can be reached using the specified // protocol. Check the parameters within the ADDRESS section of // TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the // Oracle operating system specific documentation for your platform. // Protocols that resolve names at the transport layer (such as DECnet object // names) are vulnerable to this error if not properly configured or names are // misspelled. / 12222, 00000, "TNS:no such protocol adapter" // *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" // keyword-value pair in a TNS address) is unknown. If the supplied address // is typographically correct then the protocol adaptor is not installed. // *Action: Install the protocol adapter or correct typographically error, // as appropriate. Note: if the supplied address was derived from // resolving the service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). / 12223, 00000, "TNS:internal limit restriction exceeded" // *Cause: Too many TNS connections open simultaneously. // *Action: Wait for connections to close and re-try. / 12224, 00000, "TNS:no listener" // *Cause: The connection request could not be completed because the listener // is not running. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to // go by way of an Interchange). Start the listener on the remote machine. / 12225, 00000, "TNS:destination host unreachable" // *Cause: Contact can not be made with remote party. // *Action: Make sure the network driver is functioning and the network is up. / 12226, 00000, "TNS:operating system resource quota exceeded" // *Cause: The current user has exceeded the allotted resource assigned in the // operating system. // *Action: Acquire more operating system resource, or perform a different // function. / 12227, 00000, "TNS:syntax error" // *Cause: The supplied connect descriptor contains illegal syntax. // *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. / 12228, 00000, "TNS:protocol adapter not loadable" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter is // missing or one of its supporting libraries is missing then this error is // returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will include the name of the shared library (or DLL) that // could not be loaded. / 12229, 00000, "TNS:Interchange has no more free connections" // *Cause: One or more Interchanges along the path to the destination // desired has no more free connections available to be used for this // call. // *Action: Try again later when the Interchanges are less busy, or contact // your network administrator to have him determine which interchange it is, // and increase the number of connections available on that interchange. / 12230, 00000, "TNS:Severe Network error ocurred in making this connection" // *Cause: This error is reported by an interchange which fails to make // contact with the destination due to a physical network error while calling // a destination. // *Action: Try again later when the network service may have been fixed // or report the problem to your Network Administrator so that he may fix // the problem. / / 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. / / 12400 - 12499 Reserved for TRUSTED ORACLE / / Begin messages for TRUSTED ORACLE / 12400, 00000, "DBLOW is not a valid operating system label" // *Cause: The operating system label corresponding to DBLOW has become // invalid due to a change in operating system label definitions. // *Action: Use the operating system facilities to restore the definition // of this label, or change the value of DBLOW to a valid label. // To change the value of DBLOW, you must mount the database and // switch to OSMAC mode. 12401, 00000, "DBHIGH is not a valid operating system label" // *Cause: The operating system label corresponding to DBHIGH has become // invalid due to a change in operating system label definitions. // *Action: Use the operating system facilities to restore the definition // of this label, or change the value of DBHIGH to a valid label. // To change the value of DBHIGH, you must mount the database and // switch to OSMAC mode. 12402, 00000, "file: %s" // *Cause: Reporting file name for detail of another message. // *Action: Examine the message stack for additional detail. 12403, 00000, "file label (%s) must be equal to DBHIGH (%s)" // *Cause: An ORACLE file was found to have a label that does not match // the operating system equivalent of DBHIGH. // This may be caused if DBHIGH has been changed, or if the file // has been relabeled. // *Action: Either relabel the file so that its label matches DBHIGH, or // alter DBHIGH so that it matches the label on the file. 12404, 00000, "device low (%s) must be dominated by DBLOW (%s)" // *Cause: A ORACLE file was found on a device with an authorized range // insufficient to handle the lowest labeled data in the file. DBLOW // must always dominate the minimum device label. // *Action: Lower the authorized minimum device label or move the file // to a different device. 12405, 00000, "device high (%s) must dominate DBHIGH (%s)" // *Cause: An ORACLE file was found on a device with an authorized range // insufficient to handle the highest labeled data in the file. // DBHIGH must always be dominated by the maximum device label. // *Action: Raise the authorized maximum device label or move the file // to a different device. 12406, 00000, "must be at DBHIGH (%s) in OS to add files to a tablespace" // *Cause: A file was added to a new or existing tablespace by a user // whose operating system label was not equal to DBHIGH. // *Action: Log in to the operating system at DBHIGH to add the file. // If you are creating a new tablespace, set your session label // to the label at which you want the tablespace to be created, // then create the tablespace. If you are adding a file to an // existing tablespace, set your session label to match the // creation label of the tablespace, then alter the tablespace // See the Trusted ORACLE Administrator's Guide for more detailed // information about creating and altering tablespaces. 12407, 00000, "cannot insert or update the ROWLABEL column of a view" // *Cause: You tried to insert into or update the ROWLABEL column of // a view. Trusted ORACLE does not allow you to modify the ROWLABEL // column of a view. // *Action: While you cannot modify the ROWLABEL column of a view, you can // modify the ROWLABEL column in the base table(s) of the view. // Use the INSERT or UPDATE commands to modify the base tables(s); // consequently, this modifies the view. 12408, 00000, "tablespace previously existed at another label (%s)" // *Cause: A tablespace by this name was previously created and dropped // at another label. Part of the dictionary entry for the old // tablespace remains, and the new tablespace is attempting to // reuse the old entry. // *Action: Either recreate the tablespace at the original label or // choose a new name for this tablespace. 12409, 00000, "DBLOW cannot be null in DBMS MAC mode" // *Cause: The database was started in DBMS MAC mode before resetting DBLOW. // *Action: Restart the database in OS MAC mode and supply valid values for // both DBHIGH and DBLOW before starting up in DBMS MAC mode. 12410, 00000, "DBHIGH cannot be null in DBMS MAC mode" // *Cause: The database was started in DBMS MAC mode before resetting DBHIGH. // *Action: Restart the database in OS MAC mode and supply valid values for // both DBHIGH and DBLOW before starting up in DBMS MAC mode. 12411, 00000, "DBHIGH must dominate DBLOW" // *Cause: DBHIGH does not dominate DBLOW. // *Action: Restart the database in OS MAC mode and supply valid values // for DBHIGH and DBLOW before starting up in DBMS MAC mode. 12412, 00000, "Cannot raise DBLOW above %s" // *Cause: You tried raise DBLOW above its current value. DBLOW can only // be lowered; it cannot be raised. // *Action: Do not attempt to raise DBLOW. 12413, 00000, "Cannot lower DBHIGH below %s" // *Cause: You tried to lower DBHIGH below its current value. DBHIGH // can only be raised. // *Action: Do not attempt to lower DBHIGH. 12414, 00000, "must be DBHIGH (%s) to startup database" // *Cause: You tried to open a database while at an OS label not equal // to DBHIGH. // *Action: Login at DBHIGH to start the database. 12415, 00000, "session label must dominate the creation label of role %s" // *Cause: You tried to grant a privilege to a role while at a label // that does not dominate the role's creation label. // Your DBMS label must dominate the role's creation label in order // to grant a privilege to the role. // *Action: Check the creation label of the role and perform the grant // while at a label that dominates the creation label of the role. 12416, 00000, "label of audit must dominate user" // *Cause: You tried to set statement audit options for a user while at a // label that does not dominate the user's creation label. // Your DBMS label must dominate the user's creation label in order // to set statement audit options for the user. // *Action: Check the creation label of the user and set the statement // audit option while at a label that dominates the creation // label of the user. 12418, 00000, "label of index must equal table" // *Cause: You tried to create an index on a table while at a label that // does not match the table's creation label. // Your DBMS label must match the table's creation label in order // to create an index on the table. If the table was created at // DBHIGH or DBLOW, your label must be set to DBHIGH or DBLOW. // *Action: Check the creation label of the table and create the index // while at a label that matches the creation label of the table. 12419, 00000, "label of column must equal table" // *Cause: You tried to add a column to a table while at a label that // does not match the table's creation label. // Your DBMS label must match the table's creation label in order // to add a column to the table. // *Action: Check the creation label of the table and add the column // while at a label that matches the creation label of the table. 12420, 00000, "label of stored object must dominate referenced object %s" // *Cause: You tried to create or you issued a statement that tried // to create a stored object (view, procedure, function, // trigger) which references some object while at a label // that does not dominate the referenced object's creation label. // Your DBMS label must dominate the creation labels of all // referenced objects in order to create a stored object. // While the referenced object may be visible due to enabled // MAC privileges, MAC privileges cannot be used to // create the stored object. // *Action: Check the creation labels of the referenced objects and // create the stored object while at a label that dominates // the creation labels of all referenced objects. 12421, 00000, "label of grant must dominate object" // *Cause: You tried to grant privileges on an object while at a label // that does not dominate the object's creation label. // Your DBMS label must dominate the object's creation label // in order to grant privileges on the object. // *Action: Check the creation label of the object and perform the grant // while at a label that dominates the creation label of the object. 12422, 00000, "label of grant must dominate grantee %s" // *Cause: You tried to grant privileges to a user while at a label that // does not dominate the user's creation label. // Your DBMS label must dominate the user's creation label // in order to grant privileges to the user. // *Action: Check the creation label of the user and grant the privileges // while at a label that dominates the creation label of the user. 12423, 00000, "label of constraint must equal table" // *Cause: You tried to add a constraint to a table while at a label // that does not match the table's creation label. // Your DBMS label must match the creation label of the table // in order to add a constraint to the table. // *Action: Check the creation label of the table and add the constraint // while at a label that matches the creation label of the table. 12424, 00000, "label of object must dominate tablespace" // *Cause: You tried to create an object in a tablespace while at // a label that does not dominate the tablespace's creation label. // Your DBMS label must dominate the tablespace's creation label // in order to create an object in the tablespace. // *Action: Check the creation label of the tablespace and create the object // while at a label that dominates the creation label of // the tablespace. 12425, 00000, "label of table must dominate cluster" // *Cause: You tried to create a table in a cluster while at a label // that does not dominate the cluster's creation label. // Your DBMS label must dominate the cluster's creation label // in order to create a table in the cluster. // *Action: Check the creation label of the cluster and create the table // while at a label that dominates the creation label of the cluster. 12426, 00000, "label of user must dominate default or temporary tablespace" // *Cause: You tried to assign a user a default or temporary tablespace // when the user's creation label did not dominate the tablespace's // creation label. The user's creation label must dominate the // tablespace's creation label in order for the default or temporary // tablespace to be assigned to the user. Your DBMS label must // dominate both the user's and the tablespace's creation labels // in order to assign the tablespace to the user. // *Action: Check the creation label of the default or temporary tablespaces // and create the user so that the user's creation label // dominates the creation label of the tablespaces. 12427, 00000, "label of object must dominate schema" // *Cause: You tried to create an object in a schema while at a label // that does not dominate the schema's creation label. // Your DBMS label must dominate the schema's creation label in // order to create an object in the schema. // *Action: Check the creation label of the schema and create the object // while at a label that dominates the creation label of the schema. 12428, 00000, "insufficient MAC privileges" // *Cause: You tried to write to an object when you did not have // sufficient privileges. You may have sufficient privileges // to read the object, but do not have MAC write access to // the object. // *Action: Either retry the operation at the label of the object or // ask the database administrator for sufficient MAC privileges // to write the object. See the Trusted ORACLE7 Server // Administrator's Guide for more information on MAC privileges. 12429, 00000, "label of comment must equal table or view" // *Cause: You tried to comment a table or view while at a label that does // not match the table's or view's creation label. // Your DBMS label must match the table's or view's creation // label in order to comment the table or view. // *Action: Check the creation label of the table or view and add the comment // while at a label that matches the creation label of the table // or view. 12430, 00000, "label of trigger must equal table" // *Cause: You tried to create or you issued a statement that tried // to create a trigger on a table while at a label // that does not match the table's creation label. // Your DBMS label must match the table's creation label in // order to create the trigger on the table. // While the table may be visible due to enabled MAC privileges, // MAC privileges cannot be used to create a trigger. // *Action: Check the creation label of the table and create the trigger // while at a label that matches the creation label of the table. 12431, 00000, "label of user must dominate default profile" // *Cause: You tried to assign a user a default profile when the // user's creation label did not dominate the default // profile's creation label. In order to assign a default profile to // a user, the user's creation label must // dominate the default profile's creation label. Your DBMS // label must dominate both the user's and the default profile's // creation labels in order to assign the user the default profile. // *Action: Check the creation label of the default profile and create the // user so that the user's creation label dominates the creation // label of the default profile. 12432, 00000, "label of grant must equal label of procedure" // *Cause: An attempt was made to assign MAC privileges to a procedure at // a label other than the creation label of the procedure. // *Action: Grant MAC privileges to the procedure at the procedure's creation // label. 12433, 00000, "label of default role %s must dominate user" // *Cause: You tried to assign a default role to a user when the default // role's creation label did not dominate the user's creation label. // The default role's creation label must dominate the user's // creation label. Your DBMS label also must dominate both the // role's and user's creation label in order to assign a user a role. // *Action: Check the creation labels of the user and role and assign // only those roles whose creation labels dominate the creation // label of the user. 12434, 00000, "label of child record must dominate parent" // *Cause: You tried to insert a child record with a label that // does not dominate the corresponding parent record's label or // update a parent record such that the child records would not // dominate the corresponding parent's label. The label of a child // record must always dominate that of its parent record. // *Action: Check the label of the parent record and insert the child // record while at a label that dominates the label of the // parent record or update the label of the child record before // updating the parent record so that the child can still dominate // the parent after the update. 12435, 00000, "label of package body must equal package" // *Cause: You tried to create a package body while at a label that does // not match the corresponding package's creation label. // Your DBMS label must match the package's creation label in // order to create a package body. // *Action: Check the creation label of the package and create the package body // while at a label that matches the creation label of the package. 12436, 00000, "package body must exist to grant MAC privileges" // *Cause: An attempt was made to grant MAC privileges to a package when the // package body does not exist. // *Action: Create the package body for the package and then re-attempt // the grant. 12437, 00000, "cannot write down to a database at a lower label" // *Cause: You tried to perform a write operation in a secondary database. // You can only perform write operations in your primary database. // *Action: Connect directly to the secondary database to perform the // operation. 12438, 00000, "insufficient privileges to validate constraint on all rows" // *Cause: You must have access to all rows in a table in order to attempt // to enable a constraint. // *Action: Either enable MAC privileges so that you can read all rows in // the table, or downgrade all rows in the table so you can read them. // Then enable the constraint. 12439, 00000, "cannot modify ROWLABEL column" // *Cause: You tried to modify the definition of the ROWLABEL column with // the ALTER command. For example, you may have tried to lengthen // the ROWLABEL column. // *Action: Although the value of the ROWLABEL column can be changed, the // ROWLABEL column definition cannot be modified. 12440, 00000, "database has not been mounted in read-compatible mode" // *Cause: The requested secondary database was not started in // read-compatible mode. In order for a database to be mounted by // a higher level read-secure instance, the database must be mounted // by its primary instance in read-compatible mode. // *Action: Set the DB_MOUNT_MODE parameter to READ_COMPATIBLE in the // secondary database and start up the secondary database. 12441, 00000, "grant already exists at a different label" // *Cause: You tried to grant a privilege that was previously granted at a // different label. // *Action: Check USER_SYS_GRANTS or USER_OBJ_GRANTS to identify the // label of the privilege's previous grant. If you want to execute // the grant at the new label, revoke the old grant // and regrant the privilege while at the new label. 12442, 00000, "must be at same label as user to modify default roles" // *Cause: You tried to modify a user's default roles while at a // label that does not match the user's creation label. // Your DBMS label must match the user's creation label in // order to alter a user. // *Action: Check the ALL_USERS view to determine the creation // label of the user and modify the user's default roles // while at a label that matches the creation label of the user. 12443, 00000, "audit option already exists at a different label" // *Cause: You tried to audit an event that was previously audited at a // different label. // *Action: Check the DBA_STMT_AUDIT_OPTS or DBA_PRIV_AUDIT_OPTS dictionary // views to identify the label of the previous audit statement. If // you want to audit the event at the new label, stop the old // audit (using the NOAUDIT statement) and re-audit the event // while at the new label. 12444, 00000, "file label is lower than instance label" // *Cause: You tried to reuse a file with a label different than the database // instance label. // *Action: Examine the message stack for the file name. Remove the file // or relabel it to match the database instance label. 12445, 00000, "index/row label mismatch - see trace file" // *Cause: // *Action: 12446, 00000, "file label is higher than instance label" // *Cause: You tried to reuse a file with a label different than the database // instance label. You can only reuse files labeled at or below the // instance label. // *Action: Examine the message stack for the file name. Remove the file // or relabel it to match the database instance label. 12447, 00000, "non-secure protocol used; connection denied" // *Cause: You tried to connect to Trusted ORACLE7 with a networking protocol // that was not secure. You must use a secure networking protocol to // connect via a remote location. // *Action: Either connect to the database with a secure networking protocol or // log in directly to the database. 12448, 00000, "greatest lower bound resulted in an invalid operating system 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: Examine the message stack for a more specific messages. See // your installation or user's guide for information on invalid // label generation. See the Trusted ORACLE7 Server Administrator's // Guide for information on greatest lower bound (GLB) functions. 12449, 00000, "least upper bound resulted in an invalid operating system 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: Examine the message stack for a more specific messages. See // your installation or user's guide for information on invalid // label generation. See the Trusted ORACLE7 Server Administrator's // Guide for information on least upper bound (LUB) functions. 12450, 00000, "internal buffer overflow during label translation" // *Cause: An internal buffer used to translate labels overflowed. A possible // cause could be a format mask you specified is too large. // *Action: Try using a smaller format mask. 12451, 00000, "format mask for TO_LABEL or TO_CHAR function is invalid" // *Cause: The format mask that you specified did not contain valid format // codes for label conversion. // *Action: Check the Trusted ORACLE7 Server Administrators Guide for valid // format codes. Correct the format mask and reattemopt the // operation. 12452, 00000, "error initializing label context" // *Cause: An internal error occurred that prevented initialization of the // label context. This may be caused by internal memory corruption // or a software defect. // *Action: Please contact Oracle WorldWide Technical Support. 12453, 00000, "binary label could not be translated into a string" // *Cause: The binary label that you specified for conversion is not valid. // *Action: Check the source of the binary label. Execute the conversion // with a valid binary label. 12454, 00000, "input string does not contain expected punctuation or literal" // *Cause: The punctuation you supplied in the label string is inconsistent // with the format you specified. // *Action: Change the punctuation in the label string or format, whichever is // appropriate, and reissue the statement. 12455, 00000, "invalid internal format code found" // *Cause: In performing the requested translation, a format code was invalid. // This message may result from memory corruption. // *Action: Please contact Oracle WorldWide Technical Support. 12456, 00000, "duplicate format code specified in string to label conversion" // *Cause: You may not specify duplicate string input when converting to // a binary label. For example, 'SEN SENLEV' is an invalid format // mask. // *Action: Change the format mask and input string to specify a format code // only once. 12457, 00000, "invalid length for MLSLABEL bind variable" // *Cause: A bind variable of type MLSLABEL is too long. // *Action: Consult your documentation for proper datatype lengths. 12458, 00000, "the input string could not be translated into a binary label" // *Cause: The input string you specified is not a valid binary label on your // operating system. // *Action: Check the input string, change any components so that they // form a valid label, and retry the operation. 12459, 00000, "maximum number of columns in a Trusted Oracle table is 253" // *Cause: A CREATE or ALTER TABLE statement tried to add more than 253 // columns (not counting ROWLABEL) to a table. // *Action: Specify no more than 253 columns in your CREATE or ALTER TABLE // command. 12460, 00000, "the value %s for the MLS_LABEL_FORMAT parameter is not valid" // *Cause: The value for the MLS_LABEL_FORMAT parameter you specified does not // contain a valid format mask. You must have a valid // MLS_LABEL_FORMAT parameter for the database to start up. // *Action: Change this parameter setting in your init.ora file to a correct // value. 12461, 00000, "invalid binary label" // *Cause: You provided a binary label in an OCI program's bind // statement that was not a valid operating system label. // *Action: Replace the invalid binary label with one that is valid. 12470, 00000, "process label could not be found" // *Cause: An error was encountered in translating the your operating system // process label into a label number. // *Action: Examine the message stack for a more specific message. 12475, 00000, "cannot log in below DBLOW (%s)" // *Cause: You attempted to log in at a label dominated by DBLOW. You can // only log in to Trusted ORACLE between DBLOW and DBHIGH, inclusive. // *Action: Either log in at a higher label, or lower DBLOW. 12476, 00000, "cannot log in above DBHIGH (%s)" // *Cause: You attempted to log in at a label dominating DBHIGH. You can // only log in to Trusted ORACLE between DBLOW and DBHIGH, inclusive // *Action: Either log in at a lower label, or raise DBHIGH. 12477, 00000, "cannot insert label below DBLOW (%s)" // *Cause: You tried to explicitly insert a value below DBLOW into the // ROWLABEL column, or tried to specify a value lower than DBLOW // in a column of datatype MLSLABEL. Any label you insert into // Trusted ORACLE table must fall between DBLOW and DBHIGH, inclusive. // *Action: Either lower the value of DBLOW, or specify a higher label on // the INSERT or UPDATE statement. 12478, 00000, "cannot insert label above DBHIGH (%s)" // *Cause: You tried to explicitly insert a value above DBHIGH into the // ROWLABEL column, or // tried to specify a value higher than DBHIGH in a column of // datatype MLSLABEL. Any label you insert into a Trusted ORACLE // table must fall between DBLOW and DBHIGH, inclusive. // *Action: Either raise the value of DBHIGH, or specify a lower label on the // INSERT or UPDATE statement. 12480, 00000, "secondary database changing between OS MAC and DBMS MAC modes" // *Cause: An attempt was made to access a secondary database while the // secondary database was in the process of changing between OS MAC // and DBMS MAC modes. // *Action: Re-attempt the operation after the change is complete. 12485, 00000, "cannot find file label for %s" // *Cause: An error was encountered while reading the label of the specified // file. // *Action: Examine the message stack for an operating system message. 12487, 00000, "insufficient privileges to set label to DBHIGH or DBLOW" // *Cause: You must connect to Trusted ORACLE using the INTERNAL keyword // in order to set your label to DBHIGH or DBLOW. // *Action: Connect to Trusted ORACLE using INTERNAL, then set your label to // DBHIGH or DBLOW. If you do not have privileges to connect using // INTERNAL, contact your database administrator. 12488, 00000, "session label must be equal to %s" // *Cause: An attempt was made to log in to an OS MAC database at other than // the database label. // *Action: Log in from an OS process at the specified label. 12489, 00000, "insufficient MAC privileges to alter your session label" // *Cause: You tried to alter your session label without the appropriate // MAC privileges. You must have the appropriate MAC privileges // in order to dynamically change your session label. Note that // MAC privileges are not available in an OS MAC database, only in // a DBMS MAC database. // *Action: To change your session label, do one of the following: // * Change your operating system label. This is your // only alternative in OS MAC mode. This can be done by // logging out of the DBMS, changing your operating system label // within the operating system, and then logging back into the // DBMS. Note that, if you are logging into an OS MAC database, // your operating system label must match the label of your // primary database. // * Obtain the appropriate MAC privileges that allow you to // dynamically change your session label within the DBMS. // You need the READUP and WRITEUP MAC privileges to raise // your session label, and the WRITEDOWN MAC privilege // to lower your label, and all three to alter your // label laterally. Note that changing your session label // does not effect your operating sysem label. 12490, 00000, "cannot alter DBMS label below username creation label (%s)" // *Cause: You attempted to alter your DBMS label to a label lower than // that at which your username was created. You can only alter // your DBMS label between your username's creation label and // DBHIGH, within the limits of your clearance. // *Action: Either do not alter your DBMS label below the specified label, // or contact the database administrator to recreate your username at // lower level. 12491, 00000, "cannot change MAC mode when mounted in READ_COMPATIBLE mode" // *Cause: You tried to change between OS and DB MAC mode while the database // was mounted in READ_COMPATIBLE mode. // *Action: Set the DB_MOUNT_MODE parameter to NORMAL and restart the // database. 12494, 00000, "cannot mount secondary database labeled above DBLOW" // *Cause: The secondary database that you attempted to mount is labeled above // DBLOW in the primary database. You can only mount a secondary // database if that DBHIGH in that database (or, in OS MAC mode, the // label of the database) is lower than DBLOW in your primary // database. // *Action: Determine if you really want to establish a read-secure link // between the two databases. If so, relabel the secondary database // so that DBHIGH in the secondary database is lower than DBLOW in // the primary database. 12495, 00000, "multi-threaded server cannot be used with Trusted Oracle" // *Cause: The MTS_DISPATCHERS parameter is set in the initialization file, // which initiated the configuration of the multi-threaded server. // *Action: Remove the MTS_DISPATCHERS parameter from the initialization file // and restart the instance. / / 12500 - 12699 Reserved for sql*net errors / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 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 maybe 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. If error persists, contact Worldwide Customer // Support. / 12501, 00000, "TNS:listener failed to spawn process" // *Cause: The listener failed to start the program specified. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the alias of the program started by listener in the system // LISTENER.ORA file. Make sure the program exists and the arguments are // correct. // Do not include in error manual. / 12502, 00000, "TNS:listener received no CONNECT_DATA from client" // *Cause: No CONNECT_DATA was passed to the listener. // *Action: Check that the service name resolved from TNSNAMES.ORA has // the CONNECT_DATA component of the connect descriptor. / 12504, 00000, "TNS:listener was not given the SID in CONNECT_DATA" // *Cause: The SID was missing from the CONNECT_DATA. // *Action: Check that the connect descriptor corresponding to the service // name in TNSNAMES.ORA has an SID component in the CONNECT_DATA. / 12505, 00000, "TNS:listener could not resolve SID given in connect descriptor" // *Cause: The SID in the CONNECT_DATA was not found in the listener's tables. // *Action: Check to make sure that the SID specified is correct. // The SIDs that are supported can be obtained by typing // "LSNRCTL STATUS " and matching the SID specified in // TNSNAMES.ORA with one of the SIDs displayed in the services summary. / 12506, 00000, "TNS:listener was not given the ALIAS in CONNECT_DATA" // *Cause: The SID was missing from the CONNECT_DATA. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the command line or name-address mappings for the // ALIAS component of the CONNECT_DATA. // Do not include in error manual. / 12507, 00000, "TNS:listener could not resolve ALIAS given" // *Cause: The ALIAS in CONNECT_DATA was not found in the system // TNSNAMES.ORA file. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check to make sure that the ALIAS specified is correct. // Do not include in error manual. / 12508, 00000, "TNS:listener could not resolve the COMMAND given" // *Cause: The COMMAND given to listener is not supported. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the COMMAND given to listener. This error is probably // caused by incompatible SQL*Net versions. // Do not include in error manual. / 12509, 00000, "TNS:listener failed to redirect client to service handler" // *Cause: The dispatcher terminated unexpectedly // *Action: Attempt to connect again and if the same error occurs, // contact the DBA to check the state of the dispatchers for this SID. // If the problem persists, turn on tracing in the listener to determine // the TNS error caused by the redirect. / 12510, 00000, "TNS:database lacks resources to handle the request for this SID" // *Cause: The dispatchers are busy handling other requests. // *Action: Contact the DBA to increase the number of dispatchers // servicing this SID. / 12511, 00000, "TNS:service handler found but it is not accepting connections" // *Cause: The dispatchers are busy handling other requests and they notified // the listener that they are temporarily busy. // *Action: Attempt the connection again. If error persists, ask // the DBA to increase the number of dispatchers. / 12512, 00000, "TNS:service handler found but it has not registered a redirect address" // *Cause: The dispatcher just came up and has not had time yet to register the // address that a client should be redirected to. // *Action: Attempt the connection again. If error persists, ask // the DBA to increase the number of dispatchers. / 12513, 00000, "TNS:service handler found but it has registered for a different protocol" // *Cause: The dispatchers registered for this service are connected to // the listener by way of a different network protocol than that of the client. // *Action: Contact the DBA to register a dispatcher on your protocol. / / 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 // Worldwide 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 // Worldwide Customer Support. / 12535, 00000, "TNS:operation timed out" // *Cause: The requested connection could not be completed within the timeout // period specified by the CONNECT_TIMEOUT parameter in listener.ora. This // error arises from the tnslsnr. // *Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means // wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher // value. Or, if the timeout is unacceptably long, turn on tracing // for further information. / 12536, 00000, "TNS:operation would block" // *Cause: An internal operation did not commence because to do so would // block the current process and the user has requested that operations be // non-blocking. // *Action: None needed; this is an information message. / 12537, 00000, "TNS:connection closed" // *Cause: "End of file" condition has been reached; partner has disconnected. // *Action: None needed; this is an information message. / 12538, 00000, "TNS:no such protocol adapter" // *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" // keyword-value pair in a TNS address) is unknown. If the supplied address // is typographically correct then the protocol adaptor is not installed. // *Action: Install the protocol adapter or correct typographically error, // as appropriate. Note: if the supplied address was derived from // resolving the service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). / 12539, 00000, "TNS:buffer over- or under-flow" // *Cause: Buffer too small for incoming data or too large for outgoing data. // *Action: This restriction (which is associated with CONNECT DATA) is not // normally visible to the user. For further details, turn on tracing and // reexecute the operation; contact Worldwide 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 // Worldwide Customer Support. / 12545, 00000, "TNS:name lookup failure" // *Cause: A protocol specific ADDRESS parameter cannot be resolved. // *Action: Ensure the ADDRESS parameters have been entered correctly; // the most likely incorrect value is the node name. / 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 // Worldwide 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 // Worldwide 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 // Worldwide 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. / 12560, 00000, "TNS:protocol adapter error" // *Cause: A generic protocol adapter error occurred. // *Action: Check addresses used for proper protocol specification. Before // reporting this error, look at the error stack and check for lower level // transport errors.For further details, turn on tracing and reexecute the // operation. Turn off tracing when the operation is complete. / 12561, 00000, "TNS:unknown error" // *Cause: A generic protocol error occurred. // *Action: For further details, turn on tracing and reexecute the operation. / 12562, 00000, "TNS:bad global handle" // *Cause: Internal error - bad 'gbh' agrument passed to TNS from caller. // System may have been linked with old libraries. // *Action: Not normally visible to the user, contact Worldwide 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 Worldwide 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 // Worldwide 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 // Worldwide 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 // Worldwide Customer Support. / 12582, 00000, "TNS:invalid operation" // *Cause: An internal function received an invalid request. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide 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 // Worldwide 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 // Worldwide 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 // Worldwide 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 // Worldwide 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 Worldwide 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 Worldwide 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 // Worldwide Customer Support. / 12595, 00000, "TNS:no confirmation" // *Cause: TNS is unable to get requested confirmation acknowledgement from // remote partner. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide 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 Worldwide 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 // Worldwide Customer Support. / 12598, 00000, "TNS: operation failed due to error returned by native service" // *Cause: The TNS native service component returned an error. // *Action: Details of the exact violation are reported in the "secondary // error" field of the TNS result descriptor. If necessary, turn on // tracing and reexecute the operation to see the result descriptor. / 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. / / 12610 - 12629 ns secondary errors / /12611, 00000, "TNS:operation is not portable" // *Cause: Attempted operation is not portable. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / /12612, 00000, "TNS:connection is busy" // *Cause: Attempted operation failed because it conflicts with an on-going // action or status of the connection. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide 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 // Worldwide 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 // Worldwide Customer Support. / /12617, 00000, "TNS:bad 'what' type" // *Cause: The operation failed because the type of data specified is unknown. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. Iferror persists, contact // Worldwide 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 Worldwide 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 // Worldwide 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 Worldwide 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 Worldwide 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 Worldwide 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 Worldwide 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 Worldwide Customer // Support. / / 12630 - 12699 Reserved for NA errors. / 12630, 00000, "TNS: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, "TNS:name 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, "TNS: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, "TNS: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, "TNS:memory allocation failed" // *Cause: Process was unable to allocate memory. // *Action: Terminate other processes in order to reclaim needed memory. / 12635, 00000, "TNS: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, "TNS: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 Worldwide Customer Support. / 12637, 00000, "TNS: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 Worldwide Customer Support. / 12638, 00000, "TNS: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, "TNS: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, "TNS:authentication service 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, "TNS:authentication service failed to initialize" // *Cause: The authentication service failed during initialization. // *Action: Enable tracing to determine the exact error. / 12642, 00000, "TNS: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, "TNS:process communication failed" // *Cause: A process was unable to communicate with 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 Worldwide Customer Support. / 12644, 00000, "TNS:authentication service initialization failed" // *Cause: The routine called to initialize the authentication adapter failed. // *Action: Enable tracing to determine the exact error. A likely cause is that // memory is exhausted. / 12645, 00000, "TNS: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, "TNS: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, "TNS: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, "TNS:encryption or data integrity algorithm list empty" // *Cause: A SQL*Net list-of-algorithms parameter was empty, e.g. // "()". // *Action: Change the list to contain the name of at least one // installed algorithm, or remove the list entirely if every // installed algorithm is acceptable. / 12649, 00000, "TNS:unknown encryption or data integrity algorithm" // *Cause: A SQL*Net list-of-algorithms parameter included an // algorithm name that was not recognized. // *Action: Either remove that algorithm name, correct it if it was // misspelled, or install the driver for the missing // algorithm. / 12650, 00000, "TNS: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, "TNS: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 Worldwide Customer Support. / 12652, 00000, "TNS:string truncated" // *Cause: Not enough memory was allocated for a string so it had to be // trucated // *Action: If it is OK that the string is truncated, then it is not an // error. Otherwise, call the routine that reported the error // again with a larger string buffer. / 12653, 00000, "TNS: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, "TNS: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, "TNS: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, "TNS: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, "TNS: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, "TNS:native service required but TNS version is incompatible" // *Cause: A process that is running an earlier version of TNS attempted to // connect but the connection failed because the server process // required that a native 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, "TNS: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. / 12699, 00000, "TNS:native service internal error" // *Cause: An internal error occurred in the native services component. // *Action: Enable tracing to determine the exact error. Contact Worldwide // Customer Support. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12700 - 12799 Reserved for NLS / 12700, 00000, "invalid NLS parameter value (%s)" // *Cause: An invalid or unknown NLS configuration parameter was specified. // *Action: 12701, 00000, "CREATE DATABASE character set is not known" // *Cause: The character set specified when creating the database is unknown. // *Action: 12702, 00000, "invalid NLS parameter string used in SQL function" // *Cause: An unknown parameter name or invalid value is specified in a NLS // parameter string. // *Action: 12703, 00000, "this character set conversion is not supported" // *Cause: The requested conversion between two character sets in the CONVERT // function is not implemented // *Action: / / 12704 free for future use / 12705, 00000, "invalid or unknown NLS parameter value specified" // *Cause: The NLS parameter value specified in an alter session statement // is not valid or not implemented. // *Action: 12706, 00000, "this CREATE DATABASE character set is not allowed" // *Cause: It is not allowed to create a database on a native ASCII-based // machine using an EBCDIC-based character set, and vice versa. // *Action: 12707, 00000, "error while getting create database NLS parameter %s" // *Cause: Internal error // *Action: 12708, 00000, "error while loading create database NLS parameter %s" // *Cause: Internal error // *Action: 12709, 00000, "error while loading create database character set" // *Cause: Internal error // *Action: / / / 12800 - 12849 Reserved for Parallel Query/Index Creation / / 12800, 00000, "system appears too busy for parallel query execution" // *Cause: load on system is too high to perform parallel queries. // *Action: re-execute serially or wait until system load is reduced. / 12801, 00000, "error signaled in parallel query server %s" // *Cause: A parallel query server reached an exception condition. // *Action: Check the following error message for the cause, and consult // your error manual for the appropriate action. // *Comment: This error can be turned off with event 10397, in which // case the server's actual error is signaled instead. / 12802, 00000, "parallel query server lost contact with coordinator" // *Cause: A parallel query server lost contact with the foreground // (coordinator) process/thread. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. / 12803, 00000, "parallel query server lost contact with another server" // *Cause: A parallel query server lost contact with another server. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. / 12804, 00000, "parallel query server appears to have died" // *Cause: Cannot find process information for a parallel query // server thread. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. / 12805, 00000, "parallel query server died unexpectedly" // *Cause: A parallel query server died unexpectedly, PMON cleaning // up the process. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. See trace file for more details. / 12806, 00000, "could not get background process to hold enqueue" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // contact your customer service representative. / 12807, 00000, "process queue could not receive parallel query message" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // contact your customer service representative. / 12808, 00000, "cannot set %s_INSTANCES greater than number of instances %s" // *Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES // using the ALTER SYSTEM command to a value larger than the number // of available instances. // *Action: See the accompanying message for the current allowable // maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES // to ALL. / 12809, 00000, "cannot set %s_INSTANCES when mounted in exclusive mode" // *Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES // using the ALTER SYSTEM command while the database was mounted // in exclusive mode. // *Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless // running Oracle parallel server mounted in SHARED or PARALLEL // mode. / 12810, 00000, "PARALLEL_MAX_SERVERS must be less than or equal to %s" // *Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter // to a value higher than the maximum allowed by the system. // *Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to // the maximum specified in the accompanying message and retry. / 12811, 00000, "PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, %s" // *Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter // to a value higher than PARALLEL_MAX_SERVERS. // *Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to // PARALLEL_MAX_SERVERS (indicated in the accompanying message) // and retry. / 12812, 00000, "only one PARALLEL or NOPARALLEL clause may be specified" // *Cause: PARALLEL was specified more than once, NOPARALLEL was specified // more than once, or both PARALLEL and NOPARALLEL were specified // in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or // CLUSTER statement, or in a RECOVER command. // *Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and // reissue the statement. / 12813, 00000, "value for PARALLEL or DEGREE must be greater than 0" // *Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, // CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement. // *Action: Specify a degree of parallelism greater than 0 or specify // default parallelism using PARALLEL with no degree or using // DEGREE DEFAULT within a PARALLEL clause. / 12814, 00000, "only one CACHE or NOCACHE clause may be specified" // *Cause: CACHE was specified more than once, NOCACHE was specified more // than once, or both CACHE and NOCACHE were specified in a // CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER // statement. // *Action: Remove all but one of the CACHE or NOCACHE clauses and // reissue the statement. / 12815, 00000, "value for INSTANCES must be greater than 0" // *Cause: PARALLEL parameter specifying number of instances must // be a positive integer or DEFAULT // *Action: specify a positive integer or DEFAULT for INSTANCES // if parallelism across instances is desired. / 12816, 00000, "parallel create index fastpath operation" // *Cause: // *Action: set this event only under the supervision Oracle development // *Comment: this event permits fastpath index creation. it merges // sub-index in a quick but suboptimal fashion wrto space usage. // Level: the level indicates the number of rows in a branch block // that we are willing to copy before attempting fastpath operation. / 12817, 00000, "parallel query option must be enabled" // *Cause: A parallel query option feature has been invoked but this option // has not been enabled. // *Action: Enable the parallel query option. / 12818, 00000, "invalid option in PARALLEL clause" // *Cause: an unrecognized option was used within a PARALLEL clause. // *Action: specify any combination of DEGREE { | DEFAULT } and // INSTANCES { | DEFAULT } within the PARALLEL clause. / 12819, 00000, "missing options in PARALLEL clause" // *Cause: PARALLEL clause cannot be empty. // *Action: specify any combination of DEGREE { | DEFAULT } and // INSTANCES { | DEFAULT } within the PARALLEL clause. / 12820, 00000, "invalid value for DEGREE" // *Cause: invalid value for DEGREE was specified within a PARALLEL // clause. // *Action: specify a positive integer or DEFAULT for the DEGREE // option within a PARALLEL clause. / 12821, 00000, "invalid value for INSTANCES" // *Cause: invalid value for INSTANCES was specified within a PARALLEL // clause. // *Action: specify a positive integer or DEFAULT for the INSTANCES // option within a PARALLEL clause. / 12822, 00000, "duplicate option in PARALLEL clause" // *Cause: DEGREE or INSTANCES was specified more than once within // a PARALLEL clause. // *Action: specify each desired PARALLEL clause option only once. / 12823, 00000, "default degree of parallelism may not be specified here" // *Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was // specified in the PARALLEL clause of an ALTER DATABASE RECOVER // command. // *Action: respecify with an explicit degree of parallelism. / 12824, 00000, "INSTANCES DEFAULT may not be specified here" // *Cause: INSTANCES DEFAULT was specified in the PARALLEL clause // of an ALTER DATABASE RECOVER command // *Action: respecify with an explicit value for INSTANCES or omit // the INSTANCES option if single instance recovery is desired. / 12825, 00000, "explicit degree of parallelism must be specified here" // *Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER // command. // *Action: respecify with an explicit degree of parallelism. / 12826, 00000, "hung parallel query server was killed" // *Cause: parallel query server was hung and subsequently killed. // *Action: re-execute query and report suspicious events in trace // file to Oracle support representative if error persists. / / 12827, 00000, "insufficient parallel query slaves available" // *Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than // minimum slaves were acquired // *Action: either re-execute query with lower PARALLEL_MIN_PERCENT or // wait until some running queries are completed, thus freeing // up slaves / 12828 - 12849 unused (parallel query/index creation messages) / / / / 13000 - 13199 (Reserved for Oracle7 Spatial Data Option) / / 13000, 00000, "dimension number is out of range" // *Cause: The specified dimension is either smaller than 1 or greater than // the number of dimensions encoded in the HHCODE. // *Action: Make sure that the dimension number is between 1 and the maximum // number of dimensions encoded in the HHCODE. / 13001, 00000, "dimensions mismatch error" // *Cause: The number of dimensions in two HHCODEs involved in a binary // HHCODE operation do not match. // *Action: Make sure that the number of dimensions in the HHCODEs match. / 13002, 00000, "specified level is out of range" // *Cause: The specified level is either smaller than 1 or greater // than the maximum level encoded in an HHCODE. // *Action: Verify that all levels are between 1 and the maximum number of // levels encoded in the HHCODE. / 13003, 00000, "the specified range for a dimension is invalid" // *Cause: The specifed range for a dimension is invalid. // *Action: Make sure that the lower bound (lb) is less than the upper bound // (ub). / 13004, 00000, "the specified buffer size is invalid" // *Cause: The buffer size for a function is not valid. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13005, 00000, "recursive HHCODE function error" // *Cause: An error occured in a recursively called HHCODE function. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13006, 00000, "the specified cell number is invalid" // *Cause: The cell identifier is either less than 0 or greater that // (2^ndim - 1). // *Action: Make sure that the cell identifier is between 0 and (2^ndim - 1). / 13007, 00000, "an invalid HEX character was detected" // *Cause: A character that is not in the range [0-9] or [A-Fa-f] was // detected. // *Action: Verify that all characters in a string are in [0-9] or [A-Fa-f]. / 13008, 00000, "the specified date format has an invalid component" // *Cause: Part of specified date format is invalid. // *Action: Verify that the date format is valid. / 13009, 00000, "the specified date string is invalid" // *Cause: The specified date string has a bad component or does not match // the specified format string. // *Action: Make sure that the components of the date string are valid and // that the date and format strings match. / 13010, 00000, "an invalid number of arguments has been specified" // *Cause: An invalid number of arguments was specified for an HHCODE function. // *Action: Verify the syntax of the function call. / 13011, 00000, "value is out of range" // *Cause: A specifed dimension value is outside the range defined for that // dimension. // *Action: Make sure that all values to be encoded are within the defined // dimension range. / 13012, 00000, "an invalid window type was specifed" // *Cause: An invalid window type was specifed. // *Action: Valid window types are RANGE, PROXIMITY, POLYGON. / 13013, 00000, "the specified topology was not INTERIOR or BOUNDARY" // *Cause: A topology was specified that was not INTERIOR or BOUNDARY. // *Action: Make sure that INTERIOR or BOUNDARY is used to describe an // HHCODE's topology. / 13014, 00000, "a topology identifier outside the range of 1 to 8 was specified" // *Cause: A topology identifier outside the range of 1 to 8 was specified // *Action: Specify a topology in the range of 1 to 8. / 13015, 00000, "the window definition is not valid" // *Cause: The number of values used to define the window does not // correspond to the window type. // *Action: Verify that the number of values used to defined the window is // correct for the window type and number of dimensions. / 13016, 00000, "bad partition definition" // *Cause: The partition common code was not correctly decoded. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13017, 00000, "unrecognized line partition shape" // *Cause: The shape of a 2-D line partition could not be determined. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13018, 00000, "bad distance type" // *Cause: The specified distance type is invalid. // *Action: The only supported distance functions are EUCLID and MANHATTAN. / 13100, 00000, "badly formed request frame" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13101, 00000, "partition name datatype should be varchar2" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13102, 00000, "reply pipe name datatype should be varchar2" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13103, 00000, "failed to acknowledge on pipe %s due to timeout" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13104, 00000, "failed to send reply on pipe %s due to timeout" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13105, 00000, "buffer overflow encountered on pipe %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13106, 00000, "acknowledgment on pipe %s interrupted" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13107, 00000, "reply on pipe %s interrupted" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13108, 00000, "spatial table %s not found" // *Cause: The specified spatial table does not exist. // *Action: Check the Spatial Data option data dictionary to make sure // that the table exists. / 13109, 00000, "spatial table %s exists" // *Cause: The specified spatial table exists. // *Actions: Drop the existing table or use a different name. / 13110, 00000, "spatial table %s is not partitioned" // *Cause: The specified spatial table is not partitioned. // *Actions: Check the Spatial Data option data dictionary and make sure // that a high water mark is set. / 13111, 00000, "spatial table %s has no partition key defined" // *Cause: The specified spatial table does not have a partition key defined. // *Actions: Check the Spatial Data option data dictionary and make sure // that the table is partitioned. / 13112, 00000, "invalid count mode %s" // *Cause: The specified count mode is not valid. // *Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT. / 13113, 00000, "Oracle table %s does not exists" // *Cause: The specified Oracle table does not exist. // *Action: Check the Oracle7 data dictionary and make sure that the table // exists. / 13114, 00000, "tablespace %s not found" // *Cause: The specified tablespace does not exist. // *Action: Check the Spatial Data option data dictionary and make sure // that the specified tablespace exists and that there is a space // quota defined on it. / 13115, 00000, "tablespace %s is already allocated" // *Cause: The specified tablespace is already allocated to the spatial table. // *Action: Allocate another tablespace name to the table. / 13116, 00000, "tablespace %s is not allocated to table %s" // *Cause: The specified tablespace is not allocated to the specified spatial // table. // *Action: Allocate the tablespace to the spatial table. / 13117, 00000, "partition %s not found" // *Cause: The specified partition does not exist. // *Action: Verify the name of the partition by checking the Spatial Data // option data dictionary. / 13118, 00000, "partition %s is offline" // *Cause: The specified partition is offline. // *Action: Bring the partition online and then retry the operation. / 13119, 00000, "source and target tablespaces are identical" // *Cause: Identical source and target tablespaces were specified when trying // to move partition. // *Action: Specify different source and target tablespaces if you wish to // move a partition. / 13120, 00000, "SD*POD is not listening on pipe %s" // *Cause: There is no partition operation daemon listening on the specifed // pipe. // *Action: Start a daemon listening on the pipe by using the LISTEN command // line option of SD*POD. / 13121, 00000, "failed to create child partition" // *Cause: The creation of a child partition failed. // *Action: Check for other errors that accompany this error and correct them // first. / 13122, 00000, "child partition %s not found" // *Cause: This is an internal error. // *Action Document messages and contact Oracle Worldwide Support. / 13123, 00000, "column %s is already defined" // *Cause: The specified column is already defined for the spatial table. // *Action: Use a different column name. / 13124, 00000, "unable to determine columnd id for column %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13125, 00000, "partition key is already set" // *Cause: A partition key is already set for the spatial table. // *Action: Only one partition key can be specified per spatial table. / 13126, 00000, "unable to determine class for spatial table %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13127, 00000, "failed to generate target partition" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13128, 00000, "failed to identify dimensions for column %s" // *Cause: The dimension definitions could not be found for the specified // column. // *Action: Make sure that the specified column is a spatial column. / 13129, 00000, "HHCODE column %s not found" // *Cause: The specified spatial column does not exist. // *Action: Verify that the specified column is a spatial column by checking // the Spatial Data option data dictionary. / 13130, 00000, "timed out waiting for reply on %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13131, 00000, "record in pipe %s is too big" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13132, 00000, "pipe read on %s was interrupted" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13133, 00000, "archive request failed" // *Cause: The request to archive a partition failed. // *Action: Check the log file and correct any errors indicated. / 13134, 00000, "restore request failed" // *Cause: The request to restore a partition failed. // *Action: Check the log file and correct any errors indicated. / 13135, 00000, "duplicate offline path" // *Cause: The offline path specifed is already being used by another // spatial table. // *Action: Use a different offline path. / 13136, 00000, "null common code generated" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13138, 00000, "could not determine name of object %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13139, 00000, "could not obtain column definition for %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13140, 00000, "invalid target type" // *Cause: The specified target type is not valid. // *Action: Substitute a valid target type. Valid target types are TABLE or // VIEW. / 13141, 00000, "invalid RANGE window definition" // *Cause: The RANGE window specified is not correctly defined. // *Action: A RANGE window is defined by specifying the lower and upper // boundary of each dimension as a pair of values // (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). // There should be an even number of values. / 13142, 00000, "invalid PROXIMITY window definition" // *Cause: The PROXIMITY window specified is not correctly defined. // *Action: A PROXIMITY window is defined by specifying a center point and a // radius. The center point is defined by ND values. There should // be ND+1 values. / 13143, 00000, "invalid POLYGON window definition" // *Cause: The POLYGON window specified is not correctly defined. // *Action: A POLYGON window is defined by specifying N pairs of values // that represent the vertices of the polygon. There should be // an even number of values. / 13144, 00000, "target table %s not found" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13145, 00000, "failed to generate range list" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13146, 00000, "could not find table substitution variable %s" // *Cause: The partition name substitution variable %s was not found in the // SQL filter. // *Action: The substitution variable %s must be in the SQL filter to indicate // where that partition name should be placed. / 13147, 00000, "failed to generate MBR" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13148, 00000, "failed to generate SQL filter" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13149, 00000, "failed to generate next sequence number for spatial table %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13150, 00000, "failed to insert exception record" // *Cause: Operation failed to insert a record into the exception table // *Action: Fix any other errors reported. / 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. / 13197, 00000, "only MDSYS can execute %s" // *Cause: You tried to execute a restricted procedure. // *Action: Only MDSYS can execute the specified partition. / / 13198, 00000, "Oracle error ORA%s encountered" // *Cause: Specified Oracle error was encountered. // *Action: Correct the Oracle error. / / / / 14000 - 14999 Reserved for Partitioned Objects Project (PTI) / / 14000 - 14099 Reserved for new parse (syntax) error introduced by / the Partitioned Objects Project (PTI) / 14400 - 14499 Reserved for new execution errors introduced by the / Partitioned Objects Project (PTI) / 14500 - 14549 Reserved for new analyze errors introduced by the / Partitioned Objects Project (PTI) / 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, must be between -20000 and -20999, inclusive" // *Cause: // *Action: Use an error number in the range of -20000 to -20999, inclusive. / / 21100 - 21299 Reserved for CORE / / 21300 - 22999 Reserved for OI/KO/KG (Object Interface and Subsystem) / / 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, 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 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. 23311, 00000, "object group %s is quiesced" // *Cause: Suspend_master_activity has been called before the object group // has resumed normal operation. // *Action: If a resume_master_activity request is pending, wait until it // completes, and then reinvoke suspend_master_activity. 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 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_snapshot_master if the // invocation database is a snapshot site. 23314, 00000, "database is not a snapshot site for %s" // *Cause: The invocation database is not a snapshot database for the given // object group. // *Action: Connect to the desired snapshot database and retry the request, // or make the invocation database a snapshot site with // create_snapshot_repschema or create_snapshot_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: One of the masters to be removed is the masterdef // *Action: Relocate the masterdef to a master that will not be removed, and // then reinvoke the remove_master_databases request at the new // masterdef. 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 2000 bytes for char/varchar2 parameters and 255 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, "the system is being quiesced" // *Cause: A deferred rpc operation was attempted while the database // was quiesced. // *Action: Resume database activity with the dbms_repcat.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, "snapshot base table \"%s\".\"%s\" differs from master table \"%s\".\"%s\"" // *Cause: When creating a snapshot through repcat, the snapshot base table // name did not match a replicated table name at the master. // *Action: Change the snapshot ddl to use the same base table as the // replicated table name at the master. // 23329, 00000, "successful user-provided ddl but no snapshot \"%s\".\"%s\"" // *Cause: The DDL provided by the user to create a snapshot was executed // without error, but snapshot does not exist. // *Action: Manually back-out the DDL, and reregister with matching ddl // and snapshot. // 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 is undefined for table %s" // *Cause: Trying to generate replication support for a table without // a primary key as defined by a constraint or dbms_repcat.set_columns. // *Action: Add a primary key constraint to the table or define a primary key // using dbms_repcat.set_columns. // 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" // *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\"" // *Cause: Deferred RPC can not be executed at the destination because // their propogation has been disabled. // *Action: Enable deferred RPC execution with the dbms_defer_sys.enable 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. 23360, 00000, "only one snapshot for master table \"%s\" can be created" // *Cause: Trying to create more than one snapshot on a given master // table in the same rep group. // *Action: Create these other snapshots in a different rep group at another // site. // 23361, 00000, "snapshot \"%s\" does not exist at master site" // *Cause: The snapshot does not exist at the master site for offline // instantiation of the snapshot. // *Action: The correct procedure is to create the snapshot in a different // schema at the master site, and then follow the instructions // for offline instantiation of snapshots. // 23363, 00000, "mismatch of snap base table \"%s\" at master and snap site" // *Cause: The name of the base table of the snapshot at the master site // is different from the base table at the snapshot site. This // error may arise during offline instantiation of snapshots. // *Action: Retry offline instantiation with a snapshot name less than 24 bytes // 23364, 00000, "replication option not installed" // *Cause: The replication option was not installed at this site. Updatable // snapshots, deferred RPCs, and other replication features were, // therefore, unavailable. // *Action: Install the replication option. The replication option is not // part of the Oracle7 Server product and must be purchased // separately. Contact an Oracle Sales representative if the // replication option needs to be purchased. // 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 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 already exists" // *Cause: The given database already replicates the given object group. // *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" // *Cause : The connection qualifier used in the database link for the // specified object group does 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 is misspelled, or is not supported. // *Action: Refer to the manual on replicated data for valid propagation modes. // 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. // // 23385-23399 reserved for DBMS_LOB PL/SQL package // 23400, 00000, "invalid snapshot name \"%s\"" // *Cause: A null, misspelled, or badly formed snapshot name was given to // dbms_snapshot.refresh. // *Action: Provide a valid snapshot name to dbms_snapshot.refresh. // 23401, 00000, "snapshot \"%s\".\"%s\" does not exist" // *Cause: A snapshot name was given to dbms_snapshot.refresh that is not // in sys.snap$ or its associated views. // *Action: Provide a snapshot name that is in sys.snap$, all_snapshots // or user_snapshots. // 23402, 00000, "refresh was aborted because of conflicts caused by deferred txns" // *Cause: There are outstanding conflicts logged in the DefError table // at the snapshot'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 snapshot'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 snapshot and does not have // ALTER ANY SNAPSHOT privileges. // *Action: Perform the operation as the owner of the snapshot or as a // user with ALTER ANY SNAPSHOT privileges. // 23407, 00000, "object name %s must be shaped like \"schema\".\"object\" or \"object\"" // *Cause: The object name (e.g., the rollback segment, the snapshot name, // the refresh group) was incorrectly specified. // *Action: Retry the operation with the object name properly specified // (like "schema"."object" or "object") // 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, "snapshot \"%s\".\"%s\" is already in a refresh group" // *Cause: A snapshot of the same name is already in a refresh group. // *Action: Subtract the snapshot 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, "snapshot \"%s\".\"%s\" is not in refresh group \"%s\".\"%s\"" // *Cause: The specified snapshot is not in the specified refresh group. // *Action: Try again with the proper snapshot and refresh group names. // 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. 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. // 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. / / 24300 - 24999 Reserved for OCI/UPI/TTC/OPI/RPI/PSDs etc / 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 of the data. // *Action: Make sure that the length of this piece and the cumulative length of // all the previous pieces is not more than the progvl parameter // specified in the obindps call. / / 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. / / 25100-25199 Reserved for Parser errors (e.g. v7) 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. / / 25200-25699 Reserved for Advanced Queueing 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, "BITMAP may not be used with a cluster index" // *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 14" // *Cause: // *Action: / / 32767 - (MAX ERROR NUMBER; NONE CAN BE LARGER) /