home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-04 | 130.6 KB | 3,082 lines |
- /
- / $Header: error.msg,v 6002709.5 89/12/07 00:08:51 dosterbe Exp $ error.msg Copyr (c) 1989 Oracle
- /
- / Copyright (c) 1987 by the Oracle Corporation. All rights reserved.
- /
- / File: v6$knl:[olb]error.msg
- / Created: 10/17/86
- / Note: Message text should be limited to a maximum of 76 characters.
- / Messages containing embedded % directives should not overrun
- / the 76 character limit unless they signal unusual errors
- / which do not occur as part of user applications. For example,
- / startup errors and system-dependent errors can probably get
- / away with longer message text.
- / MODIFIED:
- / Hong 11/08/89 - add trace 10235
- / Harmon 10/28/89 - replication project, add 1917, 2290-2293
- / Heigham 10/12/89 - reserve range for loader
- / Mendelsohn 09/28/89 - reserve range for mvs sql*net
- / Porter 08/29/89 - add sllf errors 7840-7859
- / Bridge 06/27/89 - add 1154-1157 problems getting enqueues
- / Tan 06/27/89 - add event 10234 for recovery test
- / Mendelsohn 06/23/89 - bug 25806: reinstate error 1854
- / Porter 06/14/89 - add message 7640 for SGA validation
- / Bridge 05/20/89 - add messages for multi-thread recovery
- / Mendelsohn 05/18/89 - reserve errors for os/2 and msdos
- / Lambert 05/08/89 - add packed decimal-to-oranum conversion errors
- / Cyril 05/04/89 - add NETDNT, NETTCP, NETCMN and TWOTASK errors
- / Mendelsohn 05/03/89 - add more errors reserved for unix and mpexl ports
- / Hong 03/21/89 - add 1590
- / Loaiza 04/07/89 - expanded description for 0700
- / Hong 03/21/89 - add 10233
- / Bridge 03/15/89 - add 1128, 1140, 1142, 1149, 1150
- / Porter 02/14/89 - add 7826, 7827, 7830, modify 7820, 7821, 7825
- / Loaiza 02/01/89 - added 10046
- / Chris 01/09/89 - Added "(%s)" to 8101 and 8102
- / Porter 12/27/88 - Added SPS errors (7820-7839)
- / Mendelsohn 12/16/88 - add precompiler error messages
- / Wijaya 12/13/88 - add error 1082
- / Peeler 12/04/88 - add errors 2401,2402, 2403, 2404
- / Chin 11/21/88 - add trace 10232
- / Chris 11/20/88 - add trace 10231
- / Porter 11/18/88 - Changing ORACLE$SID to ORA_SID (#7582)
- / Wijaya 11/10/88 - marketing revisions
- / Bulchan 11/01/88 - Delete error 1579
- / Wijaya 10/31/88 - change error 2030
- / Mendelsohn 10/30/88 - add error 1716
- / Wijaya 10/27/88 - add error 701
- / Bulchan 10/27/88 - delete 1140, 1854, 916, 2266, 1142
- / modify 1511, 1516, 1525, 4001
- / Mendelsohn 10/25/88 - delete errors 4011 and 8003
- / Grant 10/21/88 - add control file backup errors: 1582 - 1587
- / Mendelsohn 10/21/88 - delete errors 960 through 963; merge 2179 and
- / 2188 into 2216
- / Porter 10/21/88 - add error 7554
- / Wijaya 10/21/88 - delete event 10034 (obsolete due to new EXPLAIN)
- / Bamford 10/20/88 - add event 10230 - copy kco before applying
- / Mendelsohn 10/18/88 - delete error 1029; fix message for 1107;
- / fix message for 1024; delete 2009;
- / Wijaya 10/18/88 - add error 2274 and 2275
- / Hong 10/12/88 - add error 1079, modify 1562
- / Wijaya 09/19/88 - add error
- / Hong 09/19/88 - remove error 1128, document error
- / Bulchan 09/12/88 - add error 1508
- / Hong 09/07/88 - add error
- / Bulchan 08/20/88 - add error 1897
- / Lambert 08/15/88 - add error 1483
- / Mendelsohn 08/04/88 - reserve error range for sql connect/ims;
- / shorten messages 1105 and 2205;
- / add note on message text length.
- / Hong 08/09/88 - add merror 1558
- / Wijaya 08/04/88 - 1019: remove
- / Goldber 08/02/88 - add causes and actions for VMS OSD errors
- / Wijaya 07/28/88 - 2265: add
- / Hong 07/26/88 - add 1576
- / Wijaya 07/25/88 - 1506: improve
- / Grant 07/25/88 - add trace 10228
- / Chris 07/22/88 - add trace 10227
- / Bulchan 07/22/88 - add 1859
- / Mendelsohn 07/20/88 - add error ranges for native Macintosh and DG AOS;
- / - free old DG error range.
- / Wijaya 07/18/88 - 976: add new error
- / Moore 07/14/88 - add sgapad byte string to insuff. sgapad error msgs
- / Moore 07/13/88 - 1409: create index nosort requires sort.
- / Wijaya 07/13/88 - 1408: "column" -> "such column list"
- / Mendelsohn 07/12/88 - give ctos an error range
- / Wijaya 06/22/88 - 983: add new error
- / Wijaya 06/14/88 - 1536: add "no resource privilege or"
- / Wijaya 06/03/88 - 1547: get rid of ugly single quotes for allocation size
- / Mendelsohn 06/01/88 - move and expand cms range; add more sql*net errors
- / Harmon 06/01/88 - error for use_row_enqueues
- / Mendelsohn 05/16/88 - fix message for 10038
- / Goldberg 05/08/88 - add index trace
- / Mendelsohn 05/08/88 - editing suggested by Tom Portfolio
- / Hong 05/01/88 - add error 1569, 58
- / Forest 04/27/88 - add soarc errors
- / Mendelsohn 04/27/88 - add error 2201
- / Wijaya 04/20/88 - enhance error 1463 message to handle revoke as well
- / Mendelsohn 04/17/88 - improve error 1506 causes
- / Hong 04/13/88 - add error 1568
- / Wijaya 04/06/88 - add error 964
- / Grant 04/06/88 - add errors 1565-7
- / Mendelsohn 04/05/88 - change text of 972; add text for 3122
- / Mendelsohn 04/01/88 - add cause/action for new v6 sql errors;
- / delete obsolete v5 errors
- / Wijaya 04/01/88 - add cause/action for error 2250 - 2289
- / Hong 03/31/88 - merge in andy's changes and add cause/action for
- / some errors, add error 1025
- / Derry 03/30/88 - add error range for Wang port
- / Grant 03/27/88 - add 1139, 1140 for manual recovery
- / Kabcenell 03/27/88 - add recursive SQL error
- / Mendelsohn 03/21/88 - fix bug 10439 (renumber various errors reserved in v5)
- / Chris 03/18/88 - add 10220, 10221 for debugging
- / Freeland 03/18/88 - add 1466
- / Wijaya 03/18/88 - remove 2274 and 2275
- / Chris 03/18/88 - add trace 10219
- / Forrest 03/17/88 - update sf errors
- / Derry 03/17/88 - change comments; reword 1089, 1090
- / Mendelsohn 03/15/88 - rename to error.msg
- / - reword text for 3006
- / Grant 03/14/88 - add 2288, 1137, 1138
- / Chris 03/14/88 - add code for debugging sequence numbers
- / Mendelsohn 03/08/88 - fix 1462; delete 1079
- / Chris 03/08/88 - add 04013
- / Freeland 03/07/88 - read only transaction errors
- / Hong 03/06/88 - add 1562
- / Derry 03/06/88 - typo in 7560
- / Chris 03/03/88 - add more errors for sequences
- / Mendelsohn 02/25/88 - fix bug 11006 (typos) and db_id -> db_name
- / Wijaya 02/23/88 - add errors for sequence
- / Hong 02/16/88 - add 481
- / Mendelsohn 02/14/88 - made 1470 an internal error (12310)
- / Wijaya 02/09/88 - more errors for integrity constraint
- / Evan 02/8/88 - add trace events 10212-15 for control file testing
- / Mendelsohn 02/8/88 - removed "alter database:" from 1506 thru 1512
- / Hong 02/5/88 - add err# 1561, # 474
- / Chris 02/5/88 - code for validate cluster (ksepec)
- / Forrest 01/36/88 - add kcm error
- / Kabcene 01/20/88 - reserve OSD ranges
- / Wijaya 01/12/88 - errors for constraint supports
- / Mendelsohn 01/06/88 - change error 959 to use text of 1519 and delete 1519;
- / - delete errors 964, 965, 1011, 1036, 1051, 1409, 1411,
- / - 1412, 1426, 1442, 1451, 1456, 1466, 1469, 1479, 1716
- / Klein 01/05/99 - add 1057
- /
- / List of V6 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 .. 20000 are reserved for debug event codes that are
- / not really errors.
- /
- /
- 00000, 00000, "normal, successful completion"
- // *Cause: Normal exit
- // *Action: None
- 00001, 00000, "duplicate key in index"
- // *Cause: An index that was specified as unique has duplicate keys
- // *Action: Either remove the unique restriction or don't insert the key
- /0002 reserved for v2 compatibility (null column)
- /0003 reserved for v2 compatibility (column value trunctated)
- /0004 reserved for v2 compatibility (end-of-fetch)
- /0009 reserved for v2 compatibility
- /
- 00014, 00000, "there is no session number %s in this process"
- // *Cause: Programming error
- // *Action: Report as bug
- 00017, 00000, "maximum number of calls exceeded"
- // *Cause: All call state objects are in use
- // *Action: Increase the number of maximum calls - init.ora parameter "calls"
- 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 sessions per process (%s) exceeded"
- // *Cause: Number of user sessions exceeded
- // *Action: Increase init.ora parameter "user_sessions"
- 00020, 00000, "maximum number of processes (%s) exceeded"
- // *Cause: All process state objects are in use
- // *Action: Increase maximum processes - init.ora parameter "processes"
- /
- 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 number of DML locks - init.ora parameter
- 00056, 00000, "DDL lock on object '%s' is already held in an incompatible mode"
- // *Cause: An attempt was made to aquire 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 DDL locks exceeded"
- // *Cause: System has run out of DDL locks.
- // *Action: Increase DDL lock parameter and warm start.
- 00058, 00000, "timeout occurred while waiting for DDL lock"
- // *Cause: Other user has a DML or DDL lock on the table you are trying
- // to lock.
- // *Action: Wait for the other user to release its DML or DDL lock and
- // then retry your operation.
- 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: DBA - Look at the trace file to see the transactions and resources
- // involved
- // User - 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_FILE init.ora parameter exceeded
- // *Action: Increase the LOG_FILES parameter and warm start.
- /
- /
- /
- / 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 obviouis things like disk space, quotas, etc.
- 00201, 00000, "control file '%s' version %s incompatible with ORACLE version %s"
- // *Cause: The control file was created by incompatible software
- // *Action: Need to go back to software version that created the control file,
- // export the database. Then cold start, and import the database
- // using current software version.
- 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 cannnot find the 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.
- 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 occured 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 retore a good copy of the control file or
- / cold start.
- 00218, 00000, "control file '%s' was created with physical size %s now is %s"
- // *Cause: The size of the control file in its header is different than
- // the physical block 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.
- 00219, 00000, "required control file size %s larger than maximum %s"
- // *Cause: Create database has specified a combination of parameters that
- // results in the the control file exceeding the internal maximum
- // size.
- // *Action: Create the database, using "maxdatafiles" or "maxlogfiles"
- // clauses in the create database statement.
- /
- /
- / 250 .. 299 archival & media recovery errors
- /
- 00250, 00000, "archival not enabled"
- // *Cause: Archival must be enabled in order to envoke it.
- // *Action: Enable archival.
- 00251, 00000, "archival/media recovery requires DBA privileges"
- // *Cause: Do not have DBA priviledge
- // *Action: contact a DBA
- 00252, 00000, "offline log '%s' is of sequence %s, want log of sequence %s"
- // *Cause: Specified log is out of sequence
- // *Action: Find log of correct sequence
- 00253, 00000, "length %s of specified archive string '%s' exceeds limit of %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 occured during archival of log '%s', sequence # %s"
- // *Cause: An error occured during archival.
- // *Action: Check the error stack for more detailed information.
- 00256, 00000, "error occured in translating archive text string '%s'"
- // *Cause: An error occured translating the archive control string.
- // *Action: Check the error stack for more detailed information.
- 00260, 00000, "cannot archive log sequence %s; >= current log sequence %s"
- // *Cause: The log sequence number supplied to the archival command is too large
- // to be valid.
- // *Action: Specify a valid log sequence number.
- 00261, 00000, "cannot archive log sequence %s; log currently being archived"
- // *Cause: The log sequence number specified to the archive command is
- // currently being archived.
- // *Action: Check all operating archive processes.
- 00262, 00000, "cannot archive log sequence %s; log reused"
- // *Cause: The log file corresponding to the log sequence specifed has been
- // reused.
- // *Action: None.
- 00263, 00000, "there are no logs that need archiving"
- // *Cause: The command ARCHIVE LOG NEXT found no logs needing archival.
- // *Action: None.
- 00264, 00000, "requested sequence %s before RESETLOGS sequence %s"
- // *Cause: It is not legal to apply logs that came before a
- // ALTER DATABASE OPEN RESETLOGS statement. This is caused
- // by an old database file being restored to the database.
- // *Action: Restore the offending database file(s) from a backup taken
- // after ALTER DATABASE OPEN RESETLOGS.
- 00265, 00000, "cannot archive log sequence %s before sequence %s"
- // *Cause: Logs must be manually archived in the order created.
- // *Action: Archive the older log first. If it is being archived now then
- // wait for it to successfully complete before archiving the next log.
- /
- / 300..359 - Redo File errors
- /
- 00300, 00000, "illegal redo log block size %s specified - exceeds limit of %s"
- // *Cause: The specified size of the redo log is greater than the maximum
- // block size for the system.
- // *Action: Reduce the redo log 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 occured
- // 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
- 00305, 00000, "log '%2!s' inconsistent; belongs to another database '%1!s'"
- // *Cause: The database name in the log file does not match the database name
- // *Action: Restore the correct log file
- 00306, 00000, "limit of %s log writer instances exceeded"
- // *Cause: Too many instance started
- // *Action: None
- 00308, 00000, "cannot open offline log '%s'"
- // *Cause: The system cannot open the specified offline redo log.
- // *Action: Restore access the log (check name, device, etc.) and retry.
- 00309, 00000, "log '%s' belongs to wrong database '%s'"
- // *Cause: The system cannot apply the redo log because it
- // belongs to another database
- // *Action: Restore the correct redo log
- 00310, 00000, "offline log '%s' contains sequence %s; sequence %s required"
- // *Cause: The offline log is not the correct log.
- // *Action: Restore the correct log file.
- 00313, 00000, "cannot open online log '%s' (log # %s, log sequence # %s)"
- // *Cause: The online log cannot be opened.
- // *Action: Restore online log.
- 00314, 00000, "online log '%s' (log # %s, sequence # %s) doesn't match sequence # %s"
- // *Cause: The online log is corrupted.
- // *Action: Restore online log.
- 00317, 00000, "cannot open current log '%s' (log # %s, sequence # %s) for writing"
- // *Cause: Either file is locked or protections are wrong.
- // *Action: Check the file protections or if the file is locked by another
- // process.
- 00320, 00000, "cannot read log file header"
- // *Cause: The file is not available.
- // *Action: Restore the log file.
- 00321, 00000, "cannot update log file header"
- // *Cause: Cannot write to the log file.
- // *Action: Restore the access to the file.
- 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 unstranslated name that yeilds a shorter translated name.
- 00327, 00000, "log file '%s' has size %s but should be size %s"
- // *Cause: A log file has shrunk in size. This is likely
- // to have been caused by operater 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
- // manual recovery may be required.
- 00331, 00000, "log '%s' 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 warmstart with current software.
- 00332, 00000, "log '%s' 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.
- 00334, 00000, "cannot start up logs - %s logs found, at least 2 needed"
- // *Cause: All on-line logs have been dropped.
- // *Action: Add at least 2 redo logs before starting the database.
- 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.
- 00340, 00000, "IO error processing online log file %s (log # %s, log sequence # %s)"
- // *Cause: An IO error occured on the named online log.
- // *Action: Restore accessability to file, or restore file from backup.
- 00341, 00000, "online log file '%s' has log file # %s, should be # %s"
- // *Cause: The internal information in an on-line log file does not
- // match the control file.
- // *Action: Restore correct file from backup.
- 00342, 00000, "current online log '%s' has wrong sequence # %s, should be %s"
- // *Cause: During crash recovery, the state of the log files is reconstructed
- // and it was found that the current log has been replaced with
- // a different version.
- // *Action: Restore the correct log, or use manual recovery.
- 00343, 00000, "unspooled online log '%s' has wrong sequence # %s, should be %s"
- // *Cause: During crash recovery, the state of the log files is reconstructed
- // and it was found that an unspooled (unarchived) log has the wrong
- // sequence number. Unless repaired, this may cause a future
- // attempt to use media recovery to fail.
- // *Action: Restore the correct file, or shut off media recovery, start the
- // database, backup up the database, and then restart media recovery.
- 00344, 00000, "unable to recreate log '%s' at the end of manual recovery"
- // *Cause: At the end of manual recovery, all logs need reformatting.
- // This message indicates a log IO failure occured.
- // *Action: Correct the file/device as indicated by accompaning errors.
- 00345, 00000, "redo log write error block %s count %s"
- // *Cause: An IO error has occured while writing the log
- // *Action: Correct the cause of the error, and then restart the system.
- // If the log is lost, apply media/manual recovery.
- 00346, 00000, "log no longer online. Media recovery required."
- // *Cause: While applying an online log during recovery, the log
- // was reused.
- // *Action: During media recovery the system catches this error, and prompts
- // for you to supply the spooled version of this log. For tablespace
- // online you now need to do media recovery.
- 00347, 00000, "online log '%s' (log # %s, sequence # %s) has blockize %s should be %s"
- // *Cause: During online recovery, the blocksize indicated in the control
- // file did not match the blocksize contined in the log file.
- // *Action: Restore correct log
- 00348, 00000, "single-process redo failure"
- // *Cause: An failure occured 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 accompaning error message, and correct the
- // device or specify another file name.
- 00350, 00000, "failure obtaining time"
- // *Cause: The operating system was unable to determine the time
- // to place in the redo log.
- // *Action: Consult the accompaning error message, take appropriate
- // action, and restart.
- 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.
- /
- / 370-389 kcb external errors
- /
- 00370, 00000, "potential deadlock during kcbchange operation"
- // *Cause:
- // *Action:
- 0371, 00000, "no free buffer handles available"
- // *Cause:
- // *Action:
- 0372, 00000, "file has gone off line; no further changes allowed"
- // *Cause:
- // *Action:
- 0373, 00000, "instance recovery block is current in cache"
- // *Cause:
- // *Action:
- 0374, 00000, "parameter db_block_size = %s invalid, valid range [%s..%s]"
- // *Cause: invalid value for db_block_size parameter
- // *Action: adjust parameter and restart
- 0375, 00000, "unable to get default db_block_size"
- // *Cause: the system was unable to determine the default db_block_size
- // *Action: see accompaning system specific error. As a workaround,
- // specify the blocksize in the init.ora file.
- / 436, 437: Oracle licencing 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 Detatched process startup errors
- /
- 00444, 00000, "background process '%s' failed while starting"
- // *Cause: Usaully due to a bad (or non-existent) background process image.
- // *Action: Get a good background process image.
- 00445, 00000, "background process '%s' didn't start"
- // *Cause: The specified process did not start
- // *Action: Ensure that the executable image is in the correct place with
- // the correct protections.
- 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 normaly (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
- 00481, 00000, "SMON process posting itself"
- // *Cause: This is trapped internally
- // *Action: None
- 00482, 00000, "SMON shut, shutdown abort required"
- // *Cause: Instance or Transaction recovery was required after the SMON
- // process was stopped in anticipation of shutdown. This is
- // a rare condition that can occur only in multi-instance operation.
- // *Action: Use shutdown abort. This instance will be recovered by surviving
- // instance(s) or by warm-start recovery.
- /
- / V5-compatibility DECNET driver codes
- /
- 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]"
- // *Cause: This is the generic internal error number for Oracle program
- // exceptions. This indicates that a proccess 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, "fatal ORACLE error occurred: unwise to proceed"
- // *Cause: The RDBMS is in an unrecoverable state.
- // *Action: Shutdown and warm start the system.
- 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
- /
- 00700, 00000, "maximum number of row cache objects (parameter '%s') exceeded"
- // *Cause: There are not enough row cache objects of the specified type
- // *Action: Increase the appropriate row cache object parameter and warm start
- // the system.
- // If the parameter is 'dc_free_extents' then this could mean that
- // your database is almost out of space, and is trying to coallesce
- // a large number of fragmented extents and failing. If this is
- // the case, then you should add more space to your database
- // (perhaps by adding a new datafile).
- 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, "maximum number of row cache enqueues exceeded"
- // *Cause: There are not enough row cache enqueues.
- // *Action: Increase the row cache enqueue paramter and warm start the system.
- 00703, 00000, "maximum number of row cache instance locks exceeded"
- // *Cause: There are not enough row cache enqueues.
- // *Action: Increase the row cache enqueue paramter and warm start the system.
- /
- 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 large for CHAR column"
- // *Cause:
- // *Action:
- 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, "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 [ <identifier> . ] <identifier> 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, "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:
- 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-wide 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-wide options in separate
- // statements.
- 00982, 00000, "missing plus sign"
- // *Cause:
- // *Action:
- 00983, 00000, "cannot define ROWID column - no corresponding SQL datatype"
- // *Cause: Attempt to create a table with a rowid column as in
- // "CREATE TABLE ... AS SELECT ROWID ... FROM ..." which is illegal
- // because there is no corresponding SQL datatype for rowid.
- // *Action: Use the function ROWIDTOCHAR to convert rowid to character as in
- // "CREATE TABLE ... AS SELECT ROWIDTOCHAR(ROWID) ... FROM ...".
- 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, "invalid format for GRANT command"
- // *Cause:
- // *Action:
- 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:
- // *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:
- // *Action:
- 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:
- 01017, 00000, "invalid username/password; logon denied"
- // *Cause:
- // *Action:
- 01018, 00000, "column does not have a LONG datatype"
- // *Cause:
- // *Action:
- /
- 01020, 00000, "unknown context state"
- // *Cause:
- // *Action:
- 01021, 00000, "invalid context size specified"
- // *Cause:
- // *Action:
- 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.
- 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, "error backing out last row, transaction rolled back"
- // *Cause:
- // *Action:
- 01030, 00000, "SELECT ... INTO variable does not exist"
- // *Cause:
- // *Action:
- 01031, 00000, "insufficient privileges"
- // *Cause:
- // *Action:
- 01032, 00000, "no such userid"
- // *Cause:
- // *Action:
- 01033, 00000, "ORACLE initialization or shutdown in progress"
- // *Cause:
- // *Action:
- 01034, 00000, "ORACLE not available"
- // *Cause: The host database is down or doesn't have the proper file
- // permissions to allow connection.
- // *Action: Make sure the database is up. Check to see that the file
- // permissions of the ORACLE executable include the setuid bit.
- 01035, 00000, "ORACLE only available to users with DBA privilege"
- // *Cause:
- // *Action:
- 01037, 00000, "cannot allocate sort work area cursor; too many cursors"
- // *Cause:
- // *Action:
- 01038, 00000, "this version of ORACLE is too old to access the database"
- // *Cause:
- // *Action:
- 01039, 00000, "database version %s incompatible with ORALCE version %s"
- // *Cause:
- // *Action:
- 01040, 00000, "this version of ORACLE does not match the mounted system"
- // *Cause:
- // *Action:
- 01046, 00000, "cannot acquire space to extend context area"
- // *Cause:
- // *Action:
- 01050, 00000, "cannot acquire space to open context area"
- // *Cause:
- // *Action:
- 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:
- /
- / 1070 - 1099: V6 program interface errors
- 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 was previously created.
- // *Action: Check what error was signaled when the database was first
- // created and take appropriate actions to recreate the database.
- 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".
- 01085, 00000, "maximum savepoints exceeded"
- // *Cause: Obvious
- // *Action:
- 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: A DBA has used the SHUTDOWN IMMEDIATE command 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: A DBA has used the SHUTDOWN command 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
- /
- 01099, 00000, "cannot mount database in SHARED mode if started in single process mode"
- // *Cause: Obvious
- // *Action:
- /
- / 1100 to 1200: 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.
- // *Action:
- 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 number for first instance (%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, "control file seq %s disagrees with first instance's control file seq %s"
- // *Cause: An attempt to start this instance has determined that the control
- // file's sequence number does not match that of an existing instance.
- // It is likely that the wrong control file is being used.
- // *Action: Check to see that the correct control file is being used.
- 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, "too many instances opening database"
- // *Cause: Too many instances are already running
- // *Action:
- 01109, 00000, "database not open"
- // *Cause: ??? Should this be an internal error???
- // *Action:
- 01110, 00000, "file '%s' not online"
- // *Cause: Unused error message
- // *Action:
- 01111, 00000, "already started media recovery"
- // *Cause: The same user is attempting to start media recovery and it is
- // already running.
- // *Action: None.
- 01112, 00000, "media recovery not started"
- // *Cause: An attempt to end media recovery is being made but media recovery
- // was not started.
- // *Action: None.
- 01113, 00000, "file '%s' needs media recovery starting at log sequence # %s"
- // *Cause: An attempt was made to open a database file that is in need
- // of media recovery.
- // *Action: First apply media recovery to the file.
- 01114, 00000, "IO error writing blocks of file '%s' (block # %s, # blocks %s)"
- // *Cause: Device on which the file resides is probably offline
- // *Action: Restore access to the device
- 01115, 00000, "IO error reading blocks from file '%s' (block # %s, # blocks %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: Usaully the file is not accessable.
- // *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'; database is open or mounted SHARED"
- // *Cause: Obvious
- // *Action:
- 01121, 00000, "cannot rename online database file '%s'; database is open or mounted SHARED"
- // *Cause: Obvious
- // *Action:
- 01122, 00000, "database file '%s' (file '%s') failed verification check"
- // *Cause: The information in this file is inconsistent with information
- // from the control file.
- // *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 online file '%s' - must be offline to recover"
- // *Cause: obvious
- // *Action:
- 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 tablespace does not exist"
- // *Cause: ???
- // *Action:
- 01130, 00000, "database file '%s' 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:
- // *Action:
- 01136, 00000, "DBWR failed to open file '%s' - possibly locked by another OS process"
- // *Cause:
- // *Action:
- 01137, 00000, "error ending backup - begin backup timestamps do not match"
- // *Cause: An attempt to end a tablespace backup has found that the files'
- // begin backup timestamps do not match. This inconsistency could be
- // introduced by giving tablespaces that did not start backup together
- // or by restoring a database file while a backup is progress.
- // *Action: Make sure that all files belonging to the tablespace are
- // cotemporaneous and the tablespaces ending backup started backup
- // in the same start command.
- 01138, 00000, "manual database recovery has not applied enough logs to make file '%s' valid"
- // *Cause: A manual recovery session was started, but an insufficient number of
- // logs were applied to make the database consistent.
- // *Action: Either apply more logs until the database is consistent or
- // restore the database files from an older backup and repeat recovery.
- 01139, 00000, "RESETLOGS option only valid after a manual database recovery"
- // *Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there
- // has been no manual 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' is offline"
- // *Cause: An attempt to disable media recovery found an offline file.
- // The offline file could possibly need media recovery, thus
- // media recovery can not be disabled.
- // *Action: Bring the offending file online or drop the tablespace it
- // belongs to and retry this command.
- 01144, 00000, "SYSTEM tablespace file '%s' needs media recovery starting at log sequence # %s"
- // *Cause: An attempt to do crash recovery found a file in the SYSTEM
- // tablespace which requires media recovery. Since this tablespace
- // contains the data dictionary no recovery can be accomplished before
- // doing media recovery.
- // *Action: Do media recovery on the database.
- /
- 01145, 00000, "tablespace offline immediate disallowed unless media recovery enabled"
- // *Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE is only allowed if media
- // recovery is enabled.
- // *Action:
- /
- 01146, 00000, "Could not open SYSTEM tablespace file '%s'"
- // *Cause: An attempt to open a file belonging to the SYSTEM TS failed.
- //
- // *Action:
- /
- 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 can not 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: Obvious
- // *Action:
- 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 offline tablespace - 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.
- 01151, 00000, "start and end backup must be for same files - file '%s' missing"
- // *Cause: When attempting to end backup it was noticed that a file that
- // started backup at the same time was not included in the list of files
- // ending backup.
- // *Action: Complete backup of all files that were specified in start backup
- // and then enter end backup for all the files.
- 01152, 00000, "file '%s' was not restored from a sufficiently old backup "
- // *Cause: A manual 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. Note that this mistake
- // can not always be caught.
- // *Action: Either apply more logs until the database is consistent or
- // restore the database file from an older backup and repeat recovery.
- 01153, 00000, "NORESETLOGS option not allowed with old control file"
- // *Cause: NORESETLOGS option was given after manual recovery but the control
- // file is older than some of the data files. The database would be
- // corrupt if the logs are not reset.
- // *Action: Use RESETLOGS option or restore all files and do a normal database
- // recover.
- 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, "Another media recovery is running now"
- // *Cause: Attempt to start a second media recovery or open resetlogs during
- // media recovery.
- // *Action: Wait for the other recovery to complete.
- /
- /
- / 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 a concatenated 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.
- // *Action: Create the index without the NOSORT option.
- 01410, 00000, "invalid ROWID"
- // *Cause:
- // *Action:
- 01416, 00000, "two tables cannot be outer-joined to each other"
- // *Cause:
- // *Action:
- 01417, 00000, "more than one table with (+) in outer join predicate"
- // *Cause:
- // *Action:
- 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:
- 01427, 00000, "single-row subquery returns more than one row"
- // *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 view of more than one 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 exceeded"
- // *Cause:
- // *Action:
- 01451, 00000, "column to be modified to NULL is already NULL"
- // *Cause:
- // *Action:
- 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 update operation inside a READ ONLY transaction"
- // *Cause: A non-DDL 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 255 characters"
- // *Cause:
- // *Action:
- 01463, 00000, "cannot grant to or revoke from self"
- // *Cause:
- // *Action:
- 01464, 00000, "circular grant (granting to grant ancestor) of table or view"
- // *Cause:
- // *Action:
- 01465, 00000, "invalid hex number"
- // *Cause:
- // *Action:
- 01466, 00000, "unable to read data - table definition has changed"
- // *Cause: Query parsed after tbl (or index) change, and executed
- // w/old snapshot
- // *Action: commit (or rollback) transaction, and re-execute
- 01467, 00000, "sort key too long"
- // *Cause:
- // *Action:
- 01468, 00000, "a predicate may reference only one outer-joined table"
- // *Cause:
- // *Action:
- 01469, 00000, "PRIOR can only be followed by a column name"
- // *Cause: Attempting to specify "PRIOR <something>" where <something> is not
- // a column name.
- // *Action: Only a column name can follow PRIOR. Replace with a column name.
- 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 255 bytes.
- // *Action: Such bind variables cannot participate in array binds.
- // Use an ordinary bind operation instead.
- 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 will an ASCII null character.
- 01481, 00000, "invalid TO_CHAR format string"
- // *Cause: The format string parameter to the TO_CHAR function is not
- // a valid format string for converting a number to a character string.
- // *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.
- /
- / 1484 - 1486 -- reserved for V6.1 array bind variable errors
- /
- 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 packed decimal nibble"
- // *Cause: An impossible request for decimal to oracle number conversion was
- // made
- // *Action: This conversion cannot be performed
- /
- / 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 occured during create database
- // *Action: See accompaning errors.
- 01503, 00000, "cannot get control file name(s)"
- // *Cause: During create database or alter database, the control file(s)
- // could not be found.
- // *Action: Make sure your control file(s) are accessible.
- 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.
- 01514, 00000, "error in dropping log '%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.
- 01515, 00000, "cannot drop log at this time; log in use"
- // *Cause: ALTER DATABASE is attempting to drop a log file which
- // is currently in use.
- // *Action: Wait until the log file is no longer in use.
- 01516, 00000, "nonexistent log/data file '%s'"
- // *Cause: ALTER DATABASE is attempting to rename 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, "cannot rename log '%s' at this time; log in use"
- // *Cause: ALTER DATABASE is attempting to rename a log file which
- // is currently in use.
- // *Action: Wait until the log file is no longer in use.
- 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, "failure in renaming data file '%s'"
- // *Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME,
- // an error occurred while renaming the file.
- // *Action: Check the error stack for detailed error information.
- 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, "no resource privilege or 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 dba 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 bring a tablespace offline because it is not online
- // *Action: Check the status of the tablespace
- 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: 1) Try to acquire offline rollback segment during startup.
- // 2) Try to drop a rollback segment that contains active transactions.
- // *Action: 1) Bring the tablespace containing the rollback segment online or
- // do not specify the rollback segment in init.ora.
- // 2) If the rollback segment is in use, shutdown the instance using
- // rollback segment, else if the rollback segment needs recovery,
- // find out the errors that are holding back the rolling back
- // of the transactions and take appropriate actions.
- 01546, 00000, "tablespace contains active rollback segment '%s'"
- // *Cause: Tried to bring a tablespace that contains active rollback segment(s)
- // offline
- // *Action: Shutdown instances that use the active rollback segments in the
- // tablespace and then bring the tablespace offline
- 01547, 00000, "failed to allocate extent of size %s in tablespace '%s'"
- // *Cause: Tablespace indicated is out of space
- // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
- // files to the tablespace indicated or create the object in other
- // tablespace if this happens during a CREATE statement
- 01548, 00000, "active rollback segment '%s' found, terminate dropping tablespace"
- // *Cause: Tried to drop a tablespace that containts active rollback segemnt(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 too small)"
- // *Cause: rollback records needed by a reader for consistent read are
- // overwritten by other writers
- // *Action: Use larger rollback segments
- 01556, 00000, "maximum number of %s extents exceeded"
- // *Cause: Tried to allocate more extents than allowed
- // *Action: Recreate the object with larger extent size or with sufficiently
- // large PCTINCREASE storage option
- 01557, 00000, "rollback segment extents must be at least 3 blocks"
- // *Cause: Specified extent of less than 3 blocks 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"
- // *Cause: One of more of the global hash table sizes specified is/are different
- // from those of other instances
- // *Action: Correct the hash table sizes using the init.ora parameters that
- // have the prefix "gc_"
- 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 (id = %s)"
- // *Cause: Failure occured when trying to extent 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 occured 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 would leave less than two log files"
- // *Cause: Dropping all the logs specified would leave fewer than the required
- // two log files.
- // *Action: Either drop fewer logs or close the database before deleting the
- // logs.
- 01568, 00000, "cannot set space quota on PUBLIC"
- // *Cause: Trying to set space quota on a tablespace for PUBLIC.
- // *Action: If trying to grant system-wide or tablespace-wide space priviledges
- // to all users, use GRANT RESOURCE [ON <tablespace>] TO PUBLIC.
- 01569, 00000, "data file too small for system dictionary tables"
- // *Cause: The datafile specified during creation of the database is too
- // small to hold the system dictioanry tables.
- // *Action: Recreate the database by specifying a larger file or more files.
- 01571, 00000, "log records version %s incompatible with ORACLE version %s"
- // *Cause: 1) There are rollback segments that need recovery.
- // 2 There are offline files that needs recovery.
- // *Action: shutdown and then warmstart using the compatible software.
- // Bring the offline tablespace online so that all deferred rollback
- // records are applied. Shutdown and then warmstart using
- // current software
- 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 occured during recovery"
- // *Cause: A write error occured 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 occured while attempting to create a
- // control file backup.
- // *Action: Check the error stack for more detailed information
- 01581, 00000, "ALTER SYSTEM requires DBA privileges"
- // *Cause:
- //
- // *Action:
- 01582, 00000, "Unable to open control file for backup"
- // *Cause: An operating system error occured 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 occured 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 occured 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 occured 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 occured 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. You must complete the database opening with the RESETLOGS
- // option.
- // *Action: Use the RESETLOGS option when opening the database.
- 01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open"
- // *Cause: Either manual or time-based 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: init.ora parameters FREE_LIST_PROC is too large.
- // *Action: Reduce the init.ora parameters FREE_LIST_PROC
- /
- / 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 255 characters.
- // *Action: Use a string literal of at most 255 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:
- 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, "must have DBA privilege to execute requested GRANT or REVOKE"
- // *Cause:
- // *Action:
- 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, "must have DBA privilege to create or drop PUBLIC synonyms"
- // *Cause:
- // *Action:
- 01735, 00000, "invalid ALTER TABLE option"
- // *Cause:
- // *Action:
- 01736, 00000, "[NOT] SUCCESSFUL expected"
- // *Cause:
- // *Action:
- 01737, 00000, "you may only lock a table in SHARE or EXCLUSIVE mode"
- // *Cause:
- // *Action:
- 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:
- 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:
- 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:
- 01756, 00000, "quoted string not properly terminated"
- // *Cause:
- // *Action:
- 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:
- 01762, 00000, "vopdrv: view query block not in FROM"
- // *Cause:
- // *Action:
- 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.
- // These options may only be specified for the cluster itself.
- // *Action: Remove the illegal option(s).
- 01773, 00000, "may not specify column datatypes in this CREATE TABLE"
- // *Cause:
- // *Action:
- 01775, 00000, "looping chain of synonyms"
- // *Cause:
- // *Action:
- 01777, 00000, "WITH GRANT OPTION not allowed in this system"
- // *Cause:
- // *Action:
- 01778, 00000, "maximum subquery nesting level exceeded"
- // *Cause:
- // *Action:
- 01780, 00000, "string literal required"
- // *Cause:
- // *Action:
- 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:
- 01799, 00000, "must have DBA privilege for this AUDIT operation"
- // *Cause: User issued AUDIT or NOAUDIT on default or system-wide auditing
- // and does not possess DBA privilege.
- // *Action: Only a DBA may issue these operations.
- /
- / 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:
- /
- / 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 3442447"
- // *Cause: An invalid Julian date was entered.
- // *Action: Enter a valid Julian date between 1 and 3442447.
- 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 letter was found in a date where a number was expected"
- // *Cause:
- // *Action:
- 01859, 00000, "a number was found in a date and a letter was expected"
- // *Cause:
- // *Action:
- 01897, 00000, "invalid delimiter in date input string"
- // *Cause: An invalid delimiter was used as the input to the to_date function
- // *Action: Most obvious delimiters work ('-', ':', '/')
- /
- / 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 legal for tables but not 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.
- 01915, 00000, "invalid auditing option for views"
- // *Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is
- // legal for tables but not for views.
- // *Action: The following options may not be used for views
- // and should be removed: ALTER, INDEX, REFERENCES
- 01916, 00000, "ONLINE keyword or OFFLINE keyword expected"
- // *Cause: keyword missing
- // *Action: supply missing keyword
- 01917, 00000, "SEQUENCE keyword expected"
- // *Cause: keyword missing
- // *Action: supply missing keyword
- /
- / 2000 - 2099 Parse errors continued from 1700 - 1799
- /
- 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:
- 02008, 00000, "non-zero scale specified for nonnumeric column"
- // *Cause:
- // *Action:
- 02010, 00000, "missing host connect string"
- // *Cause:
- // *Action:
- 02011, 00000, "duplicate database link name"
- // *Cause:
- // *Action:
- 02012, 00000, "missing USING keyword"
- // *Cause:
- // *Action:
- 02013, 00000, "missing CONNECT keyword"
- // *Cause:
- // *Action:
- 02014, 00000, "cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc."
- // *Cause:
- // *Action:
- 02015, 00000, "cannot select FOR UPDATE from remote table"
- // *Cause:
- // *Action:
- 02016, 00000, "cannot use a subquery in a START WITH on a remote database"
- // *Cause:
- // *Action:
- 02017, 00000, "integer value required"
- // *Cause: The given parameter is not an integer.
- // *Action: Use an integer or use a function such as trunc or round to
- // produce an integer value for the parameter.
- 02018, 00000, "database link of same name has an open connection"
- // *Cause:
- // *Action:
- 02019, 00000, "database link does not exist"
- // *Cause:
- // *Action:
- 02020, 00000, "database link connection table is full"
- // *Cause:
- // *Action:
- 02021, 00000, "inappropriate operation for remote database"
- // *Cause:
- // *Action:
- 02022, 00000, "a LONG column cannot be fetched from a remote database"
- // *Cause:
- // *Action:
- 02023, 00000, "START WITH or CONNECT BY predicate cannot be evaluated by remote database"
- // *Cause:
- // *Action:
- 02024, 00000, "CONNECT BY and ROWID not supported by remote database"
- // *Cause:
- // *Action:
- 02025, 00000, "must have DBA privilege to create or drop PUBLIC database links"
- // *Cause:
- // *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 255 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.
- 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 clutstered 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 performed a speed-execution call on a SQL statement
- // containing host variables without first performing
- // a speed bind call
- // *Action: perform a speed bind call before performing a speed execution
- // call.
- /
- / 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
- /
- 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, 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.
- 02150, 00000, "invalid username following ALTER USER"
- // *Cause: An identifier does not follow ALTER USER.
- // *Action: Specify a user name identifier following ALTER USER.
- 02151, 00000, "invalid option for ALTER USER"
- // *Cause: An invalid option is present.
- // *Action: Specify a valid ALTER USER option.
- 02152, 00000, "invalid password for ALTER USER IDENTIFIED BY"
- // *Cause: An identifer does not follow IDENTIFIED BY.
- // Note that character string literals are not valid passwords.
- // *Action: Specify a password identifer.
- 02153, 00000, "invalid password text for ALTER USER IDENTIFIED BY VALUES"
- // *Cause: Either a character string literal does not follow BY VALUES or
- // the string is longer than 30 characters.
- // *Action: A string enclosed in single quotes of at most 30 characters
- // must follow BY VALUES.
- 02154, 00000, "invalid argument to ALTER USER IDENTIFIED BY"
- // *Cause: An identifer or the keyword VALUES does not follow IDENTIFIED BY.
- // *Action: Place a password identifier or VALUES followed by a
- // character string literal after IDENTIFIED BY.
- 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.
- 02161, 00000, "invalid value for MAXLOGFILES"
- // *Cause: A number does not follow MAXLOGFILES.
- // *Action: Specify a number after MAXLOGFIELS.
- 02162, 00000, "invalid value for MAXDATAFILES"
- // *Cause: A number does not follow MAXDATAFILES.
- // *Action: Specify a number after MAXDATAFILES.
- 02163, 00000, "invalid value for MAXINSTANCES"
- // *Cause: A number does not follow MAXINSTANCES.
- // *Action: Specify a number after MAXINSTANCES.
- 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.
- 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.
- 02175, 00000, "invalid rollback segment name"
- // *Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifer
- // was not found following ROLLBACK SEGMENT.
- // *Action: Place the segment name folling 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.
- 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.
- 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 <name> after ROLLBACK [WORK].
- 02182, 00000, "savepoint name expected"
- // *Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
- // *Action: Place a savepoint name following TO [SAVEPOINT].
- 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 <tablespace> required"
- // *Cause: In a grant or revoke statement, the user specified a tablespace
- // quota but did not follow it with the ON <tablespace> clause.
- // *Action: Specify the tablespace on which the quota is to be applied
- // with the ON <tablespace> clause.
- 02190, 00000, "keyword TABLES expected"
- // *Cause: The keyword TABLES is expected following DROP CLUSTER <name>
- // INCLUDING.
- // *Action: Place TABLES after INCLUDING.
- 02192, 00000, "must have DBA privilege to CREATE or ALTER DATABASE"
- // *Cause: The user does not have DBA privilege.
- // *Action: This command may only be issed by a user with DBA privilege.
- 02193, 00000, "must have DBA privilege to CREATE/ALTER/DROP ROLLBACK SEGMENT"
- // *Cause: The user does not have DBA privilege.
- // *Action: This command may only be issed by a user with DBA privilege.
- 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, "must have DBA privilege to CREATE/ALTER/DROP TABLESPACE"
- // *Cause: The user does not have DBA privilege.
- // *Action: This command may only be issed by a user with DBA privilege.
- 02196, 00000, "must have DBA privilege to ALTER USER"
- // *Cause: The user does not have DBA privilege.
- // *Action: This command may only be issed by a user with DBA privilege.
- 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 and MINEXTENTS storage options not allowed"
- // *Cause: The user attempted to alter the INITIAL and/or MINEXTENTS
- // storage options of a table, cluster, index, or rollback segment.
- // These options may only be specified when the object is created.
- // *Action: Remove these options and retry the statement.
- 02204, 00000, "ALTER, INDEX, and REFERENCES privileges 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, "DELETE, INDEX, INSERT, UPDATE, and REFERENCES not allowed 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 any of DELETE, INDEX, INSERT,
- // UPDATE, and REFERENCES privileges 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:
- // GRANT/REVOKE RESOURCE, 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 specifed 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.
- 02227, 00000, "invalid cluster name"
- // *Cause: A cluster name of the form [ <identifier> . ] <identifier> is
- // expected but not present.
- // *Action: Enter an appropriate cluster name.
- 02228, 00000, "duplicate SIZE specification"
- // *Cause: The SIZE option is specified more than once.
- // *Action: Specify the SIZE option at most once.
- 02229, 00000, "invalid SIZE option value"
- // *Cause: The specified value must be an integer number of bytes.
- // *Action: Specify an appropriate value.
- 02230, 00000, "invalid ALTER CLUSTER option"
- // *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS,
- // STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
- // *Action: Specify only legal options.
- 02231, 00000, "missing or invalid option to ALTER DATABASE"
- // *Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG,
- // MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement.
- // *Action: Specify only legal options.
- 02232, 00000, "invalid MOUNT mode"
- // *Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword
- // in an ALTER DATABASE statement.
- // *Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT.
- 02233, 00000, "invalid CLOSE mode"
- // *Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword
- // in an ALTER DATABASE statement.
- // *Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE.
- 02236, 00000, "invalid file name"
- // *Cause: In a LOGFILE, DATAFILE, or RENAME clause, a character string
- // literal is expected, but not found, in a filename list.
- // *Action: Specify filenames using character string literals.
- 02237, 00000, "invalid file size"
- // *Cause: An integer file size does not follow SIZE in a LOGFILE or
- // DATAFILE file list.
- // *Action: Specify an appropriate file size after SIZE.
- 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.
- 02242, 00000, "no options specified for ALTER INDEX"
- // *Cause: No options specified.
- // *Action: Specify at least one of INITRANS, MAXTRANS, or STORAGE.
- 02243, 00000, "invalid ALTER INDEX option"
- // *Cause: An option other than INITRANS, MAXTRANS,or STORAGE is
- // specified in an ALTER INDEX 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: An option other than SET EVENTS was found.
- // *Action: Specify the SET EVENTS option.
- 02250, 00000, "missing or invalid constraint name"
- // *Cause: The constraint name is missing or invalid.
- // *Action: Specify a valid identifier name for the constraint name.
- 02251, 00000, "subquery not allowed here"
- // *Cause: Subquery is not allowed here in the statement.
- // *Action: Remove the subquery from the statement.
- 02252, 00000, "check constraint condition not properly ended"
- // *Cause: The specified search condition for the check constraint is not
- // properly ended.
- // *Action: End the condition properly.
- 02253, 00000, "constraint specification not allowed here"
- // *Cause: Constraint specification is not allowed here in the statement.
- // *Action: Remove the constraint specification from the statement.
- 02254, 00000, "DEFAULT <expression> not allowed here"
- // *Cause: Default value expression is not allowed for the column here in the
- // statement.
- // *Action: Remove the default value expression from the statement.
- 02255, 00000, "NOT NULL not allowed after DEFAULT NULL"
- // *Cause: NOT NULL specification is conflicting with the NULL default value.
- // *Action: Remove the NOT NULL or DEFAULT NULL specification.
- 02256, 00000, "number of referencing columns must be equal to number of referenced columns"
- // *Cause: The number of columns in the foreign-key referencing list is not
- // equal to the number of columns in the referenced list.
- // *Action: Make sure there are no missing 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.
- 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, "such unique or primary key does not exist in the referenced table"
- // *Cause: Self-evident.
- // *Action: Add such key in the referenced table first before referencing it.
- 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